Course Code: 5476

Scrum Team Workshop

Class Dates:
3 Days
Class Time:
Instructor-Led Training, Virtual Instructor-Led Training


  • Course Overview
  • The application of Agile principles and practices on software development projects enables a project team to quickly develop working software that meets business needs. In Scrum, teams work in 2-4 week Sprints to produce production-quality software driven by business priorities using an empirical, adaptive approach. This course provides an in-depth understanding of how Agile and Scrum teams deliver business value.

    You will learn to apply the basic practices of any Agile approach, with a focus on Scrum. You will apply what you learn in a series of exercises that take you through project start-up, project/release planning, Sprint planning, and Sprint execution. Participants will build and manage a Product Backlog, a Sprint Backlog and a Release Plan.

    The course can be modified to use real-life examples and situations from the students’ own experiences.

  • Audience
  • This course is intended for anyone who will actively participate in a project using this approach. People on the edges of the project (secondary customers, management staff, and participants in related processes) will also benefit. Project teams are encouraged to attend as a group.

    •Apply key concepts and terms of Agile and Scrum to project situations
    •Be able to explain the methodology’s benefits and key techniques
    •Experience the progression of key activities and artifacts
    •Have a deep understanding of different practices that can be applied and when to apply them
    •Be able to help others to understand and apply the practices and principles
    •Prepare to participate in an upcoming project


  • A basic understanding of Scrum

Course Details

  • Agile Fundamentals
  • •What are agile practices and principles?
  • •What is “iterative and incremental” development?
  • Scrum Fundamentals
  • •What is Scrum?
  • •Scrum Roles and responsibilities
  • •What is a Product Backlog?
  • •What is a Sprint Backlog?
  • •What is a User Story?
  • Requirements
  • •How to identify and write good User Stories
  • •Use Cases on an Agile project
  • •Non-functional requirements
  • •Evolution of requirements during a Sprint
  • •Evolution of requirements during a project
  • Project Initiation
  • •Getting started- who, what and how?
  • •Sprint 0
  • •Spikes
  • •Team Rhythm Calendar
  • Estimation and Prioritization
  • •Creating the initial Product Backlog
  • •Agile Estimation Overview
  • •Different ways to do Agile estimation
  • •Prioritization- who, what, why and when?
  • •Definition of ”Done”
  • Release Planning
  • •What is Release planning?
  • •How is an Agile release plan different from a traditional release plan?
  • •Methods for creating a release plan on an Agile project.
  • Planning a Sprint
  • •Conducting Sprint Planning Meeting Part 1
  • Selecting a subset of the product backlog
  • Determining the Sprint scope
  • •Conducting Sprint Planning Meeting Part 2
  • Developing the Sprint backlog
  • Sprint tasking and estimation
  • Running a Sprint
  • •Conducting the daily Scrum
  • •Managing the Sprint scope
  • •Tracking progress; recognizing problems
  • Closing a Sprint
  • •Conducting a Sprint review
  • •Conducting a Sprint retrospective
  • •Reporting project status
  • •Updating the backlog
  • •Closing the Sprint
  • Managing the Product Backlog and Release Plan
  • •How does the Product Backlog change during a project?
  • •How do you control changes?
  • •How does the Release Plan change during a project?
  • Agile Software Engineering
  • •Application of typical Agile Software Engineering practices such as Continuous Integration, Test Driven Development and Pair Programming
  • •Survey of tools available to support an Agile Project
  • Agile Testing
  • •Testing during the Sprint
  • •Roles/responsibilities in testing:
  • Developers
  • Team testers
  • Product Owner
  • Independent test group
  • •Testing tools