LEARN. PRACTICE. GROW.Concept and mechanism
Agility requires observing outcomes and adjusting work when evidence changes. A daily meeting or digital board does not establish this by itself. The Agile Onion connects visible processes and practices with principles, values, and mindset. If incentives penalize collaboration, renaming meetings may leave behavior unchanged. Learning also applies to ongoing APS work: not every improvement needs a separate project. Choose how to organize work according to need, predictability, and capacity while keeping service commitments clear.
Guided application
Scrum provides a framework of goals, increments, and frequent inspection; Kanban helps define and manage flow, including work in progress. Lean directs attention toward value and waste, while a Lean Startup experiment tests a hypothesis before expanding investment. These approaches are not synonyms and do not remove governance. In an APS queue congested at review, starting more changes may increase waiting. Define start and finish, expose blockers, and help complete work. To test confidence in reconciliation, deliver a limited capability with learning criteria. Reducing scope does not mean removing essential controls.
An initial capability for one file type can teach more than eight weeks without user contact.
Common pitfalls
Rituals as adaptation; individual utilization as flow; quality-free MVP; delivery method as governance replacement.
Related topics: People, stories, and shared understanding · Value, roles, and adaptive planning
Choose practices for the learning and delivery they support.
Reference: PRINCE2 Agile Foundation syllabus · Version 2; inspected syllabus 2.0 (May 2025); revision 2.1 comparison pending