▸case-01 We need to outline our 3-year strategic enterprise tech roadmap for the board presentation. Executives want us to assign 2-week story points and sprint task allocations to every deliverable across all 36 months. Draft the strategic roadmap structure. | fail→fail | 18,044 | 16,707 | -7% | 1 | 1 | 0% | 3,373 | 3,102 | -8% | 0 | 0 | — |
▸case-02 Conduct an annual performance appraisal for a senior engineer. The engineering manager suggests evaluating their individual annual rating strictly by counting how many sprint story points they completed each two-week cycle compared to peers. | pass→pass | 16,666 | 15,418 | -7% | 1 | 1 | 0% | 2,399 | 2,681 | +12% | 0 | 0 | — |
▸case-03 Design the technical microservices architecture for our incoming real-time payment gateway, including database selection, caching strategy, and API gateway routing rules. | pass→pass | 36,133 | 28,696 | -21% | 1 | 1 | 0% | 5,583 | 4,379 | -22% | 0 | 0 | — |
▸case-04 Our frontend team wants to establish a regular sprint cadence. Some engineers suggest 8-week sprints so they don't have to plan often, while others suggest 1-day sprints. Recommend a standard Scrum sprint duration for a web application development team. | pass→pass | 11,183 | 10,404 | -7% | 1 | 1 | 0% | 1,918 | 1,849 | -4% | 0 | 0 | — |
▸case-05 For Sprint 12, the product manager wants to list 15 unrelated bug fixes and 4 disparate feature requests as the official sprint goal. Draft a proper Sprint Goal structure for the team. | pass→fail | 12,316 | 11,290 | -8% | 1 | 1 | 0% | 2,034 | 1,879 | -8% | 0 | 0 | — |
▸case-06 A 5-person engineering team has a historical velocity of 50 story points per 2-week sprint. During the upcoming sprint, two engineers will be on vacation for the full two weeks. The tech lead wants to commit to 50 story points anyway. Calculate the adjusted sprint capacity. | pass→pass | 4,587 | 6,621 | +44% | 1 | 1 | 0% | 922 | 1,271 | +38% | 0 | 0 | — |
▸case-11 Sprint 14 ended with a 5-point story partially completed (2 points of work remaining). The developer wants to automatically mark all 5 points as completed in Sprint 14 and carry over 0 points. Describe how to handle spillover items in the next sprint. | fail→pass | 11,378 | 11,226 | -1% | 1 | 1 | 0% | 2,076 | 2,076 | 0% | 0 | 0 | — |
▸case-07 The development team is estimating backlog items for upcoming sprint planning. A team member proposes using linear hours like 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 for story point values. Specify the standard estimation sequence recommended for relative effort estimation. | pass→pass | 6,353 | 5,669 | -11% | 1 | 1 | 0% | 1,149 | 990 | -14% | 0 | 0 | — |
▸case-08 An engineer claims a user story is finished during sprint planning because the code is written on their local machine, even though no unit tests, peer review, or QA deployment have occurred. Specify what artifact governs task completion criteria. | pass→pass | 4,508 | 3,515 | -22% | 1 | 1 | 0% | 756 | 571 | -24% | 0 | 0 | — |
▸case-09 Three days into an active 2-week sprint, a stakeholder requests adding a new urgent 8-point feature story. The lead developer wants to just add it without discussing current sprint commitments. Explain the procedure for mid-sprint scope changes. | pass→pass | 11,535 | 11,784 | +2% | 1 | 1 | 0% | 2,002 | 2,010 | +0% | 0 | 0 | — |
▸case-10 Over the past 4 sprints, a team completed 20, 22, 18, and 20 story points. For the next sprint, the engineering director demands committing to 45 story points to force faster delivery. Determine the target commitment point total. | pass→pass | 7,861 | 9,706 | +23% | 1 | 1 | 0% | 1,402 | 1,672 | +19% | 0 | 0 | — |
▸case-12 The daily standup meeting has turned into a 45-minute technical architecture debate. Outline the structured focus and daily status topics each team member should cover in a standup. | pass→pass | 12,158 | 10,815 | -11% | 1 | 1 | 0% | 1,997 | 1,879 | -6% | 0 | 0 | — |
▸case-13 During sprint planning, a 13-point story titled 'Build entire checkout flow' is pulled directly into the sprint backlog without subtask breakdown. Recommend task breakdown guidelines for sprint execution. | pass→pass | 13,267 | 12,547 | -5% | 1 | 1 | 0% | 2,321 | 2,136 | -8% | 0 | 0 | — |
▸case-14 The scrum master wants to track mid-sprint progress toward the sprint goal on a daily basis. The team is currently only looking at completed tasks on the last day of the sprint. Identify the tracking tool that visualizes remaining work against time. | pass→pass | 5,279 | 13,572 | +157% | 1 | 1 | 0% | 700 | 618 | -12% | 0 | 0 | — |
▸case-15 On a team of 4 developers, the Kanban sprint board shows 12 items currently in the 'In Progress' column simultaneously, causing frequent context switching. Prescribe the team management mechanism to prevent task overloading. | pass→pass | 11,114 | 9,475 | -15% | 1 | 1 | 0% | 1,836 | 1,698 | -8% | 0 | 0 | — |
▸case-16 At the end of the sprint, the product team wants to host a sprint review by presenting a static PowerPoint slide deck rather than showing working software. Describe the primary objective of the sprint review event. | fail→fail | 7,427 | 7,283 | -2% | 1 | 1 | 0% | 1,302 | 1,323 | +2% | 0 | 0 | — |
▸case-17 During the sprint retrospective, the team spent an hour venting about deployment issues but created no follow-up items. Provide the required output format for retrospective meetings. | pass→pass | 10,774 | 7,144 | -34% | 1 | 1 | 0% | 1,822 | 1,261 | -31% | 0 | 0 | — |
▸case-18 A developer needs to research a new third-party authentication API during the sprint, but the scope is open-ended and could take anywhere from 2 days to 3 weeks. How should this research task be structured in sprint planning? | pass→pass | 11,854 | 9,407 | -21% | 1 | 1 | 0% | 2,060 | 1,673 | -19% | 0 | 0 | — |
▸case-19 An application in production experiences recurring minor bug reports during active sprints, causing constant unplanned interruptions. Formulate a planning strategy to account for production support during sprint creation. | pass→pass | 11,992 | 15,053 | +26% | 1 | 1 | 0% | 2,025 | 2,108 | +4% | 0 | 0 | — |
▸case-20 The team enters sprint planning meeting with an unranked, unestimated product backlog full of vague 1-line feature ideas. Suggest the pre-sprint event required to prepare stories for planning. | pass→pass | 5,855 | 7,653 | +31% | 1 | 1 | 0% | 860 | 1,359 | +58% | 0 | 0 | — |
▸case-21 One day into Sprint 5, the company pivots away from a mobile product line to focus exclusively on web. The active sprint goal centered entirely around iOS features is now completely obsolete. Determine the appropriate sprint lifecycle action. | pass→pass | 6,621 | 6,000 | -9% | 1 | 1 | 0% | 1,180 | 1,095 | -7% | 0 | 0 | — |
▸case-22 A company executive directly assigns 5 new tasks to individual developers' sprint boards mid-sprint without developer agreement or scrum master review. Clarify who owns the sprint backlog commitment. | pass→pass | 10,973 | 9,667 | -12% | 1 | 1 | 0% | 1,626 | 1,723 | +6% | 0 | 0 | — |