Top 30 Intermediate Agile & Scrum Concepts Quiz

30 questions. Pick an answer, or open “Show the answer” to read it.

Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.

1. Question 1 of 30

   Which of the following best explains the Lean Software Development principle of 'Decide as Late as Possible'?

   • aIt ensures that all stakeholders have ample opportunity to provide input before a decision is finalized.
   • bIt encourages extensive upfront analysis to prevent costly rework later in the project.
   • cIt aims to preserve flexibility and keep options open until the last responsible moment, adapting to new information.
   • dIt allows teams to defer difficult technical choices, reducing immediate pressure and improving morale.
   Show the answer

   Answer: c · It aims to preserve flexibility and keep options open until the last responsible moment, adapting to new information.

   The card explicitly states that 'Decide as Late as Possible' is to 'preserve flexibility and keep options open until the last responsible moment.' This allows for adaptation to new information. Option B is incorrect because Lean emphasizes fast feedback and adaptation over extensive upfront analysis, which could be considered waste if it delays learning or delivery.

   Read the full bite: Lean Software Development: Focus on Value, Not Waste

2. Question 2 of 30

   What is the primary objective when an agile team applies the concept of Muda to its development process?

   • aTo strictly minimize all forms of delays and handoffs within the workflow.
   • bTo ensure every feature developed is a "gold-plated" solution meeting all possible future needs.
   • cTo assign blame to individuals or teams responsible for inefficiencies.
   • dTo identify and eliminate activities that consume resources without adding value for the customer.
   Show the answer

   Answer: d · To identify and eliminate activities that consume resources without adding value for the customer.

   The core purpose of Muda is to identify and remove activities that consume resources but create no customer value, thereby maximizing value-adding work. While delays and handoffs are wastes, the card explicitly warns against blindly eliminating all forms, as some might be necessary, making option A incorrect.

   Read the full bite: The Seven Wastes of Software Development (Muda)

3. Question 3 of 30

   A software development team consistently observes that their Lead Time is significantly longer than their Cycle Time. What does this disparity most likely suggest?

   • aThe team should focus on optimizing their active development tasks to reduce the time spent coding.
   • bSignificant bottlenecks exist in the workflow before or after the team's active development phase.
   • cThe overall project scope is too ambitious, causing the entire development lifecycle to be prolonged.
   • dThe metrics are being miscalculated, as Lead Time and Cycle Time should ideally be very similar.
   Show the answer

   Answer: b · Significant bottlenecks exist in the workflow before or after the team's active development phase.

   The card explicitly states that "A large difference between Lead Time and Cycle Time signals that the biggest delays are happening outside of active development, in your queues and handoffs." Option A represents a common mistake, as focusing only on Cycle Time optimization ignores these larger, customer-impacting delays.

   Read the full bite: Cycle Time vs. Lead Time: Team Speed vs. Customer Wait

4. Question 4 of 30

   When a Scrum team is blocked by an external dependency, what is a Scrum Master's characteristic approach?

   • aDocument the dependency as a risk and adjust the sprint goal to account for potential delays.
   • bDirectly intervene with the external department to personally resolve the issue and unblock the team.
   • cRe-prioritize the Product Backlog to avoid the dependency until it's resolved by management.
   • dFacilitate communication, make the dependency visible, and coach the team to establish a resolution like an SLA.
   Show the answer

   Answer: d · Facilitate communication, make the dependency visible, and coach the team to establish a resolution like an SLA.

   The Scrum Master acts as a coach and facilitator, helping the team address impediments by making them visible and guiding the team to establish solutions, rather than solving the problem for them or managing the risk directly. The card's example shows the SM facilitating communication and coaching the team to create an SLA.

   Read the full bite: The Scrum Master: A Coach, Not a Manager

5. Question 5 of 30

   Which principle best describes the MoSCoW method's approach to project delivery?

   • aAdapting the project timeline to accommodate all identified requirements.
   • bPrioritizing all features equally to maintain stakeholder satisfaction.
   • cFocusing on delivering only the 'nice-to-have' features first to build momentum.
   • dAdjusting the scope of work to meet a predefined delivery schedule.
   Show the answer

   Answer: d · Adjusting the scope of work to meet a predefined delivery schedule.

   The MoSCoW method treats time as fixed and scope as flexible, meaning the scope is adjusted to ensure a viable product is delivered by a specific deadline. Option A is incorrect because MoSCoW is used when the timeline is fixed, not flexible.

   Read the full bite: The MoSCoW Method: Prioritizing for Fixed Deadlines

6. Question 6 of 30

   A product team consistently ships features from a long backlog but observes low user engagement. How would User Story Mapping most effectively address this challenge?

   • aIt streamlines the development process by eliminating unnecessary features, allowing the team to ship products faster.
   • bIt helps them visualize the entire user journey to identify core pain points and prioritize work based on customer value.
   • cIt provides a detailed, hierarchical breakdown of all features, enabling more efficient task allocation and tracking.
   • dIt ensures all team members are aware of every feature in the backlog, improving communication and reducing duplicate effort.
   Show the answer

   Answer: b · It helps them visualize the entire user journey to identify core pain points and prioritize work based on customer value.

   User Story Mapping shifts focus from merely shipping features (outputs) to understanding the user's journey and delivering valuable outcomes. By visualizing the entire experience, teams can identify critical pain points and re-prioritize work to address what truly impacts customer value, directly tackling low engagement. Option A is incorrect because the card explicitly states that 'finishing work quickly is meaningless if customers don't use or benefit,' emphasizing value over speed.

   Read the full bite: User Story Mapping: From Backlog to Value Map

7. Question 7 of 30

   How should a project manager engage a stakeholder with high power but low interest, according to the Power/Interest grid?

   • aManage them closely with frequent collaboration.
   • bKeep them satisfied with concise, high-level updates.
   • cMonitor them periodically with minimal engagement.
   • dKeep them informed and actively solicit their feedback.
   Show the answer

   Answer: b · Keep them satisfied with concise, high-level updates.

   The card states that High Power and Low Interest stakeholders should be 'kept satisfied with concise updates.' Managing closely is for High Power, High Interest, while keeping informed is for Low Power, High Interest.

   Read the full bite: Stakeholder Mapping: Prioritizing Voices by Power and Interest

8. Question 8 of 30

   When would a Scrum team find a formal Definition of Ready (DoR) most valuable?

   • aAs a tool for the Product Owner to strictly control story acceptance
   • bTo replace the need for regular backlog refinement meetings
   • cWhen sprints are frequently disrupted by unclear requirements or unexpected blockers
   • dIf the team consistently achieves high predictability and shared understanding
   Show the answer

   Answer: c · When sprints are frequently disrupted by unclear requirements or unexpected blockers

   The card states a formal DoR is most valuable "when teams frequently find their sprints derailed by surprises" or "when work gets blocked waiting for external dependencies or clearer requirements." Option A is incorrect because the card explicitly warns against using the DoR as a "contractual weapon or a bureaucratic gate."

   Read the full bite: Definition of Ready (DoR): The Bouncer for Your Sprint

9. Question 9 of 30

   For which situation is 'The Five Dysfunctions of a Team' model primarily intended?

   • aEnhancing the performance of an already highly effective and cohesive team.
   • bGuiding a newly assembled team through its initial formation stages.
   • cOffering a quick solution for immediate, surface-level team disagreements.
   • dDiagnosing the underlying reasons for an established team's persistent struggles.
   Show the answer

   Answer: d · Diagnosing the underlying reasons for an established team's persistent struggles.

   The card states this model is a diagnostic tool for teams not performing to their potential, focusing on understanding underlying issues in established teams. It explicitly mentions it is less relevant for newly formed or already high-functioning teams, and implies deeper issues than surface-level conflicts.

   Read the full bite: The Five Dysfunctions of a Team: A Model for Diagnosing Failure

10. Question 10 of 30

    When a newly formed team experiences significant conflict and challenges to authority, Tuckman's model suggests a manager should primarily view this as:

    • aAn expected and necessary phase for the team to address underlying issues and grow.
    • bAn opportunity to reinforce strict hierarchical control to prevent further dissent.
    • cA sign that individual personalities are incompatible and need mediation or replacement.
    • dA failure in the initial team formation process requiring immediate restructuring.
    Show the answer

    Answer: a · An expected and necessary phase for the team to address underlying issues and grow.

    The card states that conflict and disagreement during the 'Storming' phase are not signs of failure but are 'required steps on the path to high performance' and 'crucial for surfacing important issues.' Therefore, it's an expected and necessary phase, not a failure or a reason for immediate intervention to suppress it.

    Read the full bite: Tuckman's Stages: Why Teams Must Storm Before They Perform

11. Question 11 of 30

    Which action best exemplifies an Agile Coach's approach to a struggling team?

    • aDirectly instructing the team on the correct agile process steps to follow.
    • bTaking over sprint planning to ensure commitments are met and deadlines are hit.
    • cFacilitating a retrospective to help the team identify the root cause of their issues.
    • dProviding a detailed action plan for the team to implement to improve performance.
    Show the answer

    Answer: c · Facilitating a retrospective to help the team identify the root cause of their issues.

    The card emphasizes that an Agile Coach helps teams "unlock their own potential and find their own solutions" and specifically mentions facilitating a retrospective to discover root causes. While an Agile Coach teaches, they do not dictate specific solutions or manage tasks like a project manager, making direct instruction or providing a detailed plan less characteristic of their core approach.

    Read the full bite: Agile Coaching: Teacher, Mentor, Facilitator, Coach

12. Question 12 of 30

    What is the main objective when employing a powerful question?

    • aTo facilitate personal insight and explore unforeseen options.
    • bTo quickly gather precise factual information.
    • cTo subtly direct someone towards a predetermined solution.
    • dTo pinpoint accountability for past failures.
    Show the answer

    Answer: a · To facilitate personal insight and explore unforeseen options.

    Powerful questions are designed to make someone reflect and explore possibilities they hadn't considered, generating new insight for the person being asked. They are explicitly not for obtaining factual answers or for manipulating someone towards a solution the asker already knows.

    Read the full bite: Powerful Questions: Sparking Discovery, Not Just Answers

13. Question 13 of 30

    Which activity best exemplifies the 'horizontal bar' component of T-shaped skills?

    • aA UX researcher conducting comprehensive usability tests for a new product.
    • bA project manager specializing in agile methodologies and team coaching.
    • cA data scientist understanding the basics of data engineering to better integrate their models.
    • dA software engineer mastering advanced algorithms for system optimization.
    Show the answer

    Answer: c · A data scientist understanding the basics of data engineering to better integrate their models.

    The horizontal bar of T-shaped skills represents a broad ability to collaborate and understand other disciplines. A data scientist learning data engineering basics directly illustrates this by gaining enough knowledge in an adjacent field to improve collaboration and integration, as explicitly stated in the card. The other options describe deepening expertise within one's primary domain, which is the vertical bar.

    Read the full bite: T-Shaped Skills: Deep Expertise, Broad Collaboration

14. Question 14 of 30

    What is a primary advantage of implementing collective code ownership in a fast-paced development team?

    • aIt ensures that only the original author of a module can approve changes to it.
    • bIt minimizes the necessity for robust automated testing and continuous integration practices.
    • cIt enables seamless, widespread refactoring and prevents delays from module ownership boundaries.
    • dIt clearly defines individual responsibility for each component, improving accountability.
    Show the answer

    Answer: c · It enables seamless, widespread refactoring and prevents delays from module ownership boundaries.

    Collective code ownership allows any developer to change any part of the code, which is crucial for efficient refactoring across modules and preventing bottlenecks, as highlighted in the card's example. Option D describes a characteristic of strong or weak ownership, where individual accountability for specific components is emphasized, rather than the team-wide responsibility of collective ownership.

    Read the full bite: Collective Code Ownership: The Team Owns the Code

15. Question 15 of 30

    Which situation best exemplifies an appropriate use case for pair programming?

    • aA new team member is integrating a complex, security-sensitive authentication module.
    • bAn experienced engineer is exploring multiple experimental solutions for a future feature.
    • cA developer needs to fix a typo in a configuration file.
    • dTwo developers with known personality clashes are assigned to a routine task.
    Show the answer

    Answer: a · A new team member is integrating a complex, security-sensitive authentication module.

    Pair programming is ideal for complex or critical features, especially when onboarding new team members, as it allows for real-time error detection and knowledge transfer. It is not recommended for simple tasks, highly exploratory work, or when team chemistry is poor.

    Read the full bite: Pair Programming: Two Heads, One Keyboard

16. Question 16 of 30

    What is the primary purpose of an Agile Theme in strategic planning?

    • aTo organize and communicate how multiple epics align with a major business objective.
    • bTo manage a collection of small, independent tasks that lack a common strategic goal.
    • cTo detail the technical specifications for a new product feature.
    • dTo track the completion status of all tasks within a single development sprint.
    Show the answer

    Answer: a · To organize and communicate how multiple epics align with a major business objective.

    An Agile Theme serves as a strategic focus that groups related epics to achieve a larger business goal and communicate this alignment to stakeholders. It is not intended for detailing technical specifications or tracking individual sprint tasks, which are lower-level concerns.

    Read the full bite: Agile Themes: Connecting Work to Strategy

17. Question 17 of 30

    Which problem does the adoption of a DEEP Product Backlog primarily aim to solve for an agile team?

    • aThe product owner consistently struggles to generate a sufficient volume of new ideas for the backlog.
    • bThe development team spends excessive time on story refinement, resulting in minimal actual delivery of value.
    • cLeadership has lost confidence in the team's ability to provide accurate and reliable project forecasts.
    • dStakeholders frequently introduce new requirements for features already under active development.
    Show the answer

    Answer: b · The development team spends excessive time on story refinement, resulting in minimal actual delivery of value.

    The card explicitly states that a DEEP backlog prevents the 'quicksand of endless refinement with no progress' and helps when 'messy backlogs are causing teams to spin their wheels on refinement instead of delivering work.' While restoring confidence in forecasts (C) is a key outcome, it is a result of addressing the underlying process problem described in C.

    Read the full bite: What is a DEEP Product Backlog?

18. Question 18 of 30

    Which scenario best illustrates the primary benefit of using a Job Story over a traditional User Story?

    • aDocumenting a feature where the user's specific job title dictates their workflow.
    • bDesigning an internal tool where different employee roles have distinct permissions.
    • cCreating a requirement for a feature that is a direct enhancement of an existing user story.
    • dExploring a user need where the underlying motivation and context are more critical than their demographic.
    Show the answer

    Answer: d · Exploring a user need where the underlying motivation and context are more critical than their demographic.

    Job Stories are most effective when the user's context and motivation are paramount, helping to uncover the root cause of a need, rather than focusing on a specific persona. Options A and B describe situations where specific roles and permissions are critical, which the card indicates is where traditional User Stories are more effective.

    Read the full bite: Job Stories: Focus on Motivation, Not Persona

19. Question 19 of 30

    Which of the following is the most critical input for developing effective user personas?

    • aDetailed job descriptions for the target roles a product aims to serve.
    • bAssumptions about user needs and behaviors based on industry best practices.
    • cCreative brainstorming sessions among the product development team.
    • dData collected from real user research, such as interviews and surveys.
    Show the answer

    Answer: d · Data collected from real user research, such as interviews and surveys.

    The card explicitly states that "Personas are built from user research, not imagination," emphasizing the collection of data through interviews, surveys, and analytics. While other options might play a role in product development, only real user data forms the foundation for effective personas.

    Read the full bite: Personas: Build for a Specific 'Who', Not a Vague 'Everyone'

20. Question 20 of 30

    According to the card, what is the primary negative consequence of converting story points directly to hours in relative sizing?

    • aIt reduces the team's ability to quickly generate estimates for a large number of items.
    • bIt complicates the process of selecting a suitable baseline task for comparison.
    • cIt makes it impossible to use historical velocity data for future sprint forecasting.
    • dIt undermines the abstraction of complexity and introduces a false sense of precise time-based commitment.
    Show the answer

    Answer: d · It undermines the abstraction of complexity and introduces a false sense of precise time-based commitment.

    The card explicitly states that converting points to hours "destroys the psychological safety and abstraction that makes relative sizing effective, turning points into just another word for hours." This defeats the purpose of relative estimation by reintroducing a misleading focus on absolute time. Option C is incorrect because velocity can still be tracked, but its meaning changes from relative effort to absolute time, which is the problem.

    Read the full bite: Relative Sizing: Estimate Effort, Not Hours

21. Question 21 of 30

    What is the fundamental shift in approach that Continuous Integration (CI) introduces to software development?

    • aIt mandates that developers work in isolation on large feature branches until a single, final merge.
    • bIt ensures code is only integrated into the main branch after a full release cycle is complete.
    • cIt transforms code integration into a frequent, automated process to detect issues immediately.
    • dIt primarily focuses on eliminating all forms of manual testing through comprehensive automation.
    Show the answer

    Answer: c · It transforms code integration into a frequent, automated process to detect issues immediately.

    C is correct because CI's core idea is to make integration a frequent, automated event, catching issues immediately when they are small. Option D is incorrect as CI's fundamental shift is about the integration process, not solely eliminating all manual testing.

    Read the full bite: Continuous Integration: Catching Bugs Early

22. Question 22 of 30

    For which of the following use cases would a feature toggle generally be considered an inappropriate solution?

    • aStoring a system-wide configuration setting that is expected to remain constant for years.
    • bConducting an A/B test to compare two different checkout flows.
    • cGradually rolling out a new user interface to a small percentage of users.
    • dProviding a mechanism to quickly disable a new search algorithm if it performs poorly.
    Show the answer

    Answer: a · Storing a system-wide configuration setting that is expected to remain constant for years.

    The card explicitly states to "Avoid using toggles for permanent configuration or architectural seams; they are meant for transient states." Options A, B, and C are all described as appropriate, temporary uses for feature toggles.

    Read the full bite: Feature Toggles: Decouple Deployment from Release

23. Question 23 of 30

    In a Cumulative Flow Diagram, what does a steadily widening band for a specific workflow state primarily indicate?

    • aThe overall project's Work In Progress (WIP) is increasing.
    • bThe team members assigned to that stage are not performing effectively.
    • cThe project is experiencing an unexpected increase in scope or new work items.
    • dWork items are entering that stage at a faster rate than they are being completed and moved to the next stage.
    Show the answer

    Answer: d · Work items are entering that stage at a faster rate than they are being completed and moved to the next stage.

    The card explicitly states that "If a band gets wider over time, it means more work is entering that stage than leaving it, signaling a bottleneck." This directly corresponds to option D. Option B is a common misinterpretation, as CFDs are not for tracking individual performance but for identifying systemic issues.

    Read the full bite: Cumulative Flow Diagrams: Spotting Workflow Bottlenecks

24. Question 24 of 30

    Which scenario best illustrates the appropriate use of a fishbone diagram?

    • aA business analyst wants to validate a hypothesis with clear metrics.
    • bA project manager needs to assign responsibility for a recent project failure.
    • cA developer needs to quickly fix a bug with a known cause in production.
    • dA team consistently misses sprint goals and wants to uncover underlying systemic issues.
    Show the answer

    Answer: d · A team consistently misses sprint goals and wants to uncover underlying systemic issues.

    A fishbone diagram is designed for complex problems where causes are not obvious, such as systemic issues affecting sprint goals, making option D correct. It is explicitly stated as an anti-pattern to use it for assigning blame (option B), overkill for simple problems with known causes (option C), and not a substitute for clear data (option A).

    Read the full bite: Fishbone Diagram: Mapping Problems to Root Causes

25. Question 25 of 30

    For which scenario would applying the SMART framework likely be least beneficial?

    • aSetting individual development goals for an annual performance review
    • bDefining the scope and deliverables for a short-term project
    • cDeveloping a high-level, inspirational mission statement for a startup
    • dEstablishing clear, quantifiable targets for a new marketing campaign
    Show the answer

    Answer: c · Developing a high-level, inspirational mission statement for a startup

    The card states that SMART is "less useful for high-level, aspirational vision statements" because it's a tool for tactical execution, not strategic direction. The other options are all examples where SMART is explicitly recommended for setting concrete, actionable goals.

    Read the full bite: SMART Goals: From Vague Hopes to Actionable Plans

26. Question 26 of 30

    A team lead needs to address an employee's consistent underperformance on project deadlines. Which approach best exemplifies Radical Candor?

    • aExpress belief in the employee's potential, then clearly outline specific performance gaps and offer support.
    • bDirectly state the performance issues and their negative impact, without dwelling on personal feelings.
    • cHint at the performance issues in a team meeting, letting the employee infer the feedback.
    • dAvoid confronting the employee to protect their feelings, hoping they will eventually improve.
    Show the answer

    Answer: a · Express belief in the employee's potential, then clearly outline specific performance gaps and offer support.

    Radical Candor combines 'Care Personally' (expressing belief, offering support) with 'Challenge Directly' (clearly outlining specific gaps). Option B represents Obnoxious Aggression, as it challenges directly but lacks personal care.

    Read the full bite: Radical Candor: Care Personally, Challenge Directly

27. Question 27 of 30

    What is a primary benefit of the 4Ls retrospective compared to only discussing "what went wrong"?

    • aIt provides a holistic view by incorporating positive experiences and future needs.
    • bIt focuses solely on technical issues, leading to more precise solutions.
    • cIt guarantees anonymity for all feedback, promoting honesty.
    • dIt is primarily designed for very large teams to conduct formal root cause analysis.
    Show the answer

    Answer: a · It provides a holistic view by incorporating positive experiences and future needs.

    The 4Ls retrospective explicitly balances positive, negative, and forward-looking insights through its 'Loved' and 'Longed for' categories, offering a holistic view beyond just problems. It is noted as less effective for very large groups and not a substitute for deep-dive technical root cause analysis.

    Read the full bite: The 4Ls Retrospective: Loved, Loathed, Longed For, Learned

28. Question 28 of 30

    During the "Refactor" phase of Test-Driven Development, what is the main objective?

    • aTo improve the design and readability of the code while ensuring all tests still pass.
    • bTo write the minimum amount of code necessary to make the previously failing test pass.
    • cTo add new features or functionalities to the system.
    • dTo identify and fix any bugs introduced during the "Green" phase.
    Show the answer

    Answer: a · To improve the design and readability of the code while ensuring all tests still pass.

    The "Refactor" phase focuses on improving the code's structure, removing duplication, and enhancing clarity, all while maintaining functionality and ensuring existing tests continue to pass. Option B describes the "Green" phase, where minimal code is written to pass the test.

    Read the full bite: Test-Driven Development: The Red, Green, Refactor Cycle

29. Question 29 of 30

    What is the fundamental purpose of Behavior-Driven Development (BDD) in software development?

    • aTo establish a common, executable understanding of feature requirements between business and technical teams.
    • bTo replace manual quality assurance processes entirely with automated Gherkin-based tests.
    • cTo generate comprehensive documentation for features after their implementation.
    • dTo ensure all low-level code functions are thoroughly tested with automated scripts.
    Show the answer

    Answer: a · To establish a common, executable understanding of feature requirements between business and technical teams.

    BDD's core purpose is to bridge the communication gap and create a shared, executable understanding of how a feature should behave among all stakeholders. While BDD produces documentation, the card explicitly warns against writing scenarios after coding, emphasizing its role in collaborative design, not post-implementation documentation.

    Read the full bite: Behavior-Driven Development (BDD): Requirements as Tests

30. Question 30 of 30

    Which statement accurately describes a fundamental characteristic of successful code refactoring?

    • aIt involves making small, behavior-preserving transformations, validated by running tests after each change.
    • bIt prioritizes immediate performance gains, even if it temporarily impacts code readability.
    • cIt aims to introduce new features more efficiently by reorganizing existing code.
    • dIt is typically a large-scale overhaul of a system's architecture to fix fundamental design flaws.
    Show the answer

    Answer: a · It involves making small, behavior-preserving transformations, validated by running tests after each change.

    The card explicitly states that refactoring is done through "a series of small, behavior-preserving transformations" and that "Each small change... is followed by running a test suite." Option C is incorrect because refactoring improves the 'how' without changing the 'what', meaning it doesn't introduce new features itself.

    Read the full bite: Refactoring: Cleaning Code Without Breaking It