Why this matters

Continuous improvement is not a one-off “fix”; it is a repeatable team habit for turning evidence into small, testable changes. For Iteration 2, the goal is to improve the product and the way the team works.

Core model — PDCA

1. Plan — identify a concrete problem or opportunity; define the expected effect and a measure.
2. Do — trial the smallest safe change.
3. Check — compare the result with the baseline using data and stakeholder feedback.
4. Act — standardise the change if it worked, adapt it if evidence is mixed, or discard it and start another cycle.

Practical team loop

• Gather evidence from desk checks, defects, usability feedback, mentor comments and delivery data.
• Find the likely cause, not just the visible symptom.
• Convert one improvement into a backlog item with an owner, acceptance condition and review point.
• Monitor the result during the iteration.
• Document a proven practice in the team’s working agreement or SOP.

Sustainable focus — Pomodoro

A useful default is 25 minutes focused work + 5 minutes break, followed by a longer 15–30 minute break after four cycles.

• Break work expected to exceed four Pomodoros into smaller tasks.
• Batch tasks shorter than one Pomodoro.
• Protect the active focus block; record interruptions instead of immediately following them.
• Treat the timer as a feedback device, not a productivity score. Adapt the interval to the work and the team.

Application to Iteration 2

• Choose one product improvement and one process improvement.
• Record a baseline, the change, the result and the next decision.
• Bring the evidence to the retrospective so “continuous improvement” produces a visible backlog action.

Sources

• Continuous Improvement — Atlassian
• The Pomodoro Technique — Todoist
• Pomofocus timer