|
|
Entries for 'scrum'
The purpose of Scrum is to help people inspect & adapt, to provide transparency to the work being undertaken, to know reality to base decisions on, to adjust, to adapt, to change, to gain flexibility. The rules, principles and roles of the framework, as described in the Scrum Guid...
You’ve seen the statistics - Jeff Sutherland’s group consistently achieving 500-750% increases in productivity, organisations tripling their productivity in a matter of months etc. You’ve implemented Scrum so how come you aren’t reaping these sorts of benefits?
[Read more...]...
It is often said that the Product Backlog must capture all requirements. However, the Product Backlog is not a replacement for the old requirements list. This would limit it to a new name for an old habit. The value of the Product Backlog lies not in precision, in detail or in perfection, like the r...
The ability to inspect and adapt is what differentiates good software development teams from great software development teams. For agile teams, the retrospective is a key event to making that happen. Just as the daily scrum is a scheduled time each morning to plan an attack for the day, the retrospe...
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 ...
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...
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...
Find out how Visual Studio has become the tool of choice to manage your Scrum projects, and how it stands out of the way allowing you to do Agile in your own terms instead of forcing you to adapt your development process to a tool. We will take a tour on how you can enact Scrum best practices and cy...
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...
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.
I recently received an interesting scientific article from Gunther Verheyen titled "Getting Things Done: The Science Behind Stress-Free Productivity" (Heylighen & Vidal, in press). The article discusses possible scientific explanations for the success of a personal productivity approach called "...
For reasons of competitiveness the delivery of IT services of Amir Arooni's department (CIO of the Solution Delivery Center for Channels at ING NL) needed fundamental improvements. A small project revealed that the existing, waterfall, working methods and organization structures of the cha...
Well isn’t that great? Your team is now supposed to do Scrum and now there is another set of meetings cutting into the time you would rather use to actually get something done. In popularity, “meetings” tend to be viewed as enjoyable as a dentist appointment. We have books like &ld...
The Scrum Guide describes the basic rules of the game of Scrum. You can easily detect whether you are doing Scrum. It takes no more than 9 questions. If you can answer every question with a ‘Yes’, you are doing Scrum. Congratulations. We got rid of the “ScrumBut” expressions....