The insufficiency of Scrum is a fallacy perpetrated by teams that don’t step up their practices in concert with their planning and don’t really want to make it work anyway. You can fail doing Kanban, XP, Merise and SSADM just as easily unless you have good engineering practices as well.
The term ‘Scrum’ was first used by Hirotaka Takeuchi and Ikujiro Nonaka, 2 acknowledged management thinkers, in their ground-breaking 1986 paper “The New New Product Development Game“. They borrowed the name from the game of rugby to stress the importance of teams in complex ...
I’ve spent the last 3 years exploring the in’s and out’s of different Agile frameworks and methodologies. I’ve worked with large commercial firms, government contractors, and small ISVs to adopt one set of Agile practices or another. In the beginning things are generally amaz...
Today I was finally able to connect some dots on something that had been bothering me for a while. As a Scrum.org Scrum trainer, I always tried to convey that assigning value to information has a big risk of obscuring the transparency needed for inspect & adapt. The reasoning here is that if you...
Lean Agile adoption can only be successful when the people themselves create the necessary changes and therefore are really committed and feel accountable for it. The path to Lean Agile adoption can therefore not be planned in full detail upfront. But the path towards adoption can only emerge, the p...
Scrum is not a methodology. Scrum is a process, but of a non-repeatable kind. Scrum is a framework of rules, roles and principles that helps people and organizations emerge their real process, specific and fitting to their time and context. Scrum is a light and simple base that wraps existing produc...
In May of 2011 I was able to run my first Pay It Forward Scrum Training at the University of Bern in Switzerland. I had blogged about this event here: The 1000 Students Challenge. Last week-end I had the second run at the University of Applied Sciences (FHNW) in Brugg Switzerland. 29 stud...
On January 25th, 2013, Wired published an article by Leslie Lamport describing the need to build software like we build houses. This wasn’t the first time I heard this argument, but I was surprised that a publication as forward-thinking as Wired would publish such a backwards-looking article. ...
The most common Scrum meeting that people seem to get wrong is the Sprint Review. I hear people calling it a “demo", a “showcase” or my pet hate the “show and tell". This completely fails to achieve the key purpose of the Sprint Review.
The Sprint Review is designed so tha...
This is a game I created, which was then used and refined by me and my colleague Laurie Young to help gauge how well everyone involved in a project understand their responsibilites to the project and each other. It lends insight in to the pre-conceptions that people have about how projects should be...
In our Professional Scrum classes we also talk about the topics of User Stories, Planning Poker and (Daily) Stand-up meetings. Some attendants have never heard of it. Some have never practiced it. Some are convinced, or have been instructed, that Scrum says these are mandatory to do.
The Scrum.org Face to Face meeting this weekend (Jan. 26-27) was as usual packed with information I will be digesting over the next few weeks. In a Scrum.org Face to Face we are all invited to actively participate. With every presentation it transpired the ideal of contributing to the “improve...
One of the key ingredients to becoming a great team is learning to focus on solutions, not problems. Unfortunately, this is really hard and requires practice. As humans, our natural response is to do just the opposite. In this post, I will explore why this is so and share things you can do to help.
Probably the most known purpose (task) of a Scrum Master is to remove impediments. If that is reassuring: it’s even described in the Scrum Guide. A Scrum Master is indeed ‘officially’ expected to remove impediments to development and to the Development Team’s progress.
A Scrum.org acaba de liberar o teste aberto de Scrum Developer, o Developer Open Assessment. É uma prova que você pode fazer gratuitamente para avaliar o seu nível de conhecimento com desenvolvimento de software usando Scrum. Diferentemente da Scrum Open Assessment, que tamb&eacu...