40 questions covering everything from the Agile Manifesto to User Stories, MVP, and estimation. For learning — not assessment. See how you do, then read the explanations.
40 questionsTrue / False · Single select · Multi selectSessions 1–6~20 min
0 / 40 answered
Session 1 — Agile Mindset
Q1True / FalseSession 1
The Agile Manifesto values "working software over comprehensive documentation" — meaning documentation should never be written in an Agile project.
True
False
Q2True / FalseSession 1
Agile works best for projects where requirements are well understood upfront and unlikely to change.
True
False
Q3Single selectSession 1
Which of the following best describes what the Agile Manifesto means by "responding to change over following a plan"?
Agile teams do not create plans at all.
When new information emerges, adapting the plan is more valuable than following the original plan precisely.
Change requests must be approved by stakeholders before the team can respond to them.
Agile teams change direction every Sprint regardless of whether circumstances have changed.
Q4Multi selectSession 1
Which of the following are stated values in the Agile Manifesto? Select all that apply.
Individuals and interactions over processes and tools
Predictability and control over experimentation and learning
Customer collaboration over contract negotiation
Working software over comprehensive documentation
Velocity and throughput over team wellbeing
Responding to change over following a plan
Q5True / FalseSession 1
The Agile Manifesto was written primarily to describe how software should be built faster and at lower cost.
True
False
Q6Single selectSession 1
A company says "We follow Agile" but runs annual planning cycles, measures success by hours logged, and never shows working software to customers until the project is complete. This is best described as:
Agile with a structured governance overlay
"Doing Agile" without "Being Agile" — using the language but not the mindset
A hybrid methodology combining Agile and Waterfall appropriately
Scaled Agile — appropriate for enterprise contexts
Session 2 — Agile as PM
Q7True / FalseSession 2
In an Agile team, the Product Owner is responsible for both deciding what to build and assigning tasks to developers.
True
False
Q8Single selectSession 2
What is the primary distinction between Scrum and Kanban?
Scrum is for software teams; Kanban is for operations teams.
Scrum uses fixed-length iterations (Sprints) with committed scope; Kanban is a continuous flow system with no fixed iteration length.
Scrum requires a Product Owner; Kanban requires a Scrum Master.
Kanban uses story points; Scrum uses hours.
Q9True / FalseSession 2
WIP limits in Kanban are designed to prevent teams from multitasking and to expose bottlenecks in the workflow.
True
False
Q10Multi selectSession 2
Which of the following are responsibilities of the Product Owner in Scrum? Select all that apply.
Maintaining and ordering the Product Backlog
Deciding which developers work on which tasks each Sprint
Ensuring stakeholders understand and can view the Product Backlog
Accepting or rejecting work at the Sprint Review
Facilitating the Daily Scrum each morning
Sessions 3 & 4 — Scrum Framework & Practice
Q11True / FalseSessions 3–4
The Daily Scrum is a status report meeting where each team member updates the Scrum Master on what they have completed.
True
False
Q12Single selectSessions 3–4
What is the primary purpose of the Sprint Retrospective?
To demonstrate completed work to stakeholders and gather product feedback.
To identify and plan improvements to the team's process, collaboration, and tools.
To estimate the stories for the next Sprint.
To review whether the team met its velocity target.
Q13True / FalseSessions 3–4
In Scrum, only the Scrum Master can add new stories to the Product Backlog during a Sprint.
True
False
Q14Multi selectSessions 3–4
Which of the following are Scrum ceremonies (events)? Select all that apply.
Sprint Planning
Backlog Refinement
Daily Scrum
Quarterly Business Review
Sprint Review
Sprint Retrospective
Q15True / FalseSessions 3–4
"Scrum But" refers to teams that adopt only the parts of Scrum they find convenient, typically removing the elements that create the most productive discomfort.
True
False
Q16Single selectSessions 3–4
A team is halfway through a Sprint and a stakeholder requests a significant new feature be added to the current Sprint. What is the correct Scrum response?
The Scrum Master should immediately add the feature to the Sprint Backlog.
The PO should evaluate the request, add it to the Product Backlog, and consider it for the next Sprint — not the current one.
The team should vote on whether to include the feature mid-Sprint.
The stakeholder should raise it directly with individual developers.
Session 5 — Initiation & Requirements
Q17True / FalseSession 5
In Agile, the Product Vision should be updated regularly — ideally every Sprint — to reflect what the team has learned.
True
False
Q18Single selectSession 5
What is a story map's "narrative spine"?
The list of all user stories ordered by priority.
The top row of a story map — the sequence of high-level user activities arranged left to right in the order a user experiences them.
A description of the product vision written in story format.
The horizontal release line that separates the MVP from Release 2.
Q19True / FalseSession 5
An MVP is considered viable if at least one feature in it works without bugs.
True
False
Q20Multi selectSession 5
Which of the following correctly describe how epics should be managed? Select all that apply.
Epics should be broken into stories as soon as they are identified.
Epics sit on the backlog in rough form until they are close to being needed.
A good epic has one common goal thread connecting all its stories.
Epics are permanent backlog categories that group related stories forever.
An epic is closed when all its stories are done and the goal is met.
Q21Single selectSession 5
Which of the following best describes the role of stakeholders in Agile requirements gathering?
Stakeholders provide a complete requirements list at project initiation which the team then builds.
Stakeholders are ongoing collaborators who help the team understand the problem space — and whose needs evolve as the product develops.
Stakeholders approve or reject stories before they enter the Sprint Backlog.
Stakeholder involvement ends after the initial discovery workshop.
Session 6 — Stories, Journey & Release
Q22True / FalseSession 6
A User Story is complete when the code has been written and passes all unit tests — regardless of whether acceptance criteria were defined.
True
False
Q23Single selectSession 6
A story reads: "As a user, I want a dashboard." What is the most significant problem with this story?
It is too short — a good story should be at least three sentences.
It is missing the "so that" clause — the team cannot understand what value the dashboard is meant to deliver.
The word "user" is not a valid user type in Agile.
It does not include a point estimate.
Q24True / FalseSession 6
Story points measure the number of hours a story will take to complete.
True
False
Q25Single selectSession 6
Why does planning poker use simultaneous card reveal rather than asking people to share estimates one at a time?
It makes the process faster by eliminating discussion.
It prevents anchoring — where the first number spoken influences everyone else's estimate.
It ensures the Scrum Master's estimate is not revealed before the team votes.
Cards are used because verbal estimates are not tracked in Scrum tools.
Q26True / FalseSession 6
A team's velocity can be compared to another team's velocity to determine which team is more productive.
True
False
Q27Multi selectSession 6
Which of the following are anti-patterns in Agile estimation? Select all that apply.
Using velocity as a measure of team performance and pressuring teams to increase it.
Treating Sprint commitments as firm contracts rather than forecasts.
Adding a systematic 30% buffer to all estimates "just in case".
Using simultaneous card reveal in planning poker.
Comparing velocity across different teams.
Q28True / FalseSession 6
A User Journey shows the complete sequence of steps a specific user takes to achieve a goal — and User Stories are the building blocks of that journey.
True
False
Q29Single selectSession 6
A QuickBite MVP includes: browse restaurants, view menu, add to cart, and pay. A stakeholder asks to add live map delivery tracking before launch. The PO correctly responds:
"Tracking is valuable — I'll add it to the MVP since users will expect it."
"Live tracking is valuable but not required for a customer to complete an order. I'll add it to the Release 2 backlog so we can launch and learn first."
"If the stakeholder wants it, we should include it — stakeholder satisfaction is the measure of a good MVP."
"We cannot add anything to the MVP after Sprint Planning begins."
Q30True / FalseSession 6
The cone of uncertainty tells us that estimates become more accurate as a project progresses, because the team has built more and has less remaining work to be wrong about.
True
False
Mixed — Across all sessions
Q31Single selectAll sessions
A release forecast shows: 180 backlog points ÷ 30 velocity = 6 Sprints. The team's Sprints are 2 weeks long. What is the correct way to communicate this to stakeholders?
"We will launch in exactly 12 weeks."
"We expect to launch in approximately 11–14 weeks based on our current backlog and velocity."
"We cannot give any estimate until we are closer to delivery."
"The forecast is 6 Sprints but stakeholders should add their own buffer."
Q32True / FalseAll sessions
The Product Backlog is finished once all user stories have been written and estimated before the project begins.
True
False
Q33Multi selectAll sessions
Which of the following correctly describe the relationship between the Product Vision, User Journey, MVP, and Backlog? Select all that apply.
The vision sets the destination — it describes why the product exists and who it serves.
The User Journey maps the route — it shows the sequence of steps needed to achieve the user's goal.
The MVP is the entire backlog — everything must be built before the product is viable.
The MVP is the first stop — the minimum needed to prove the journey works end-to-end.
The backlog contains everything else — every stop after the MVP, ordered by value.
Q34Single selectAll sessions
Which role is responsible for ensuring the Scrum ceremonies happen on time, are productive, and that impediments blocking the team are removed?
The Product Owner
The Scrum Master
The developers lead
The project sponsor
Q35True / FalseAll sessions
In Agile, the "Definition of Done" is a list of acceptance criteria for a specific User Story.
True
False
Q36Multi selectAll sessions
Which of the following statements about the Sprint Review are correct? Select all that apply.
The Sprint Review is a demo of completed work to stakeholders.
The Sprint Review is the same event as the Sprint Retrospective.
Stakeholder feedback at the Sprint Review is the backlog's primary update mechanism.
Only work that meets the Definition of Done can be demonstrated at the Sprint Review.
The Sprint Review replaces formal project status reports for stakeholders.
Q37Single selectAll sessions
A team has been working for 8 Sprints with velocities of: 18, 22, 27, 31, 29, 33, 31, 32. What is the best velocity to use for a release forecast?
33 — the highest Sprint, to show the best-case scenario.
18 — the lowest Sprint, to be conservative.
31 — the rolling average of the last 4–5 stable Sprints (Sprints 4–8).
27 — the average of all 8 Sprints including the ramp-up period.
Q38True / FalseAll sessions
In Agile, a good User Story should describe what the system does — written from the perspective of the technical team who will build it.
True
False
Q39Multi selectAll sessions
Which of the following are valid story splitting patterns? Select all that apply.
By workflow step — split a large story into each step of the user's process.
By developer — assign one story per team member so everyone has their own piece.
By user type — if different users need the same feature differently, give each user their own story.
Happy/unhappy path — build the success case first, handle error states in a separate story.
MVP slice — build the simplest version that delivers value, then add richness in a follow-up story.
Q40Single selectAll sessions
A team asks "Why did we ship slower this Sprint — was it the tech debt we tackled, the new team member onboarding, or the ambiguous stories?" This conversation is best suited for which ceremony?