Official certification training for the Professional Scrum Master according to Ken Schwabers Scrum Organisation (Scrum.org)
The Professional Scrum Master (PSM) course teaches the principles and empirical process theory underlying Scrum, with the aim of giving participants a solid foundation in Scrum and its core principles so that they can make decisions based on how best to use what they have learned in the context of their organization. Participants will learn the advantages and disadvantages of certain decisions and why some support agility and ultimately lead others back to a waterfall like process. In addition, you will learn how productivity metrics can be used in Scrum to make the consequences of decisions transparent and to optimize them. This Scrum training is not only about the Scrum Master certification, but also about "mastering Scrum". This Scrum Master Seminar has absolute workshop character. The participants learn through many practical exercises what Scrum is and how successful agile product and software project management is operated with the Scrum principles such as self-organization, "time boxing", retrospectives etc.. After this Scrum training the participants can assess which tasks the different roles Scrum Master, Development Team and Scrum Product Owner have and which purpose the Scrum events like the Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective serve. The typical quality mechanisms in Scrum, such as the Definition of Done, are examined in more detail. Furthermore, the participants will master the optimal handling of the Scrum product backlog, sprint backlog and release planning in Scrum. You will also learn to fulfill the role of the Scrum Master in large Scrum projects with several teams.
- Scrum basics - What is Scrum and where does it come from (History of Scrum)
- Scrum theory - Why does Scrum work and what are its principles? How do they differ from more traditional approaches and how does that affect Scrum
- Roles, rules and the Scrum flow? - How can you put scrum theory into practice by using timeboxes, roles, rules and artifacts? How do you use them most effectively and when don't they work?
- Teams - How do you put teams together? Which team dynamic processes should be considered? What impact does this have on productivity?
- Emergent Architecture - Scrum is an empirical process. What are the consequences of empiricism and emergence on complex architectures and infrastructure development?
- Done and Undone - What is the "Increment" and when is it "done"? What happens to residual work and unfinished functionalities? How does this affect the overall project?
- Scrum Planning and Reporting - How do you plan a project and estimate its costs and completion time?
- Change - Scrum is different. What does this mean for my project and my organization? What is the best way to implement Scrum in terms of expected changes?
- Scaling Scrum - Scrum works great with a single team. It also works better than anything else for projects or products that involve hundreds or even thousands of people all over the world. What is the best way to do this?
- The Scrum Master - What exactly does the Scrum Master do? What happens if the Scrum Master takes on other roles?