Professional Scrum Master™ I

Curriculum

1. The Scrum Framework
Scrum theory includes time-boxing, and specific roles, rules, and artifacts. All elements of Scrum complement each other to form a consistent whole. All work is performed in Sprints. All base rules, events, and roles are described in the Scrum Guide, the acknowledged Scrum body of knowledge. Each part of Scrum ties back to the principles and theory.

After completing this module, students will be able to:

Explain why the artefacts, roles and events in Scrum are all important to a successful Scrum project.
Discover suitable process within the Scrum framework for their organisation.

Topics:

• Scrum Events: Every event in Scrum is an inspect and adapt opportunity. How are these events important? What are the impacts of missing one of these?
• Scrum Role: Every role in Scrum has specific accountabilities. What are their accountabilities? Why are they important? How are they different to traditional project management roles?
• Scrum artefacts: Every artifact in Scrum is transparent so organisation can inspect and adapt based on it. Why are these artefacts important?
• Sprint: The Sprint is the heartbeat of the Scrum framework. What is a Sprint? What are the criteria of a successful Sprint?
• Hands-on Exercises:
• Students will collaborate with other students to define a process within the Scrum framework.

2. Scrum Philosophy and Principles

Scrum is founded on empirical process theory to deal with the complexity typical to software development. All principles and values of Scrum are based on the fundamental view of software development as creative and complex work.

After completing this module, students will be able to:

Explain what is Agility and the relation to Scrum.
Discover where Scrum is not suitable.
Understand the impact of the transparency that Scrum brings and requires, and how Scrum is best used to increase an organization’s agility.
Explain how Scrum implements empiricism in software development.

Topics:

• How is empirical approach different to defined approach?
• What makes Scrum different to traditional project management approach?
• What is Agile?
• How does Agile relate to Scrum?
• Why should we be Agile and use Scrum?
• In what case is Scrum not suitable?

3. Scrum Planning

Scrum Planning is different from traditional project management. Students will exercise tactics on planning in Scrum.

After completing this module, students will be able to:

Understand Product Backlog and Sprint Backlog
Learn planning tactics

Topics:

• Product Backlog and Sprint Backlog: The Product Backlog and Sprint Backlog is the plan in Scrum. How is planning in Scrum different traditional project management? What is the best practice to do Lean Planning in Scrum? How to do Product Backlog Refinement?
• Product Backlog Management: Product Backlog reflects the roadmap of the Product. How do we do Product Backlog management in Scrum?
• Product Backlog Ordering: Prioritization is one way to order Product Backlog. What are the other techniques to order the Product Backlog?
• Product Backlog Decomposition: Product Backlog is decomposed so that it can be done in one Sprint. How do we decompose Product Backlog to ready to execute Sprint Backlog?

4. Quality and Definition of Done

The criteria of success in Scrum are different to traditional project management.

After completing this module, students will be able to:

Define what is required for high-quality software.
Discover what documentation is required in Scrum.

Topics:

• Definition of Done: Everyone in the organisation should have the same understanding about “DONE”. What is “DONE”? What is the impact of not having “DONE” software every Sprint?
• Quality: What is required for a high-quality software? Does Scrum need documentation?

Hands-on Exercises:

In this module students will learn:
List techniques and documentation that is required for Scrum project.

5. Cross-Functional, Self-Organizing Teams

Scrum Teams are self-organizing and cross-functional; which is very different from traditional development groups. Scrum Teams are empowered to do the right thing.

After completing this module, students will be able to:

Discover what is required to generate a self-organising team.
Get Scrum teams going, guide them along the way and help them continuously self-develop to become successful through better collaboration.
Form a Scrum team.

Topics:

Creating self-organizing teams

6. Coaching and Facilitation

Scrum Masters are servant-leaders, with skills and tools to coach teams and organizations in understanding and applying Scrum. They master several techniques for coaching, conversation, and facilitation in order to help people, teams, and organizations discover what works best for them.

After completing this module, students will be able to:

Understand the people aspect of Scrum, how to work with people.
Discover coaching techniques that is appropriate for the team.

Topics:

• Coaching Techniques
• Facilitation Techniques

7. The Scrum Master

After completing this module, students will be able to:

Identify who is the Scrum Master.
Explain what makes Scrum Master different to traditional Project Manager.
Discover skills and traits are required for Scrum Master to be successful in his role.

Topics:

This course put emphasizes on one of the roles in Scrum – the Scrum Master.
Scrum Masters are servant-leaders with distinct skills.

8. Assessment and Certification

Learning Objectives:

On completing this module students will understand aspects of the certification.
The Professional Scrum Master course has two associated assessments and certification: Professional Scrum Master level I (PSM I) and Professional Scrum Master level II (PSM II).
All participants completing the Professional Scrum Master course receive a password to take the PSM I assessment and are entitled to a discount on the PSM II assessment.
These industry-recognized certifications require a minimum passing score on the associated rigorous assessment.

Topics:

• Certification Prerequisites
• Certification Exam