As discussed yesterday, the Scrum Guide 2011 brings updated roles. Besides that, the events have changed too:
Sprints
A new requirement is, that Sprints have the same length throughout the development of a product. In my opinion, Sprint lengths may vary if there are good reasons, but the Sprint length should be kept the same if possible.
While the Sprint length is now fixed, the scope is not as written down in the old Scrum Guide (“[…] team commits to doing a PBI in the sprint […]“). The Development Team now does its best to create a “forecast” of what it can achieve during a Sprint. If necessary, the scope can be renegotiated while the Development Team learns more during the Sprint as long as the Sprint Goal is still valid.
Daily Scrum
There is a now goal for the Daily Scrum now: “create a plan for the next 24 hours”. The exchange of information between the Development Team members is still there, but it is more important to assess progress towards the Sprint Goal and to formulate how to reach it each day.
Sprint Backlog
Again, the Sprint Backlog does not contain Technical Tasks anymore. It contains Product Backlog Items (PBIs) which denote the plan to deliver the product increment and realizing the Sprint Goal. New PBIs are added by the Development Team during the Sprint as more is learned. During the Sprint Planning, PBIs from the Product Backlog are moved to the Sprint Backlog, so they are estimated. The Scrum Guide does not requires estimates for PBIs added to the Sprint Backlog, although it is implicitely required to estimate the remaining work. How that is done is up to each organization.
Sprint Burndown Chart
Not only the Sprint Burndown Chart has been removed from the Scrum Guide, the time spent is also not relevant anymore, only the remaining work is important. Another paragraph in the guide still notes that historical information is helpful, but important lessons from project management have been forgotton. Metrics and historical information is the basis for continuous improvement and so a history of the velocity is very important.
During the next weeks, Ken Schwaber and Jeff Sutherland plan to shed more light on the updates in the Scrum Guide, so stay tuned.
Dieser Artikel wurde von Andreas Heilwagen am 26.07.2011 um 07:00 gepostet und unter Best-of, Scrum, Standards eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.
