Participants will be able to make the most of the class if they:
- Have studied the Scrum Guide (required).
- Understand the basics of project management.
- Understand requirements and requirements decomposition.
- Have been on or closely involved with a project that builds or enhances a product.
- Have read one of the Scrum books.
- Want to know more about how Scrum works, how to use it, and how to implement it in an organization.
The Professional Scrum Master (PSM) course provides information and tools that you can use to ensure that Scrum is understood and enacted well by your team. This course covers Scrum basics, including the framework, mechanics, and roles of Scrum. But it also teaches how to use Scrum to optimize value, productivity, and the total cost of ownership of software products. Students learn through instruction and team-based exercises, and are challenged to think on their feet to better understand what to do when they return to their workplaces.
The PSM course was initially designed in 2009 as a significant update of the Certified ScrumMaster (CSM) course created in 2002. Since 2009, the PSM course has been maintained and regularly enhance through contributions from experts in the Scrum network of Professional Scrum Trainers.
Each instructor brings his or her individual experience and areas of expertise to bear, but all participants learn the same core course content. This improves their ability to pass the Professional Scrum Master assessments and apply Scrum in their workplaces.
This course is specifically targeted to Scrum Masters, but the lessons are applicable to anyone in a role that supports a software development team's efficiency, effectiveness, and continual improvement. If you are responsible for the successful use and/or rollout of Scrum in a project or enterprise, this course is likely to be a good fit.
Upon completion of this course, participants will be able to:
- Understand Scrum and its evolution
- Know Scrum principles and theory
- Glean the optimization of Total Cost Ownership
- Recognize success of teams
- Conduct planning and estimation
- Make prediction and assess risk
- Understand scaling using Scrum
What is Scrum and how has it evolved?
Why does Scrum work and what are its core principles? How are the Scrum principles different from those of more traditional software development approaches, and what is the impact?
Scrum Framework and Meetings
How Scrum theory is implemented using time-boxes, roles, rules, and artifacts. How can these be used most effectively and how can they fall apart?
Scrum and Change
Scrum is different: what does this mean to my project and my organization? How do I best adopt Scrum given the change that is expected?
Scrum and Total Cost of Ownership
A system isn’t just developed, it is also sustained, maintained and enhanced. How is the Total Cost of Ownership (TCO) of our systems or products measured and optimized?
Scrum Teams are self-organizing and cross-functional; this is different from traditional development groups. How do we start with Scrum teams and how do we ensure their success?
Plan a project and estimate its cost and completion date.
Predictability, Risk Management, and Reporting
Scrum is empirical. How can predictions be made, risk be controlled, and progress be tracked using Scrum. Discussion starts with "Done and Undone" and continues with Quality Assurance in Scrum.
Scrum works great with one team. It also works better than anything else for projects or product releases that involve hundreds or thousands of globally dispersed team members. How is scaling best accomplished using Scrum?