Scrum Framework for Agile Project Delivery Training Course

Course overview

Projects often lose momentum when teams adopt Agile language without applying Scrum accountabilities, events and artefacts with discipline. Product backlogs become unprioritised request lists, sprint commitments are made without a clear Sprint Goal, and Daily Scrums turn into status meetings for managers. This course equips participants to use the Scrum framework to create short feedback cycles, make delivery work visible and address obstacles before they become schedule, quality or stakeholder problems.

Participants work through the Scrum accountabilities of Product Owner, Scrum Master and Developers; the purpose and facilitation of Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective; and the use of the Product Backlog, Sprint Backlog, Product Goal, Sprint Goal and Increment. They learn to write and refine Product Backlog Items, apply relative estimation with story points and Planning Poker, establish a Definition of Done, manage workflow in Jira or Azure DevOps Boards, and use empirical evidence to guide release and stakeholder decisions.

Instructor-led briefings are combined with a running delivery simulation in which teams take a product from an initial product vision through multiple simulated sprints. Participants practise backlog refinement, estimation, sprint planning, review demonstrations and retrospective improvement actions. Each participant leaves with a practical Scrum delivery pack: a prioritised product backlog, Sprint Goal, sprint plan, Definition of Done, stakeholder review approach and a 30-day application plan for their own team or project.

The course suits professionals joining Scrum teams, project managers moving from predictive delivery approaches, product roles responsible for prioritisation, and leaders who need to govern Scrum work without undermining team autonomy.

Course objectives

By the end of this course, participants will be able to:

• Apply the Scrum Guide accountabilities, events and artefacts to a realistic product delivery scenario
• Create a Product Goal and prioritised Product Backlog using value, risk, dependency and learning criteria
• Write and refine Product Backlog Items with acceptance criteria and shared-ready conditions
• Estimate backlog work using story points, affinity estimation and Planning Poker
• Facilitate Sprint Planning that produces a Sprint Goal, selected backlog items and an actionable Sprint Backlog
• Use Definition of Done and Increment inspection to make product quality and completion transparent
• Run Sprint Reviews and Sprint Retrospectives that capture stakeholder feedback and measurable improvement actions
• Configure a basic Scrum board and reporting view in Jira or Azure DevOps Boards for sprint workflow visibility

Benefits of attending

Target competencies

Who should attend

• Project Managers — who need to lead delivery teams using Scrum rather than task-driven project controls
• Scrum Masters — who need practical facilitation techniques for Scrum events and impediment removal
• Product Owners — who prioritise product work and need to create decision-ready backlogs
• Business Analysts — who translate stakeholder needs into refinable Product Backlog Items and acceptance criteria
• Software Delivery Leads — who coordinate cross-functional development work and need predictable sprint feedback
• PMO and Delivery Managers — who need to govern Scrum initiatives using evidence without directing daily team work

Requirements and prerequisites

This is a foundation-to-intermediate course and does not require prior Scrum certification or experience as a Scrum Master, Product Owner or developer. Participants should be comfortable discussing a project, product or service they know and should understand basic workplace concepts such as stakeholders, requirements, deadlines and team roles. Familiarity with a work-management tool such as Jira, Azure DevOps Boards or Trello is helpful but not assumed. A complete beginner should expect to work with practical examples and participate actively in team exercises; coding, advanced project scheduling, Agile certification and specialist software administration are not required.

Training methodology

The course uses short instructor-led explanations anchored in the Scrum Guide, followed by team-based application in a continuing product-delivery case. Participants rotate through Product Owner, Scrum Master and Developer perspectives while creating backlog items, estimating work, planning a sprint and inspecting an Increment. Facilitated debriefs compare sound Scrum practice with common anti-patterns such as assigning work in the Daily Scrum or treating a Sprint Review as a presentation. Jira or Azure DevOps Board exercises make workflow visible, and the final workshop converts learning into a 30-day implementation plan.

Course outline

Day 1: Scrum foundations and empirical delivery

• Agile values and the limits of predictive project control
• Scrum theory: empiricism, transparency, inspection and adaptation
• Scrum Team accountabilities and cross-functional collaboration
• Product Goal and value-focused product delivery
• Scrum events, timeboxes and event purposes
• Scrum artefacts and their commitments
• Common Scrum anti-patterns and framework misuse

Workshop: Teams analyse a stalled delivery scenario and produce a Scrum operating model showing accountabilities, artefacts, events and escalation boundaries.

Day 2: Product backlog design and prioritisation

• Product vision, Product Goal and outcome framing
• Product Backlog structure and ordering responsibilities
• User stories, job stories and Product Backlog Item formats
• Acceptance criteria and example mapping
• Backlog refinement cadence and readiness signals
• Value-risk-dependency prioritisation techniques
• Story mapping for release and scope conversations

Workshop: Teams create a story map and prioritised Product Backlog for the case product, including acceptance criteria for the highest-value items.

Day 3: Estimation and sprint planning

• Relative estimation and the purpose of story points
• Planning Poker and affinity estimation methods
• Forecasting capacity without individual utilisation targets
• Sprint Planning inputs and the Sprint Goal
• Selecting Product Backlog Items for a sprint
• Creating an actionable Sprint Backlog
• Definition of Done and quality built into the Increment

Workshop: Teams estimate their refined backlog, establish a Definition of Done and produce a Sprint Goal and Sprint Backlog for a simulated sprint.

Day 4: Running the sprint and inspecting progress

• Daily Scrum purpose, structure and facilitation
• Workflow visualisation with Scrum boards
• Impediment identification and Scrum Master interventions
• Managing unplanned work and scope change during a sprint
• Increment creation and evidence of completion
• Sprint Review design and stakeholder feedback capture
• Jira and Azure DevOps Boards sprint reporting views

Workshop: Teams run a simulated Daily Scrum and Sprint Review using a board-based workflow, then produce an impediment log and stakeholder feedback record.

Day 5: Improvement, governance and workplace application

• Sprint Retrospective formats and psychological safety
• Root-cause analysis using Five Whys and fishbone diagrams
• Improvement experiments and action ownership
• Metrics that support empiricism versus metrics that distort behaviour
• Release forecasting and stakeholder expectation management
• Scrum governance, dependencies and multi-team coordination
• Thirty-day Scrum adoption planning

Workshop: Participants facilitate a retrospective, define improvement experiments and complete a 30-day Scrum application plan for a live or anticipated work context.

Tools & standards covered

Scrum Guide, Jira Software, Azure DevOps Boards, Miro

A typical training day

Live online deliveries follow the same structure in the East Africa Time zone, with shorter screen blocks and longer breaks.

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions