New Scrum-Tools can be found on the market everyday due to the encouragement of Scrum. Although this term doesn’t only refer to Software tools, but aids of every kind, that support the work of the Scrum Master, Product Owner and team with their preparation and during the sprints. E.g. there is the Whiteboard and the very handy labels that offer an overview about the present sprint at the sprint planning meeting as well as at the daily standup meeting. For all the teams that work distributed there is an online-variation of the Whiteboard as software.
Figure 2: Example of a Scrum Whiteboard
Furthermore handy card games such as “Scrum Planning Poker” support the estimation of efforts or the “Business Value Game” for the prioritization of requirements for the Scrum teams easily but also effectively. Interactive online Whiteboard Regarding the Scrum tools it can be said: Before using Scrum-software the team should know how to handle this method and don’t act else wise because of uncertainties of the method. Then a Scrum tool is usually very useful, no matter if it’s about the capture, the vision and historiography of requirements, the description of user stories or tasks or the planning of a sprint. A good and complete list of such tools including judgements can be found at www.userstories.com.
The Scrum Master plays an important part as he’s the one balancing the interests of the other two Scrum-roles: The Product Owner acts primarily on the Business Value and the team requests more quality, for which it is responsible. In order to keep the balance of these two different forces the Scrum Master has to be the supporter and negotiation artist. He does not stand between the Product Owner and the Team, rather arranges a clear communication and moderates during conflicts. This is the technique how the goals of the product and a sprint can be reached.
Scrum Master/Product Owner:
* For the title of the certified Scrum Master (CSM) and Certified Scrum Product Owner (CSPO) a two days training is required, where the theoretical basics of the method get taught and where a connection is created to a practical application. For increasing the quality of the certification an exam is planned for 2010 at the end of the training.
* Who wants to be called a Scrum Practitioner needs to prove that he’s been working for at least one year in Scrum-projects and holds a certification of CSM respectively CSPO. Furthermore he needs to write a report on his experiences and judge those.
In order to be permitted as a Scrum Trainer the applicant has to turn in the following papers at the Scrum Alliance and needs to fulfill the following requests:
* A summary of the own experience with Scrum represented in a résumé
* A detailed description of the experience with giving trainings
* Own material for trainings
* References from at least two co-trainers he was doing a training with
* More papers that prove the quality of the applicant
Worldwide there are only 20 Scrum Coaches (in Germany only two: Andrea Tomasini, agile42 and Christoph Matthis), because the expectations for a certification are very high. An applicant has to fulfill the following qualifications:
* Prove at least 1500 hours Scrum-Coaching/- Consulting the last 5 years
* name two customers that are able to describe his coaching skills and prove them
* an extensive description of the projects and companies he introduced Scrum to
* an interview for the analysis and verification of the described procedures
a) Tim Listers Speech about agile leadership
b) Scrum Alliance Website
1) Marion Eickmann; Balance halten; Scrum; Part 1: Die Rolle des Product Owner; iX 8/09,S. 104