CAE Cheat Sheet 2026
The 30 highest-yield CAE facts, distilled from real exam questions. Print it, save it as a PDF, or study it here — free, no sign-up.
40 questions
60 min time limit
65.00% to pass
- Which artifact in Scrum is used to visualize remaining work in a Sprint over time? → Sprint Burndown Chart
- What does it mean for the Definition of Done to evolve over time? → The DoD may become more stringent as the team improves its practices
- Which of the following is a key event in the Scrum framework? → Sprint Planning
- Which of the following best describes Acceptance Test-Driven Development (ATDD)? → Defining acceptance tests before development begins to guide implementation
- Which scenario represents a correctly written user story format? → As a registered user, I want to log in with my email so that I can access my account
- In Scrum, who is responsible for maximizing the value of the product resulting from the Scrum Team's work? → Product Owner
- Which approach best describes how an Agile leader handles conflict within the team? → Coach the team to resolve conflicts themselves using agreed-upon norms
- In the Scaled Agile Framework (SAFe), what event synchronizes all teams on an ART and plans the next Program Increment? → PI Planning
- What outcome does the Sprint Retrospective produce according to Scrum? → A plan for implementing improvements to the team's way of working
- A Kanban board has a column consistently overflowing despite WIP limits. What is the BEST immediate action? → Stop pulling new work and swarm to clear the bottleneck
- A product owner notices that a key stakeholder stopped attending sprint reviews. What is the BEST first step? → Reach out directly to understand their concerns and re-engage them
- Which role facilitates communication and removes impediments for the team in Scrum? → Scrum Master
- The 'Five Whys' technique is used in retrospectives to: → Drill down to the root cause of a problem by repeatedly asking 'why'
- What does 'yesterday's weather' mean as an agile planning technique? → Using the previous sprint's actual velocity to forecast the upcoming sprint's capacity
- A distributed team struggles with retrospective participation because remote members feel unheard. The BEST mitigation is: → Use digital collaboration tools that give all participants equal visual and input access
- What is the primary purpose of a story map in user story development? → To visualize the full user journey and identify gaps in the backlog
- How does Scrum ensure that the Increment produced meets quality standards? → Through the Definition of Done applied consistently to each Increment
- During backlog refinement, the team realizes an item lacks enough detail to estimate. What should happen? → Discuss and add acceptance criteria before estimating
- During Sprint Planning, who decides how the work in the Sprint will be performed? → The Developers
- In Kanban, what does a 'cumulative flow diagram' (CFD) show? → The amount of work in each stage of the workflow over time
- In the context of continuous improvement, 'kaizen' means: → A philosophy of small, incremental improvements made continuously
- What does it mean when a team has a 'shared understanding' of the Definition of Done? → Every team member interprets and applies the DoD consistently without ambiguity
- Why are Agile teams encouraged to be cross-functional? → To enable delivery of complete features independently
- What is the recommended frequency for backlog refinement in Scrum? → Continuously throughout the sprint, totaling no more than 10% of the team's capacity
- What is the recommended maximum duration of a sprint planning meeting for a two-week sprint? → Up to 4 hours
- A team's retrospective consistently produces the same action items sprint after sprint with little improvement. The MOST likely root cause is: → Action items are not tracked or followed up between retrospectives
- Why is face-to-face communication preferred in Agile? → To ensure clear and efficient collaboration
- Which of the following best describes the Kanban practice of 'making policies explicit'? → Clearly defining and displaying the rules that govern how work flows through the system
- A team member raises a technical impediment during the Daily Scrum that requires a long discussion. What is the best approach? → Note it and schedule a separate meeting with the relevant people after the Daily Scrum
- When should Acceptance Criteria be defined for a user story? → Before or during Sprint Planning so the team understands scope before committing
Turn these facts into recall:
Was this helpful?