Agile Project Management Cheat Sheet 2026

The 30 highest-yield Agile Project Management facts, distilled from real exam questions. Print it, save it as a PDF, or study it here — free, no sign-up.

1. A team adopts a new process change but reverts after one Sprint because results looked worse. What is the likely mistake? → They abandoned it before giving it enough time to take effect
2. What is a 'minimum viable product' (MVP) in the context of Agile release planning? → The smallest set of features that delivers value and enables validated learning
3. What is the time-box for the Sprint Review in a one-month Sprint? → Four hours
4. What is the purpose of a spike in Agile development? → A time-boxed investigation to reduce uncertainty or research a solution
5. Which Scrum artifact has the Product Goal as its commitment, providing a long-term objective for the Scrum Team to plan against? → The Product Backlog
6. A team wants to reduce variability in delivery times. Limiting WIP helps because it: → Stabilizes flow and tightens the cycle time distribution
7. What is 'collective code ownership' in Agile engineering practices? → Any team member can modify any part of the codebase, shared responsibility for quality
8. Which statement best describes a self-organizing team? → The team decides how to accomplish its work without external direction
9. Why are Fibonacci-like sequences (1, 2, 3, 5, 8, 13) commonly used for story points? → Larger items carry more uncertainty, so gaps widen
10. A team's defect rate is rising each release. Which continuous improvement focus is most appropriate? → Investigate and strengthen quality practices
11. What is the primary purpose of a product roadmap in Agile? → To communicate the strategic direction and planned evolution of a product
12. What is 'continuous delivery' in Agile? → The practice of keeping code in a deployable state so it can be released at any time
13. What is the most efficient method of conveying information to and within a development team? → Face-to-face conversation
14. What does the acronym INVEST describe regarding well-formed user stories? → Criteria for good user stories
15. How is remaining capacity typically calculated for sprint planning? → Team availability adjusted for time off and non-project work
16. Why might a team add an explicit 'Done' sub-column (e.g., 'Dev Done') before the next stage? → To make handoff readiness and pull points visible
17. What is the purpose of an Agile information radiator in relation to stakeholders? → To provide real-time, always-visible project status without needing to request reports
18. Which principle addresses changing requirements? → Welcome changing requirements, even late in development
19. What does the Agile concept of 'empiricism' rely on? → Decisions based on observation and experimentation
20. What does 'time-boxing' mean in Agile release planning? → Setting a fixed duration for a sprint or release, regardless of how much work is completed
21. According to the 12 Principles behind the Agile Manifesto, what is the primary measure of progress? → Working software
22. Which of the following best describes the primary purpose of using story points for estimation? → To create a relative measure of the effort, complexity, and uncertainty of a user story.
23. What is the primary purpose of a 'Five Whys' analysis in continuous improvement? → To drill down to a problem's root cause
24. Elapsed Time is defined by which of the following? → Is the amount of time that passes on a clock or perhaps a calendar
25. Which statement best reflects Agile's view of change? → Change is expected and harnessed for competitive advantage
26. Who is accountable for the Product Backlog's content and availability? → The Product Owner
27. ROTI is best described by which of the following? → Measure of effectiveness of the retrospective meeting
28. Which topic is NOT addressed during Sprint Planning? → What process the team should adopt next year
29. What is a common cause of chronic underestimation in teams? → Ignoring non-coding work like testing and integration
30. What is a reference story (or baseline story) used for in relative estimation? → A known-size anchor to compare other stories against