Course Description

This 2-day Scrum and Agile Practices training course is designed to provide an honest, independent perspective of Scrum that arms participants with sufficient understanding to decide on the next step for their organisation. One of the features of the course is its clear explanation of the relationship between Scrum and other popular agile practices. The course is delivered by a Certified Scrum Master with many years of experience in the software industry.

This course is ideal for educating large groups about Scrum, as a pre-requisite for further training or to kick-start an organisation’s first Scrum project. The course can also serve as a component of a comprehensive change management program for introducing Scrum into an organisation.

The use of Scrum and agile practices to manage software development is becoming wide-spread.  Many people are aware of Scrum and would like to find out more or evaluate its suitability for their organisations.


Familiarity with business environments and business information systems.

Who is this course for?

  • Chief Information Officers (CIO), Executives, Enterprise Architects
  • Process Engineers, Software Engineering Process Group (SEPG) Staff, Methodologists, Process Improvement Staff
  • Business Analysts, Business Systems Analysts, Systems Analysts, Functional Analysts
  • Software Development Managers, Software Engineers, Software Developers, Requirements Engineers, Requirements Analysts
  • Test Managers, Test Engineers, Testers, Quality Assurance Staff
  • Project Sponsors, Project managers, Program Managers

Further Training

Course content

History of Agile Practices
Problems with the waterfall life cycle model
The history &  philosophy of Agile methods
The “Lightweight” approaches of the 1990’s
The Manifesto for Agile Software Development
Some popular Agile methods
eXtreme Programming (XP)
Dynamic System Development Method (DSDM)
Feature Driven Development (FDD)
The Agile approach as an alternative to the waterfall life cycle model
Introduction to Scrum
History & philosophy of Scrum
The New Product Development Game
Ken Schwaber & Jeff Sutherland at OOPSLA ’95
“Inspect and adapt” as the underlying Scrum philosophy
The Scrum life cycle
Scrum roles
Product Owner, Scrum Master, Team
Other roles
Stakeholders, Subject Matter Experts (SMEs),Managers
Scrum work products
The Product Owner & Product Backlog
The product backlog as a project “to-do list”
Product Backlog Items
Software features vs. software requirements
Creating, refining & prioritising the Product Backlog
Characteristics of a good Product Backlog (DEEP)
Responsibilities of the product owner
Why is the Product Owner required?
Understanding Scrum Sprints
Sprint Planning
Understanding “velocity”
Creating the Sprint Backlog
Removing obstacles to progress
Tracking progress during the Sprint
The Potentially Shippable Product Increment and the definition of “done”
The Sprint Review
Responsibilities of the team
Responsibilities of the Scrum Master
The Sprint Retrospective
Agile Practices Supporting Scrum
Agile practices as the “enablers” of Scrum
User Stories
Test-Driven Requirements
The Planning Game
Test-Driven Development
Continuous Integration
Test Automation
Implementing Scrum & Managing Change
The ADKAR change management model & Scrum
The dangers of “Scrum-But”
Creating a Scrum change “roadmap”