Actions and Detail Panel
Mon, Jun 19, 2017, 8:30 AM – Tue, Jun 20, 2017, 5:00 PM CDT
The agile Scrum development process continues to gain popularity across a wide variety of businesses and products. Educating the entire team(s) involved has a profound effect on kick-starting the process and resolving challenges that can be discovered within the course itself.
This two-day course, provides teams with the full context of what it means to be agile and how we can get there with the use of a core framework called Scrum. Many teams have individuals with experiences that are far and wide in the agile space; diluting a common understanding for your organization.
This course is designed to give teams a hands-on understanding of current agile concepts and how implementing the Scrum framework can actually accelerate their ability to ship software as frequently as the business desires. With the liberal use of exercises and discussions, team members learn why Scrum's seemingly simple processes can have a profound effect on the organization.
Teams will also learn practical advice they can leverage all the way from the trenches to the Executive offices. We focus on working with core Scrum techniques and activities; including the product backlog, sprint backlog, metrics, daily scrum meetings, sprint planning meeting, sprint review meeting, sprint retrospectives, and burn-down charts.
- Scrum Origins (What is agility and what problem is Scrum trying to solve)
- Scrum Roles (what are they, why are they there)
- Scrum Metrics (what metrics can we track to help us become better planners, we have an exercise that demonstrates this)
- Product Backlog (the genesis of a great scrum team, what is a product backlog, who manages it, and how is it created)
- Themes and Epics (how to organize around central ideas and concepts before diving into the details)
- User Stories (how to write user facing requirements to help the team solve the user’s problems while tracking acceptance and scope along the way)
- Estimating (general practices on estimating size/complexity of our backlog with the team)
- Sprint Backlog (the plan to turn the backlog into potentially shippable increment)
- Sprint Planning (using the sprint backlog to help us understand what the team can logically commit to completing based on their capacity, roles, etc…)
- Managing the Sprint (tools used to track progress during our sprint and how we synchronize our efforts, burn downs)
- Retrospectives (continuous improvement plans and techniques)
- Release Planning (long term planning with metrics and estimation, roadmap planning)
- Release Tracking (tracking progress against those long term plans with charts and burn downs and burn ups)