“The ScrumMaster is responsible for ensuring that the Scrum Team adheres to Scrum values, practices, and rules. The ScrumMaster helps the Scrum Team and the organization adopt Scrum. The ScrumMaster teaches the Scrum Team by coaching and by leading it to be more productive and produce higher quality products. The ScrumMaster helps the Scrum Team understand and use self-organization and cross-functionality. The ScrumMaster also helps the Scrum Team do its best in an organizational environment that may not yet be optimized for complex product development. When the ScrumMaster helps make these changes, this is called “removing impediments.” The ScrumMaster’s role is one of a servant-leader for the Scrum Team.”
– From the Scrum Guide, Scrum.org
This course teaches the participant how to set up and adhere to the principles and process of Scrum. Participants will learn how to work with Product Owners to create Product Backlogs and plan Sprints, work with the team to break down Backlog items into prioritized tasks. In addition, participants will learn the right methods, logistics and metrics needed to execute and track the release and Sprints and bring it to a successful customer review. Most importantly, this course will discuss the ScrumMaster’s role, not as a project manager, but as a change agent within the organization. Finally, the participants will learn how to use these skills within a large-scale, distributed environment. The course includes instructor experiences, case studies, and several in-class labs will enable participants to build knowledge and skills through active participation instead of simply lectures.
Upon completion of this course, the participant will be a certified as a Certified Scrum Master from the Scrum Alliance.
Topics:
- Overview of Scrum for product development
- Fundamental tenants of Scrum
- Transparency
- Inspection
- Adaptation
- Roles and responsibilities
- Product owner
- ScrumMaster/change Agent
- Feature team
- Q/A’s role within Scrum
- The development manager’s new role
- Creating the product backlog
- Emergent requirements
- User stories
- Story format
- Conditions of satisfaction (Acceptance criteria)
- Epics
- Complex stories
- Vertically slicing stories
- Compound stories and spikes
- Brief look at Use Cases
- Release planning
- Estimating
- Accuracy and precision
- Sprint length considerations
- Establishing velocity
- Time and feature-driven releases
- Assembling the initial release plan
- Finalizing the initial release plan
- Working within iterations
- The definition of ‘team’
- Sprint planning part 1
- Commitment-driven
- Velocity-driven
- Defining tasks
- Creating the sprint backlog
- Sprint planning part 2
- Executing the spring
- Development during a sprint
- Testing
- Visual management
- Handling interruptions
- Holding daily Scrums
- Rules for cancelling a sprint
- Rules for escalation
- Iteration reviews
- What’s done should be ‘done’
- The ScrumMaster as the ‘Servant Leader’
- Scaling Scrum and product ownership
- Working over multiple locations
- Outsourcing and globalization
Anyone
