Certified ScrumMaster Training

This two day training is aimed at Product and Project Managers, Quality Managers and Testers, as well as Team Leaders and Developers. The training gives an understanding of the background and principles of Scrum. Scrum is a management framework for agile processes that helps to reorganize the "cooperation" between product management and development teams for software development projects. The participants will experience what a Scrum environment feels like, learn how ScrumMasters and coaches handle difficult situations, and receive a broad range of practical tips and methods.

Date, Duration	Location	Language, SEI Partner, Trainer
2010/05/03 2 days	Darmstadt, Germany	Deutsch, wibas, Trainer: Andreas Schliep + Peter Beck | GUARATEED DATE
2010/09/27 2 days	Darmstadt, Germany	Deutsch, wibas, Trainer: Andreas Schliep + Peter Beck

1.300 EUR per participant
1.200 EUR per participant for registration 6 weeks prior course start.

Pricing information is subject to change. All prices are excluding VAT.

Hotel accommodation costs are not included.
Our open training courses are limited to a maximum of 20 participants.

Why attend a Certified ScrumMaster Training?

Have you looked into Scrum, read an article or book on the subject? Do you have the feeling that one or two jigsaw pieces are missing in your understanding of the subject? Are you perhaps already working with a Scrum team, but feel that you are not really making any progress? Do you want to understand the background and principles of Scrum? Do you want to know what it feels like to be part of a Scrum team? Do you want to learn how ScrumMasters and coaches handle difficult situations?

The trainers Andreas Schliep und Peter Beck will take you through the ups and downs of the Scrum framework. Experience two exciting and informative days, after which many aspects will be clearer. Prepare yourself to lead your team to success as a Scrummaster.

Become a Certified ScrumMaster(tm) and join a worldwide movement!

Agenda

Day 1

• Introduction and getting to know one another
• Overview: objectives, what is Scrum?
• Agile versus traditional: values, principles, mindset
• Scrum ingredients: roles, meetings, artefacts
• Scrum background: where Scrum evolved from and how?
• Start using Scrum: from the vision to the Backlog to the first Sprint Planning

Day 2

• Product Owner: supporting the prioritization, planning and communication
• The Team: organizing self-organization
• The ScrumMaster: how can I adequately fulfill the role?
• Sprint Closure and Scrum Reporting: getting into the rhythm
• Typical Scrum problems: pitfalls and resistance
• Live Scrum 59
• Scrum Team Works: tools, scaling, techniques
• Me as a ScrumMaster: questions and answers
• And now?

80% theory and 20% practice

Prerequisites

You should have some practical experience of Scrum. Minimum prerequisite is having read one of the following books:

• Agile Software Development with Scrum; Ken Schwaber und Mike Beedle; Prentice Hall 2001
• Scrum - Agiles Projektmanagement erfolgreich einsetzen; Roman Pichler; dpunkt 2007
• Scrum. Produkte zuverlässig und schnell entwickeln; Boris Gloger; Hanser 2008

Results

The techniques learned and explored in this training will enable

Product or Project Manager

• to concentrate on the objectives and features when planning their projects
• to obtain an operational, tested and documented product version at regular intervals
• to see at all times how the development is really progressing
• to easily add changes and new features into the running project
• to efficiently plan and monitor even large projects

Quality Managers or Testers to experience

• that all stakeholders feel responsible for the quality of the end product
• that a close cooperation between requirements provider and developer avoids misunderstandings
• that Scrum provides a framework for continuous improvement
• that your work is requested and not shoved aside
• that quality management becomes an integral component of product development

Team Leaders or Developers to experience

• that they won't be instructed precisely how things must be done
• that they can bring their ideas to be implemented, and somebody makes sure that their arguments are heard
• that somebody defends the team against constant reprioritizing and hindering of their work
• that somebody clears obstacles in the team's path whose job it is to develop software
• that it is no longer necessary for anybody to hear someone say at the project end "I told you so right from the start!"

Training material

In this training course you will receive:

• The book "Scrum - Agiles Projektmanagement erfolgreich einsetzen" (in German) by Roman Pichler

• The training materials - these will be distributed to the participants after the training as a PDF.