| Course Abstract: |
Learn the basics of Scrum’s project management approach which will give you the ability to quickly develop working software that meets business needs. In Scrum, teams work within time-boxed sprints to produce production-quality software driven by business priorities and using an empirical, adaptive approach. This course explains this approach’s values, key techniques, and how each team member contributes to success.
You will learn how to build a product backlog with user stories as input, and how to plan and work in 30 day sprints. You will apply what you learn in a series of exercises that take you through project start-up, sprint planning, and running a sprint. |
| Course Topics: |
Scrum methodology fundamentals
Intro to Scrum/benefits vs. waterfall
Brief history of Scrum, comparison to waterfall, advantages of Scrum.
What is iterative development?
Covers the basics and principles of iterative development and industry accepted best practices.
Sprints – goal, structure, scope
Describes what typically occurs in a sprint, the purpose of a sprint, what teams are expected to accomplish within a sprint.
Roles and responsibilities – The ScrumMaster Project Team
Covers the roles played within a project team, with an emphasis on the ScrumMaster.
Project initiation and release planning
Role of the product owner
Lays out the responsibilities and expectations of the product owner and his/her relationship to the project team.
Establishment of project charter
Overview of basis for scope of work, starting point for product backlog. Describe other project initiation activities.
Product backlog
Definition of the product backlog, how it is established. Demonstrate how to size stories.
Exercise: Build a product backlog
Allow participants to go through the steps of establishing the product backlog and size stories.
Setting priorities
How the product backlog gets prioritized and maintained. Focus is on the role of the product owner.
Release planning
Demonstrate how to use prioritized backlog, estimated velocity, and sprint goals to establish a release plan.
Planning a sprint
Conducting Sprint Planning Meeting
Part 1: Selecting a subset of the product backlog
Discuss how to determine the sprint scope including hangover.
Part 2: Developing the sprint backlog
Discuss how to avoid hangover, estimate velocity, and establish a sprint goal, establish spikes and technical stories.
Exercise: Build a sprint backlog
Students will be provided a product backlog and preliminary release plan, to build a sprint backlog
Developing sprint tasks
Topics covered include task granularity, dependencies, scheduling and assignment.
Exercise: Establish sprint plan tasks
Students will create and plan iteration tasks to include spikes and technical stories.
Running a sprint
Conducting the daily Scrum
Discuss the focus and conduct of the daily Scrum. Learn what is included and what is excluded. Learn the value of the daily Scrum.
Managing the sprint scope
Discuss tips and techniques for insulating the team from distractions. Learn how to handle the sprint being behind or ahead.
Warning signs and how to address them
Covers common pitfalls and avoidance strategies and recipes for failure.
Tracking progress/burndown
Methods for managing task completion. Covers burndown and progress tracking.
Exercise: Build and maintain burndown (59 minute Scrum)
Students break into teams and simulate an actual sprint. They plan the sprint, create tasks, status the tasks, and hold daily Scrums all within 59 minutes.
Closing a sprint
Conducting a sprint review
Demonstrate what is expected and covered in a sprint review.
Conducting a sprint retrospective
Discuss the purpose and scope of a sprint retrospective.
Inspecting and adapting the process
Discuss a key aspect of Scrum: inspect and adapt. Emphasizes the importance of self-directed teams.
Reporting project status
Discuss metrics, hangover, and velocity.
Updating the backlog
Covers re-prioritization, injects and budget constraints.
Closing the project
Summarization and definition of done.
© 1994-2008 IconATG |