Continuous improvement is at the heart of agile philosophy. Agile teams don’t wait for postmortems or final reviews — they inspect and adapt as they go. Task 5, “Perform Continuous Improvements,” reinforces the idea that delivering value efficiently requires regular examination of the team’s process, performance, and results — and adjusting based on what is learned.
This task is closely tied to agile retrospectives, feedback loops, and data-informed decision-making, all of which promote a culture of learning and evolution. By consistently experimenting and adjusting, teams build resilience, remove waste, and increase delivery predictability.
The PMI Agile Practice Guide, especially in Sections 5.6 (Continuous Improvement) and 4.2 (Team Performance), outlines techniques for capturing feedback, fostering self-organization, and building habits of adaptive change.
Enabler 1: Obtain Metrics and Feedback to Drive Continuous Improvements
Before a team can improve, it must understand what is working and what isn’t. Feedback and metrics provide the inputs needed to make informed improvement decisions.
Sources of feedback include:
- Sprint reviews (stakeholder feedback on delivered work)
- Retrospectives (team reflection on process and collaboration)
- User feedback (surveys, NPS, usability testing)
- Operational data (cycle time, throughput, defect trends)
Agile metrics help highlight where to focus improvement efforts:
- Lead time and cycle time show delivery efficiency
- Blocked tasks reveal bottlenecks
- Defect rates indicate quality gaps
- Team morale scores can reflect cultural health
The team should analyze data collaboratively to identify root causes and opportunities. It’s important that data is not used punitively but to promote shared learning and self-correction.
Without feedback, teams operate on assumptions; without metrics, they lack visibility. Both are required for agile maturity.
Enabler 2: Implement Improvement Actions
Insights must lead to action. During retrospectives or process reviews, agile teams should define clear, specific, and achievable improvement experiments and include them in the team’s backlog or action plan.
Examples might include:
- Adjusting story sizing techniques
- Revising Definition of Ready or Done
- Introducing pair programming or mobbing for knowledge sharing
- Automating a manual deployment step
Improvement actions should be:
- Owned by the team
- Time-bound (e.g., “Try for 2 sprints”)
- Trackable (via dashboards, task lists, or Kanban swimlanes)
A common mistake is creating too many actions or failing to act on any of them. To avoid this, teams can use improvement boards or dedicate retrospective follow-ups during planning meetings.
When implemented with commitment, even small changes can yield compounding long-term benefits.
Enabler 3: Evaluate the Effectiveness of Process Improvement
Not every improvement attempt yields results. Agile teams must inspect outcomes and decide whether to:
- Adopt the change permanently
- Refine it for another iteration
- Discard it and try something else
Evaluation techniques include:
- Team self-assessments
- Comparative metrics (before/after views of cycle time, defects, etc.)
- Satisfaction surveys
- Re-examining original problem statements during retrospectives
For instance, if a team implemented pair programming to reduce bugs, they might compare defect rates across sprints and discuss whether collaboration improved quality and morale.
Agile leadership supports a culture of experimentation — where failure is treated as a source of learning, not blame. The goal is to create a feedback-driven improvement cycle: observe → act → evaluate → adapt.
Skipping this evaluation step leads to blind change — activity without progress.
Summary Points
- Continuous improvement is a deliberate, feedback-driven process of learning and adapting.
- Data and stakeholder feedback reveal where adjustments are needed.
- Improvement actions should be specific, team-owned, and followed up in subsequent sprints.
- Effectiveness must be evaluated — if an action doesn’t produce results, the team should try something else.
- Agile teams use retrospectives and metrics not just to look backward, but to move forward intentionally.
- The improvement loop never ends — it is a core engine of agile excellence.
Test Your Knowledge
To complete this task, take a micro-exam to assess your understanding.
You can start the exam by using the floating window on the right side of your desktop screen or the grey bar at the top of your mobile screen.
Alternatively, you can access the exam via the My Exams page: 👉 KnowledgeMap.pm/exams
Look for the exam with the same number and name as the current PMI-ACP ECO Task.
After completing the exam, review your overall score for the task on the Knowledge Map: 👉 KnowledgeMap.pm/map
To be fully prepared for the actual exam, your score should fall within the green zone or higher, which indicates a minimum of 70%. However, aiming for at least 75% is recommended to strengthen your knowledge, boost your confidence, and improve your chances of success.