Agile Foundations for Product & Delivery Leaders
Master Agile principles and lightweight frameworks to lead product delivery without diving into developer practices.
- 22 hours
- Stage: First job: projects, agile, product
- Language: English
- Voice: English ✔

What you will learn
- Explain the Agile Manifesto values and 12 principles, applying each to an everyday product or delivery decision.
- Differentiate Scrum, Kanban and Lean leadership approaches, and choose the one that best fits a given team's work and context.
- Define the responsibilities of Product Owner, Product Manager and Scrum Master, and show how their accountabilities complement and differ from one another.
- Facilitate key ceremonies: Sprint Planning, Daily Stand-up, Review & Retrospective, keeping each to its purpose, timebox and expected outcome.
- Manage and prioritize both Product and Flow backlogs using MoSCoW and WSJF techniques, and explain the ranking to stakeholders.
- Use metrics (velocity, throughput, cycle time) to inform planning and continuous improvement, avoiding their misuse as individual performance targets.
Syllabus
Module 1Why Agile Exists3 hours
Agile Manifesto values · the 12 principles · early delivery · welcoming change · delivery risk · Agile vs predictive and hybrid
- The Agile Manifesto — four values and the problem each answers
- The 12 principles grouped into themes
- A principle-to-decision checklist for everyday choices
- How risk hides in long plan-driven projects
- Early delivery and welcoming change in practice
- Case: one project run two ways
- Predictive, Agile and hybrid — how each one works
- Choosing an approach — a fit checklist
- Case: when Agile is the wrong choice
Module 2Lean Thinking and Flow3 hours
Lean principles · systems thinking · types of waste · value stream map · Kanban board · work-in-progress limits
- Where Lean and systems thinking come from
- Eliminate waste, limit work in progress, optimize the whole flow
- Case: a team that improved by starting less
- The types of waste in delivery work
- Drawing a value stream map step by step
- Case: finding waste from request to release
- Why limiting work in progress improves flow
- Building a Kanban board — columns, policies and limits
- Case: a support team before and after limits
Module 3Scrum, Kanban and Delivery Roles3 hours
Scrum events · artifacts and commitments · Scrum vs Kanban vs Lean · Product Owner · Product Manager · Scrum Master
- The Scrum framework in one page
- A one-page Scrum cheat sheet
- Walking through one sprint of a real product team
- Scrum, Kanban and Lean — what each one controls
- A comparison grid for choosing an approach
- Case: three teams, three different fits
- Product Owner, Product Manager and Scrum Master accountabilities
- A role-clarity chart for a real team
- Case: when two roles blur and the team stalls
Module 4Backlogs, Stories and Priorities3 hours
epics and user stories · acceptance criteria · Definition of Done · product and flow backlogs · MoSCoW · WSJF
- Epics, user stories and acceptance criteria — from idea to task
- Writing a user story and splitting an epic
- Case: turning a vague idea into ready backlog items
- What a Definition of Done is and why teams need it
- Drafting a Definition of Done with a team
- Case: a story that was done but not finished
- Product backlog and flow backlog — what each one holds
- Ranking with MoSCoW and WSJF — a scoring sheet
- Explaining a ranking to stakeholders
Module 5Running the Team Day to Day3 hours
team boards in Jira, Trello and Azure DevOps · Sprint Planning · Daily Stand-up · Review and Retrospective · servant leadership · impediments
- Why visible work matters
- Setting up a board in Jira, Trello or Azure DevOps
- Case: reading a board to find stuck work
- The purpose, timebox and outcome of each ceremony
- Facilitation guides and agendas for each ceremony
- Case: a stand-up that became a status meeting
- Servant leadership versus command-and-control
- Removing impediments — an impediment log and daily routine
- Case: a leader who stopped directing and started clearing the way
Module 6Metrics, Forecasts and Reporting3 hours
velocity · throughput · cycle time · forecast ranges · sprint reviews · roadmaps
- Velocity, throughput and cycle time — what each one measures
- Charting team metrics from a board or tracker
- Case: when a metric became a target
- Why a range is more honest than a single date
- Building a forecast range from velocity or throughput
- Case: explaining a forecast to a worried stakeholder
- What stakeholders need in order to trust progress
- Templates for sprint reviews, roadmaps and release forecasts
- Case: a roadmap update that kept a sponsor on board
Module 7Adopting Agile Well and Growing4 hours
adoption mistakes · team health checks · adoption case study · ethical practice · sustainable pace · career paths
- Common adoption mistakes and why they happen
- A team health check and a correction plan
- Case: a team running mini-waterfall sprints
- How to study an adoption story
- A case worksheet — what worked, what failed and why
- Case study: a delivery team adopting Agile step by step
- Honest reporting, sustainable pace and respect
- An ethics check for status reports and workload plans
- Case: pressure to hide a slipping date
- The Agile career map — Scrum Master, Product Owner, Product Manager
- Building a personal learning plan with milestones
- Case: two learners, two paths from the same foundation