Agile project management
Key takeaways
Scope, time and cost move together, so every change needs a conscious trade-off.
- Copied!Any shift in scope, schedule, or budget typically forces an adjustment in at least one other constraint.
- Key takeawaysImbalances often show up as rushed work, under-resourcing, or overambitious deliverables that reduce quality.
- Agile improves delivery by combining iterative planning, tight feedback loops and disciplined ways of working.Pick at least one flexible constraint early so you can respond to issues without losing control.
- Agile delivers value in short iterations, using regular reviews and retrospectives to adapt quickly to change.Use prioritisation and formal change control to prevent scope creep and keep decisions objective.
- Scrum, Kanban, Lean and XP offer different structures, so choose based on workflow needs and team maturity.Monitor risks and progress continuously, and communicate trade-offs clearly to stakeholders.
- Clear roles, prioritised backlogs and well-written user stories reduce confusion and keep work aligned to outcomes.

focuses on adaptability, team collaboration, and continuous delivery of value to stakeholders.
Agile principles emphasise close communication, incremental progress, and regular feedback cycles to enhance quality and meet customer needs.
The Agile Manifesto: Values and principles
| The | Agile Manifesto |
|---|---|
| underpins Agile project management, defining four core values and twelve guiding principles. These foster a culture of collaboration, adaptability, and response to change. | Agile Manifesto core values |
| Individuals and interactions over processes and tools | Working software (or product) over comprehensive documentation |
| Customer collaboration over contract negotiation | Responding to change over following a plan |
| Twelve principles of Agile | Customer satisfaction through early and continuous deliveryWelcome changing requirements, even late in development |
| Deliver working products frequently | Close, daily cooperation between business people and developers |
Build
projects around motivated individualsFace-to-face conversation as the best form of communicationWorking product as the primary measure of progressSustainable development pace
Continuous attention to technical excellence and good design
- Simplicity – the art of maximising the amount of work not done – is essential
- Self-organising teams produce the best results
- Regular reflections for continuous improvement
- Key Agile frameworks and methodologies
Agile
encompasses various frameworks, each with its own practices and terminology. The most widely used Agile frameworks were designed for more efficient product delivery, rather than
- project management
- . They include
- ScrumProject Communication Plan | Knowledge Train
- , Kanban, Lean, and Extreme Programming (XP):
- ScrumMain focus: Team roles, time-boxed sprints, and iterative delivery
- Core roles:
- Product Owner,
- Scrum Master
- , Team Members
- Artefacts:
- Product backlog, sprint backlog
- Key events:
Sprint planning, daily scrum, sprint review, sprint retrospectives
Advantages: Well-defined structure, clear accountability, transparencyKanbanMain focus: Visualisation of workflow, limiting work in progress, continuous flowCore elements: Kanban board, work-in-progress limits, cards/tasks
Advantages:
- Flexibility, real-time workflow visualisation, easy adoption without role changesLean
- Main focus: Elimination of waste, maximising value, continuous improvement
- Core elements: Value stream mapping, optimised flow, customer focus
- Advantages: Improved efficiency, reduced delays, enhanced quality
- Extreme Programming (XP)Main focus:
- Technical excellence, frequent releases, customer involvementCore practices:
| user stories | Advantages: | Rapid feedback, high product quality, adaptability to change |
|---|---|---|
| Comparison: Scrum, Kanban, Lean, XP | Framework | Main focus |
| Key practice | Team structure | Best use case |
| Scrum | Time-boxed iterations (Sprints) | |
