Week 11 of 12 · 12 hours · Diploma

Leading the team, ensuring quality, working with partners and closing

Objectives of the week
  • Lead a humanitarian project team: servant leadership, team development, conflict, wellbeing.
  • Manage quality (plan, assure, control) and work with local partners in a localisation approach.
  • Close a project completely: acceptance, handover, administrative and financial closure, lessons learned.

Keep the course at home: free PDF handout with exercises, key takeaways and quiz answers.

Download this lesson as PDF Complete manual (PDF)

1The project manager's leadership

Recent frameworks (PMBOK, PRINCE2 7, Scrum) stress servant leadership: removing obstacles, clarifying priorities, protecting the team from interruptions, developing skills, rather than commanding and controlling every task.

Tuckman's model describes the stages of team development: forming (politeness, uncertainty), storming (conflict over roles and methods), norming (shared rules), performing, then adjourning at the end of the project. The project manager adapts their style: directive at the start, more delegating later.

In humanitarian work, add: the diversity of statuses (national and international staff, volunteers, partners), high staff turnover, stress and exposure to trauma. Duty of care includes security, mental health, sustainable working hours and fair treatment.

2Managing conflict and negotiating

Five conflict modes (Thomas-Kilmann model): collaborating (seeking a solution that satisfies both parties, preferred for important issues), compromising, competing (emergency, security), accommodating (low stakes for yourself), avoiding (temporarily, to let tension subside).

The PMP exam values one approach: first understand the cause, in private, with the people concerned, before escalating. Example: the logistics manager and the field coordinator disagree on distribution dates. The project manager brings them together, has each set out their constraints (truck availability, families' farming calendar), looks for a common option (two distribution waves), then formalises the decision.

3Quality: plan, assure, control

Quality is conformance to requirements and fitness for use. Three levels:

  • Plan: applicable standards (Sphere, national technical standards, donor requirements), acceptance criteria for each deliverable, inspection plan;
  • Assure: check that processes enable quality (team training, procedures, internal audits);
  • Control: inspect deliverables (sampling, tests, post-distribution monitoring) and correct.

The cost of quality includes the cost of conformance (prevention, inspection) and the cost of non-conformance (rework, rejects, loss of trust). Preventing is almost always cheaper than correcting. The Core Humanitarian Standard (CHS) sets nine commitments on quality and accountability to affected people, useful as a checklist for the whole project.

4Working with local partners

Many projects are implemented with or by local and national organisations. Localisation commitments (Grand Bargain) aim to strengthen their role, their direct funding and their decision-making power.

Good project management practice in partnership:

  • design the project and budget together, including a share of indirect costs for the partner;
  • a proportionate partner assessment, followed by a mutual capacity-strengthening plan rather than a simple list of requirements;
  • clear roles (RACI) and shared governance (joint steering committee);
  • fair risk sharing, including security: do not transfer risk to the partner without the means;
  • simplified and harmonised reporting when possible.

5Closing the project

Closure is often rushed, yet it determines sustainability and the final payment. Checklist:

  • Acceptance of deliverables with beneficiaries, authorities or management committees (signed minutes);
  • Handover: technical documents, committee training, maintenance plan, transfer or disposal of equipment according to donor rules;
  • Administrative closure: supplier and staff contracts, archiving for the required period (often 5 to 10 years after the end), closing accounts;
  • Financial closure: last eligible expenditure before the end date, reconciliations, refund of unused funds, audit preparation;
  • Communication to communities about the end of the project and the remaining avenues of recourse;
  • Final report, final evaluation if planned, and a lessons-learned workshop.

An exit strategy is prepared from the design stage: who maintains what after the project, with what resources?

6AI for the team, quality and closure

Useful uses: preparing the agenda of a difficult meeting, practising a delicate conversation (AI plays the unhappy colleague), drafting quality control procedures, generating a closure checklist adapted to the donor, synthesising lessons learned from several reports into themes, finding what past evaluations recommended.

Limits: do not use AI to assess the individual performance of a team member or draft a sanction based on personal information; do not paste HR or medical files; conduct, harassment and PSEA matters follow the organisation's confidential procedures.

Exercise: cost of quality

Situation. The fictitious NGO Bina is building 300 latrines. At the first inspection, 12% have defects (cracked slab, pit too shallow); each repair costs EUR 180. Additional training for masons and a mid-site inspection would cost EUR 2,000 and bring the defect rate down to 4%.

Task. 1) Cost of repairs without training? 2) Total cost with training? 3) Saving? 4) What other, non-quantified benefit should be mentioned?

Answer. 1) 12% × 300 = 36 latrines; 36 × 180 = EUR 6,480. 2) 4% × 300 = 12 latrines; 12 × 180 = EUR 2,160; plus EUR 2,000 for training and inspection = EUR 4,160. 3) 6,480 − 4,160 = EUR 2,320 saved. 4) Fewer health and accident risks for families, greater community trust, deadlines met, and better-trained masons for future projects.

Key points

  • Servant leadership; adapt your style to the team's stage of development (Tuckman).
  • Conflict: understand the cause in private and seek a collaborative solution before escalating.
  • Quality: plan, assure, control; prevention costs less than correction; CHS as a framework.
  • Local partnerships: joint design, indirect costs, shared risks, shared governance.
  • Closure includes acceptance, handover, administrative and financial closure, and lessons learned.
A question about this module?

Ask the other participants: they are taking the same course as you.

Ask my question See this module's discussions

💼 Programme management jobs

Put this course into practice: the latest jobs in this field.

See all 1171 Programme management jobs →

Prepare for the written test and interviewA model written test in this field, interview questions with sample answers and the STAR method.See the model test →
Further reading: course references
  1. Project Management Institute (PMI) (2025). A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th edition. www.pmi.org
  2. Project Management Institute (PMI) (2026). PMP Examination Content Outline. www.pmi.org/certifications/project-management-pmp
  3. PeopleCert (AXELOS) (2023). Managing Successful Projects with PRINCE2, 7th edition. www.peoplecert.org
  4. Ken Schwaber and Jeff Sutherland (2020). The Scrum Guide. scrumguides.org
  5. Group of 17 signatories (2001). Manifesto for Agile Software Development. agilemanifesto.org
  6. PM4NGOs (2020). Project DPro: project management guide for development professionals (PMD Pro 2nd edition). pm4ngos.org
  7. PM4NGOs (2019). MEAL DPro: guide to monitoring, evaluation, accountability and learning. pm4ngos.org
  8. European Commission (2004). Project Cycle Management Guidelines. international-partnerships.ec.europa.eu
  9. United Nations Sustainable Development Group (UNSDG) (2011). Results-Based Management Handbook. unsdg.un.org
  10. CHS Alliance, Groupe URD and Sphere (2024). Core Humanitarian Standard on Quality and Accountability. www.corehumanitarianstandard.org
  11. Sphere Association (2018). The Sphere Handbook. spherestandards.org
  12. Inter-Agency Standing Committee (IASC) (2023). Operational Guidance on Data Responsibility in Humanitarian Action. interagencystandingcommittee.org
  13. ICRC and Brussels Privacy Hub (2020). Handbook on Data Protection in Humanitarian Action (2nd edition). www.icrc.org
  14. National Institute of Standards and Technology (NIST) (2023). AI Risk Management Framework (AI RMF 1.0). www.nist.gov
  15. 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.

1In Tuckman's model, the stage where conflict over roles appears is:
2For an important conflict between two managers, the mode to favour is:
3The cost of non-conformance includes:
4The exit strategy is prepared:
5Which of these uses of AI must be excluded?

← Week 10Week 12 →