- Explain the values and principles of the Agile Manifesto, and the roles, events and artefacts of Scrum (2020 Scrum Guide).
- Manage a workflow with Kanban: board, work-in-progress limits, lead time.
- Build a hybrid approach that is credible to a donor, and use AI to prepare the backlog and retrospectives.
Keep the course at home: free PDF handout with exercises, key takeaways and quiz answers.
1The Agile Manifesto
In 2001, seventeen software practitioners published the Manifesto for Agile Software Development. Its four values:
- individuals and interactions over processes and tools;
- working solutions over comprehensive documentation;
- customer collaboration over contract negotiation;
- responding to change over following a plan.
The items on the right still have value; those on the left have more. In humanitarian work, the "customer" is first the affected population: agility meets the requirement for accountability and adaptation to context. But it does not exempt you from the documentation required by the donor, nor from respecting the contract.
2Scrum: roles, events, artefacts
According to the Scrum Guide (2020 edition, by Ken Schwaber and Jeff Sutherland), Scrum is a lightweight framework based on empiricism (transparency, inspection, adaptation).
Three accountabilities in the Scrum team (10 people at most): the Product Owner maximises value and orders the backlog; the Scrum Master helps the team apply Scrum and removes impediments; the developers (in the broad sense: those who produce) create the increment.
Five events: the sprint (one month at most, often two weeks), which contains sprint planning, the daily scrum (15 minutes), the sprint review and the retrospective.
Three artefacts with their commitments: the product backlog (product goal), the sprint backlog (sprint goal), the increment (definition of done).
Humanitarian example. An information management team develops a dashboard to track distributions. Two-week sprints; at each review, field coordinators test the version and request adjustments. After six sprints, the tool is in use; with frozen specifications, it would have been delivered late and poorly suited.
3Kanban: visualise and limit work in progress
Kanban sets neither roles nor sprints. It asks you to:
- visualise the flow on a board (for example: To do, In preparation, In validation, Done);
- limit work in progress (WIP) in each column, to finish before starting;
- measure the flow: lead time (time between the start and end of an item), throughput (items finished per week);
- improve continuously.
Kanban suits support teams (procurement, HR, grants) that receive requests continuously. Little's law links the three measures: average lead time = average work in progress ÷ average throughput. If a procurement team has 30 requests in progress and handles 10 per week, the average lead time is 3 weeks; bringing work in progress down to 15 brings it to 1.5 weeks, without working more.
4Agile measures: velocity and burndown
In Scrum, the team often estimates items in points (relative size) and measures its velocity: points completed per sprint. Velocity is used to forecast, never to compare or judge teams.
The burndown chart shows remaining work over time. If the remaining backlog is 120 points and average velocity is 24 points, about 5 sprints are needed.
Watch out for drift: inflating estimates to "improve" velocity, or declaring "done" what does not meet the definition of done. In humanitarian work, the definition of done must include protection requirements: for example "tested with users, no personal data visible, translated into working languages".
5Hybrid in front of the donor
A donor funds results within a fixed frame. You can still be agile inside that frame:
- the logframe, overall budget and contractual milestones remain fixed;
- activities and arrangements are planned in cycles of 4 to 8 weeks, reviewed with monitoring data and community feedback;
- each adjustment is documented (decision, data, approval) and, if it exceeds contractual thresholds (often 10 to 20% reallocation between lines), submitted to the donor.
Structured frameworks exist to combine the two: PRINCE2 Agile, the hybrid section of the PMBOK, or scaling frameworks such as SAFe, better suited to large digital organisations than to NGOs.
Common agile certifications: PSM (Scrum.org), CSM (Scrum Alliance), PMI-ACP (PMI). Their requirements change: check them on the official websites.
6AI serving an agile team
Useful and safe uses:
- turning expressed needs into user stories ("As a site coordinator, I want to see the week's distributions by village, so that I can spot delays") with acceptance criteria;
- proposing how to split an item that is too big into items deliverable in one sprint;
- synthesising the notes of a retrospective into themes and actions, without names;
- preparing a review summary for the donor.
AI must not estimate in place of the team (estimation is a collective act that reveals disagreements), nor order the backlog in place of the Product Owner. And community feedback being analysed must be anonymised before it is entered.
Exercise: forecasting with velocity and Little's law
Situation. The information management team of the fictitious NGO Basira is developing a complaints tracking application. Remaining backlog: 168 points. Velocities of the last four two-week sprints: 18, 22, 20, 24 points. Separately, the grants team, run with Kanban, has 24 files in progress and finishes 6 per week.
Task. 1) Average velocity? 2) How many sprints and weeks to finish the backlog? 3) Average lead time of a grant file? 4) What would you propose to reduce it?
Answer. 1) (18 + 22 + 20 + 24) ÷ 4 = 21 points. 2) 168 ÷ 21 = 8 sprints, i.e. 16 weeks (a forecast, to be revised every sprint). 3) Little's law: 24 ÷ 6 = 4 weeks. 4) Limit work in progress (for example 12 files at most): at equal throughput, lead time falls to 2 weeks; finish before starting, and find the column where files pile up.
Key points
- The Agile Manifesto values people, working solutions, collaboration and adaptation.
- Scrum: 3 accountabilities, 5 events, 3 artefacts; sprints of one month at most.
- Kanban: visualise, limit work in progress, measure flow; lead time = work in progress ÷ throughput.
- Hybrid keeps the contractual frame fixed and adapts activities in short, documented cycles.
- AI helps write stories and syntheses; the team estimates and the Product Owner orders.
Ask the other participants: they are taking the same course as you.
💼 Programme management jobs
Put this course into practice: the latest jobs in this field.
- Chief Investment Officer (CIO) – TUFIDCNational Institute of Urban Management (NIUM) · India
- UN Women National Consultant - Technical Coordinator – Karachi, Sindh, PakistanONU Femmes / UN Women · Pakistan
- Program OfficerNavshristi Foundation · India
- Sign Language InterpreterThe American India Foundation Trust (AIFT) · India
- Тренер/ка-ментор/ка з розвитку спроможності Рад ветеранівIREX · Ukraine
Further reading: course references
- Project Management Institute (PMI) (2025). A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th edition. www.pmi.org
- Project Management Institute (PMI) (2026). PMP Examination Content Outline. www.pmi.org/certifications/project-management-pmp
- PeopleCert (AXELOS) (2023). Managing Successful Projects with PRINCE2, 7th edition. www.peoplecert.org
- Ken Schwaber and Jeff Sutherland (2020). The Scrum Guide. scrumguides.org
- Group of 17 signatories (2001). Manifesto for Agile Software Development. agilemanifesto.org
- PM4NGOs (2020). Project DPro: project management guide for development professionals (PMD Pro 2nd edition). pm4ngos.org
- PM4NGOs (2019). MEAL DPro: guide to monitoring, evaluation, accountability and learning. pm4ngos.org
- European Commission (2004). Project Cycle Management Guidelines. international-partnerships.ec.europa.eu
- United Nations Sustainable Development Group (UNSDG) (2011). Results-Based Management Handbook. unsdg.un.org
- CHS Alliance, Groupe URD and Sphere (2024). Core Humanitarian Standard on Quality and Accountability. www.corehumanitarianstandard.org
- Sphere Association (2018). The Sphere Handbook. spherestandards.org
- Inter-Agency Standing Committee (IASC) (2023). Operational Guidance on Data Responsibility in Humanitarian Action. interagencystandingcommittee.org
- ICRC and Brussels Privacy Hub (2020). Handbook on Data Protection in Humanitarian Action (2nd edition). www.icrc.org
- National Institute of Standards and Technology (NIST) (2023). AI Risk Management Framework (AI RMF 1.0). www.nist.gov
- United Nations (Chief Executives Board) (2022). Principles for the Ethical Use of Artificial Intelligence in the United Nations System. unsceb.org
Weekly quiz
5 demanding questions to check your learning. Answer them all to complete the week.