Agile & Stakeholder Delivery: sprints and communication

01

When agile fits, and when hybrid is smarter

In simple words

If you bake a cake from a recipe you know, you follow the steps. If you invent a new cake, you bake a small one, taste it, and change the recipe. Agile is the "small cake, taste, change" way. Many real projects mix both.

Key facts

Before this course: Project Management in Practice: schedules, risks and tools (course 8.4.2). You should already be able to build a scope baseline, a critical-path schedule, an earned value report and a scored risk register. In course 8.4 you met the four Agile values and the basic Scrum roles and events. This course goes deeper into agile delivery and stakeholders and does not repeat those basics.
The Manifesto for Agile Software Development has 12 principles behind its four values. Some of the most useful for a project manager:
Welcome changing requirements, even late in development.
Deliver working results frequently, from a couple of weeks to a couple of months, preferring the shorter timescale.
Business people and developers work together daily.
Working results are the main measure of progress.
Keep a sustainable pace the team can keep up indefinitely.
At regular intervals the team reflects and adjusts how it works.
Scrum is built on empiricism: decisions based on what is observed. Its three pillars are transparency, inspection and adaptation (Scrum Guide 2020).
A simple fit check (a rule of thumb, not a law):

Question	Points toward predictive	Points toward agile
Are requirements clear and stable?	Yes	No, they will be discovered
Can the result be delivered in usable pieces?	No (for example, a bridge)	Yes (for example, an app or a training course)
Can a customer or user give feedback often?	Rarely	Every few weeks or more
Is the cost of changing your mind late high?	Very high	Low or medium

Hybrid means using both: for example, a predictive plan with fixed milestones for a building fit-out, and agile sprints for the booking website inside the same project. Many organisations work this way.
Agile does not mean "no plan." It means planning often, in smaller pieces, and changing the plan with evidence.

Step by step

Write at the top of your page: "Before this course: Project Management in Practice (course 8.4.2)." List the documents you already have from that course.
Pick one real project (2 to 8 weeks of work) for this whole course.
Answer the four fit-check questions for your project and write one sentence for each answer.
Split the project into parts. Mark each part P (predictive) or A (agile).
For each A part, write who will give feedback and how often.
For each P part, write the fixed milestone that must not move.
Write a two-sentence approach statement for your sponsor.
Check: someone else can read your statement and say which parts are agile and why.

LESSON 01When agile fits, and when hybrid is smarter

LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00

Voice

Read the video script

[Host] "Agile is not a religion. It is a tool for work that is uncertain."
[Text on screen: Clear and stable? Deliver in pieces? Feedback often?] "Ask three questions. If requirements will be discovered, the result can come in pieces and users can give feedback often, agile fits."
[Screen: project split into P and A parts] "Most real projects are hybrid: fixed milestones where change is costly, short cycles where learning matters."
[Text on screen: Transparency, Inspection, Adaptation] "Whatever you choose, make the work visible, inspect it often and adapt."

Try it now

Run the fit check on your project, split it into predictive and agile parts, and write the two-sentence approach statement. Show it to one person and ask if the reasons make sense.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Agile & Stakeholder Delivery: sprints and communication" on The Future Market. Lesson 1: "When agile fits, and when hybrid is smarter".

What the lesson teaches:
- Before this course: Project Management in Practice: schedules, risks and tools (course 8.4.2). You should already be able to build a scope baseline, a critical-path schedule, an earned value report and a scored risk register. In course 8.4 you met the four Agile values and the basic Scrum roles and events. This course goes deeper into agile delivery and stakeholders and does not repeat those basics.
- The Manifesto for Agile Software Development has 12 principles behind its four values. Some of the most useful for a project manager:
- Welcome changing requirements, even late in development.
- Deliver working results frequently, from a couple of weeks to a couple of months, preferring the shorter timescale.
- Business people and developers work together daily.
- Working results are the main measure of progress.
- Keep a sustainable pace the team can keep up indefinitely.

The exercise I'm working on:
Run the fit check on your project, split it into predictive and agile parts, and write the two-sentence approach statement. Show it to one person and ask if the reasons make sense.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.

I'm a parent helping my child (about 8 years old) with a lesson called "When agile fits, and when hybrid is smarter" from the course "Agile & Stakeholder Delivery: sprints and communication".

Here's what the lesson says:
If you bake a cake from a recipe you know, you follow the steps. If you invent a new cake, you bake a small one, taste it, and change the recipe. Agile is the "small cake, taste, change" way. Many real projects mix both.

The activity:
Run the fit check on your project, split it into predictive and agile parts, and write the two-sentence approach statement. Show it to one person and ask if the reasons make sense.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.

Open Claude

Sources

Principles behind the Agile Manifesto: agilemanifesto.org/principles.html
The Scrum Guide (2020): scrumguides.org/scrum-guide.html

My notes

I learned this

02