2-Day Course with Add-on Options

After taking this course, participants will understand:

• What Scrum is
• How to manage Scrum projects
• How to manage requirements in Scrum projects
• How to use Planning Poker for story estimation
• The different roles within a Scrum team
• The role of the Scrum Master
• The role of the Product Owner
• The limitations of Scrum
• How to scale Scrum to multiple teams

Many organizations are moving to agile methods and Scrum, in particular, for many reasons including the reality of changing customer requirements, the need to deliver value quickly to customers, and respond to competitive pressures. Scrum has a solid track record and has become a fixture in the agile practices.

Scrum in a Nutshell

1. Developing (and potentially delivering) software in stages
2. Having a Scrum Master manage the product backlog (items to be developed)
3. Having a Product Owner (representing the customer) prioritize these items
4. Empowering teams to develop high quality, valuable software quickly 

The Scrum Process and Roles

This course prepares entire teams to begin undertaking Scrum practices in their software development projects. It covers all of the roles within the Scrum process and focuses on how your development team can adopt Scrum—one step at a time. With a combination of interactive lectures and a significant amount of time spent on hands-on exercises, your team will learn about and practice the complete Scrum process.

Note: We highly recommend including consulting and coaching services with any of these training offerings, especially if your teams have little or no prior Scrum experience.
 
Follow-up Training and Coaching Options

Extended Course Exercises—1 day – Add an additional day of exercises immediately after the two-day training class to ground the team in iteration planning, story breakdown, and story estimation.
Intensive Coaching—4 days – Follow the two-day training class with four days of coaching, delivered over the next several weeks:

• One day: on-site coaching, immediately after the training to assist the team in preparing for their first sprint
• Half day: virtual coaching halfway through the first sprint to improve the team’s process
• Two days: on-site coaching on the last day of the first sprint and the first day of the second sprint to accelerate the team’s progress
• Half day: virtual coaching one week into the second sprint to ensure the team is on the right track

Multiple Team Environments

For multiple team environments, we offer a 3-day version of Implementing Scrum for Teams to prepare your teams to implement Scrum and work across multiple teams. In addition to the topics in the core course, participants will learn how to:

• Use an advanced visual control for managing the work across teams
• Integrate multiple teams so that they work together effectively
• Create an integration team that goes well beyond Scrum of Scrums
• Minimize technical dependencies between teams 

Who Should Attend?

This course is appropriate for software developers, testers, QA analysts, business analysts, product managers, program managers, and project managers who are members of teams transitioning to Scrum. It is advantageous for all those on the development team and related to the development team to attend. It is ideal for higher-level management to participate and contribute both to the course and the transition.