Professional Scrum Master
Taught by Simon Kneafsey
June 20-21, 2013 in London, United Kingdom
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.
Ken Schwaber initially designed the PSM course in 2009 as a significant update of the Certified ScrumMaster (CSM) course that he created in 2002. Since 2009, the PSM course has been maintained and regularly enhanced by Scrum.org through contributions from Ken and other experts in the Scrum.org network of Professional Scrum Trainers.
After class, attendees will have 14 days to take the Professional Scrum Master I online assessment, which consists of 80 multiple choice questions. If they score 85%, they will receive PSM I certification. The cost of the first attempt is included in the price of the PSM class.
Registration for this class has closed.
This two-day course covers the following:
- Scrum Basics. What is Scrum and how has it evolved?
- Scrum Theory. 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. 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?
- Scrum Planning. 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.
- Scaling 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?s. How is scaling best accomplished using Scrum?