4.1Agility & the Agile Manifesto
The essentials in 30 seconds
- Agility = moving in short cycles while adjusting to feedback, when needs are uncertain.
- Iterative (repeating short cycles) + incremental (delivering value each time).
- Reflex: the Agile Manifesto (2001, 4 values, 12 principles) favours adaptation over a fixed plan.
Running case — Bilal drops the fixed plan
Bilal steers a project in Algiers whose needs change every month: his detailed 12-month plan is wrong by week 3. With his client, he decides to work differently: short cycles, a demo each time, and adjust. This is the start of his agile shift — which we will follow through to the tools (4.5).
This same case runs through the lesson, the diagram, the script and the 48h challenge — and continues in 4.2, 4.3, 4.4 and 4.5.
1. Born of uncertainty
Agility was born in software development from one observation: on uncertain projects, planning everything in detail upfront fails, because needs evolve. The Agile Manifesto (2001) sets 4 values and 12 principles favouring adaptation over a fixed plan, collaboration over contract, a working product over exhaustive documentation.
Bilal lives exactly this observation: each client change used to break his schedule instead of enriching it.
2. Iterative, incremental, mindset
The core idea: working in short cycles (iterative) regularly delivering value (incremental), adjusting at each step through client feedback.
Agility is first a mindset — not just a toolbox. Scrum and Kanban are its most widespread frameworks.
🔎 Concrete example — 🔎 Concrete example — Agile does NOT mean unplanned
A frequent misconception.
Agile plans a lot, but DIFFERENTLY:
continuously and short-term (per iteration), not in one fixed plan.
→ you keep a vision and priorities (the backlog), you refine as you go.Outcome: adaptive planning, not its absence.
Reflex: deliver value early and often.
Section vocabulary
- Agility
- An adaptive approach to project management: moving in short cycles while adjusting to feedback.
Simple example: Bilal delivers a first version in 2 weeks then adjusts with the client.
What it is not: working with no plan and no priority, day by day.
Reflex: facing uncertainty, ask “which small increment should we deliver first?”.
- Agile Manifesto
- The founding text (2001) stating 4 values and 12 principles of agility.
Simple example: Favouring a working product and collaboration over a fixed plan.
What it is not: a precise method with imposed roles (that is Scrum's job).
Reflex: reread the 4 values before choosing an agile framework.
- Iterative and incremental
- Iterative: repeating short cycles; incremental: delivering slices of value that add up.
Simple example: Cycle 1: one usable feature; cycle 2: one more, and so on.
What it is not: delivering everything in a single block at the end.
Reflex: each cycle must end with something usable.
- Value (agile)
- The real benefit for the client. The aim is delivering it early and often, not all at the end.
Simple example: Bilal shows the client what really serves them from week 2.
What it is not: an intermediate document nobody uses.
Reflex: prioritize what serves the client, not what is easy to produce.
- Agile mindset
- A culture of collaboration, adaptation, feedback and continuous improvement — beyond tools.
Simple example: Bilal takes a client change as information, not as a fault.
What it is not: applying agile rituals without ever changing habits.
Reflex: tools follow; mindset first.
In practice — In practice — Adopting the agile mindset
- Read the 4 values of the Agile Manifesto and compare them with your current way of working.
- Spot a project or project part where needs are uncertain: would it be better handled by iterations?
- Notice the posture difference: delivering one big block at the end vs delivering small value increments regularly.
- Note what agility implies daily: close collaboration, frequent feedback, accepting change.
Ready-to-say script — proposing a first short cycle (1 min)
"Our needs evolve too much for a fixed 12-month plan. I propose we work in short cycles: we deliver a first usable increment in 2 weeks, we test it with you, then we adjust. We keep a clear vision and priorities, but we plan detail as we go. Do you agree we try it over one cycle?"
To say to the client or sponsor: frame the trial over a single cycle to remove fear of change.
Copy-paste template — framing your first increment
PROJECT: _______________
MAIN UNCERTAINTY: _______________
FIRST INCREMENT (usable in 2 weeks): _______________
TESTING CLIENT: _______________
EXPECTED FEEDBACK (what to observe): _______________
KEPT VISION (direction + priorities): _______________Very small business / tight budget
One 2-week cycle on a whiteboard is enough: one increment, one client demo, adjust.
SME in Algeria
Bilal slots his demos between travel and outages: one fixed slot per cycle, even short, beats a big postponed meeting.
Team new to agile
Start with a single uncertain project, not the whole company: the shift is proven by a first successful increment.
Highly sequential context
If everything is fixed (physical construction, strict regulation), stay predictive: reserve agility for truly uncertain parts.
✓ Best practices
- Deliver value early and often (increments).
- Keep a clear vision and priorities (the backlog).
- Reserve agility for uncertain / evolving contexts.
✗ Common pitfalls
- Believing agile = no planning.
- Reducing agility to tools or rituals without the mindset.
- Forcing agile onto a highly sequential, fixed context.
Key takeaways
- Agility answers uncertainty: adapt rather than freeze everything.
- The Agile Manifesto: 4 values, 12 principles.
- Work iterative (short cycles) and incremental (value delivered often).
- Agility is first a mindset, not just a toolbox.
48h challenge — apply tomorrow
Spot 1 uncertain need in your project and define the first increment deliverable in 2 weeks (template above). Present it to the client for first feedback.
- I can explain iterative and incremental without hesitating.
- I can tell adaptive planning from no planning.
- I framed 1 first increment deliverable in 2 weeks.
Frequently asked questions
Does agile mean “no planning”?
No, it is a frequent misconception: agile plans a lot, but differently — continuously and short-term (per iteration) rather than in a detailed plan fixed upfront. You keep a clear vision and priorities (the backlog), and you plan detail as you go. It is adaptive planning, not no planning. You simply accept that a detailed 12-month plan on uncertain needs will be wrong anyway.
Is agility only about software?
Born in software, it spread to many other fields (marketing, HR, products) wherever uncertainty and adaptation needs run high. Its principles (feedback, iterations, collaboration) transfer widely. But it stays ill-suited to highly sequential, fixed contexts (physical construction), where predictive dominates. The criterion is not the sector but the uncertainty level of needs.
What is agility's core idea?