Question 1: A team notices that many user stories share a common underlying need across different roles. Which refinement technique BEST addresses this pattern?

• Story abstraction into an epic (Correct answer)
• Retrospective action item
• Spike solution
• Velocity recalculation

Correct answer: Story abstraction into an epic

When multiple stories share a common theme or need, abstracting them into an epic helps organize work and reveals the broader feature being built.

Question 2: During a retrospective, two team members dominate the conversation while others stay silent. What should the facilitator do first?

• End the retrospective early
• Escalate the behavior to management
• Use structured techniques like round-robin sharing to include all voices (Correct answer)
• Ask the silent members to speak up individually

Correct answer: Use structured techniques like round-robin sharing to include all voices

Structured facilitation techniques ensure equal participation without singling out individuals or creating confrontation.

Question 3: What is the purpose of a RACI matrix in the context of stakeholder engagement?

• To rank stakeholders by political influence
• To track sprint velocity by team member
• To clarify who is Responsible, Accountable, Consulted, and Informed for each decision or deliverable (Correct answer)
• To assign story points to user stories

Correct answer: To clarify who is Responsible, Accountable, Consulted, and Informed for each decision or deliverable

A RACI matrix eliminates ambiguity about decision rights and communication obligations across stakeholder groups.

Question 4: Which Kanban principle directly addresses preventing team members from taking on too much work at once?

• Limit Work in Progress (WIP) (Correct answer)
• Make process policies explicit
• Manage flow
• Visualize the workflow

Correct answer: Limit Work in Progress (WIP)

Limiting Work in Progress (WIP) is a core Kanban principle that prevents multitasking overload and improves throughput by constraining how many items can be in each workflow stage.

Question 5: What is the 'definition of done' (DoD) and why is it critical for release readiness?

• A manager's approval sign-off process
• A synonym for the acceptance criteria of a single story
• A list of features the product owner wants in the next sprint
• A shared checklist that defines when an increment is truly complete and releasable (Correct answer)

Correct answer: A shared checklist that defines when an increment is truly complete and releasable

The DoD ensures every increment meets quality, testing, and documentation standards before it is considered releasable, reducing post-release surprises.

Question 6: The 'Start, Stop, Continue' retrospective technique is best described as:

• A framework for categorizing team behaviors into actions, eliminations, and reinforcements (Correct answer)
• A risk identification framework
• A sprint review template for stakeholders
• A method for prioritizing backlog items

Correct answer: A framework for categorizing team behaviors into actions, eliminations, and reinforcements

'Start, Stop, Continue' sorts team feedback into new behaviors to adopt, behaviors to eliminate, and behaviors to maintain.

Question 7: A backlog item has dependencies on work managed by another team. How should the Product Owner handle this in backlog management?

• Assign all dependent work to one team to eliminate the dependency
• Remove the item until the dependency is resolved on its own
• Ignore the dependency and let the teams resolve it during the sprint
• Identify and make dependencies explicit in the backlog, and coordinate with the other team's Product Owner (Correct answer)

Correct answer: Identify and make dependencies explicit in the backlog, and coordinate with the other team's Product Owner

Explicit dependency management—flagging items and coordinating across teams—prevents sprint disruptions and reduces integration risks.

Question 8: A product owner writes ten new user stories before a refinement session. Which preparatory step adds the MOST value before the session begins?

• Schedule individual meetings with each team member to explain the stories
• Review and prioritize the stories so the team focuses on the most important ones first (Correct answer)
• Convert all stories into tasks before the session
• Assign story point estimates to each story in advance

Correct answer: Review and prioritize the stories so the team focuses on the most important ones first

Prioritizing stories before refinement ensures the team spends limited session time on the highest-value items rather than working through a random list.

Question 9: What does a 'Cumulative Flow Diagram (CFD)' primarily reveal about a Kanban system?

• The velocity of each team member
• The total number of features completed per sprint
• The flow of work through each stage and the size of queues over time (Correct answer)
• The priority ordering of the backlog

Correct answer: The flow of work through each stage and the size of queues over time

A CFD visualizes how work accumulates and moves through each stage over time, making WIP, queue sizes, and approximate cycle time visible.

Question 10: What is 'sprint goal' and why is it important during sprint planning?

• The total story points committed for the sprint
• The product increment to be delivered at sprint end
• A list of all user stories to be completed in the sprint
• A single objective that gives the sprint purpose and guides team decisions (Correct answer)

Correct answer: A single objective that gives the sprint purpose and guides team decisions

The sprint goal provides a cohesive objective that helps the team stay focused and make trade-off decisions if challenges arise during the sprint.

Question 11: A Scrum team consistently fails to complete all sprint backlog items by the end of the sprint. According to Scrum, what is the MOST appropriate response?

• Extend the sprint until all items are complete
• Move incomplete items back to the Product Backlog and re-prioritize with the Product Owner (Correct answer)
• Ask the Scrum Master to assign tasks more evenly among team members
• Reduce the team's velocity target for future sprints automatically

Correct answer: Move incomplete items back to the Product Backlog and re-prioritize with the Product Owner

Incomplete Sprint Backlog items return to the Product Backlog at the end of the sprint, where the Product Owner re-prioritizes them; the sprint itself never extends.

Question 12: What is the BEST description of Backlog Refinement (grooming) in Scrum?

• An ongoing activity where the team adds detail, estimates, and order to Product Backlog items (Correct answer)
• A meeting led by the Scrum Master to prioritize backlog items
• A formal ceremony where the Product Owner presents the backlog to stakeholders
• A mandatory Scrum event held at the start of each Sprint

Correct answer: An ongoing activity where the team adds detail, estimates, and order to Product Backlog items

Backlog Refinement is an ongoing collaborative activity, not a formal Scrum event, where detail and estimates are added to Product Backlog items.

Question 13: When a conflict arises between standard procedures and a unique situation in Sprint Planning & Estimation, what should a APM professional prioritize?

• Strict adherence to written procedures without exception
• The preference of the client or stakeholder
• The most cost-effective solution available
• Safety and ethical obligations while seeking expert consultation (Correct answer)

Correct answer: Safety and ethical obligations while seeking expert consultation

Safety and ethics always take priority in Sprint Planning & Estimation. When standard procedures don't adequately address a unique situation, consulting with experienced colleagues or supervisors ensures both safety and professional standards are maintained.

Question 14: What is the maximum recommended duration for a Daily Scrum?

• 1 hour
• 45 minutes
• 30 minutes
• 15 minutes (Correct answer)

Correct answer: 15 minutes

The Daily Scrum is time-boxed to 15 minutes to keep the team focused and the meeting efficient.

Question 15: A Product Owner is managing a backlog for a B2B SaaS product and receives conflicting feature requests from two high-value clients. What is the BEST approach?

• Prioritize the client that generates more revenue without analysis
• Build both features simultaneously to satisfy both clients
• Delegate the decision to the development team
• Evaluate both requests against the product vision and overall user base impact, then decide (Correct answer)

Correct answer: Evaluate both requests against the product vision and overall user base impact, then decide

Decisions on conflicting requests should align with the product vision and serve the broadest user base, not just be driven by individual client pressure.

Question 16: Which roadmap format is BEST suited for communicating high-level strategic direction to executive stakeholders without committing to specific delivery dates?

• Sprint backlog view
• Gantt chart with fixed milestones
• Detailed feature changelog
• Now-Next-Later roadmap (Correct answer)

Correct answer: Now-Next-Later roadmap

A Now-Next-Later roadmap conveys strategic sequencing without locking in delivery dates, making it ideal for executive communication.

Question 17: What is the primary difference between a product roadmap and a product backlog?

• A roadmap communicates strategic direction and timelines; a backlog is the ordered list of work items (Correct answer)
• A roadmap lists all user stories; a backlog lists epics only
• A roadmap is updated daily; a backlog is updated annually
• A roadmap is owned by engineering; a backlog is owned by marketing

Correct answer: A roadmap communicates strategic direction and timelines; a backlog is the ordered list of work items

The roadmap is a strategic communication artifact showing direction and timing, while the backlog is the tactical, ordered list of work for the development team.

Question 18: How does continuous delivery (CD) change the nature of release planning for an Agile team?

• It allows teams to release small, validated increments frequently, reducing the scope and risk of each release event (Correct answer)
• It eliminates the need for any release coordination
• It centralizes release authority to a single team
• It requires longer release cycles with more testing

Correct answer: It allows teams to release small, validated increments frequently, reducing the scope and risk of each release event

CD enables small, frequent releases, shifting the planning focus from big-bang launches to sustainable flow and deployment pipelines.

Question 19: A new Scrum Team member asks why Sprint length should remain consistent. What is the BEST answer?

• It makes it easier for management to track progress on a fixed calendar
• Consistent length prevents the team from delivering too early
• It is required by the Scrum Guide and cannot be changed
• Consistent Sprint length establishes cadence, reduces planning overhead, and enables meaningful velocity trends (Correct answer)

Correct answer: Consistent Sprint length establishes cadence, reduces planning overhead, and enables meaningful velocity trends

Consistent Sprint length creates a sustainable cadence, simplifies planning, and provides stable data for forecasting.

Question 20: Which metric helps an Agile team determine if their estimation process is improving over time?

• Number of retrospectives held
• Estimation accuracy trend (planned vs. actual story points) (Correct answer)
• Stakeholder satisfaction score
• Total number of story points delivered

Correct answer: Estimation accuracy trend (planned vs. actual story points)

Tracking planned versus actual story points over time reveals whether the team's estimation accuracy is improving across sprints.

Question 21: A Scrum team is planning their first sprint with no historical velocity. What is the BEST approach to determine sprint commitment?

• Ask management to set an initial velocity target
• Make an educated team estimate and treat the first sprint as a calibration sprint (Correct answer)
• Use industry benchmark velocity for teams of the same size
• Commit to zero stories until velocity is established

Correct answer: Make an educated team estimate and treat the first sprint as a calibration sprint

New teams should make their best initial estimate collaboratively and use the first sprint to gather real data for future calibration rather than paralysis or external imposition.

Question 22: What is 'feature freeze' in the context of Agile release planning?

• A technique to prioritize features by business value
• A point in time when no new features are added to the release scope to allow stabilization (Correct answer)
• A method for estimating story points
• A daily standup agenda item

Correct answer: A point in time when no new features are added to the release scope to allow stabilization

Feature freeze allows the team to focus on stabilization, testing, and bug fixes without new scope being introduced before a release.

Question 23: In Agile reporting, what is the distinction between 'lagging indicators' and 'leading indicators'?

• Lagging indicators predict future performance; leading indicators confirm past results
• Lagging indicators are used only in Kanban; leading indicators only in Scrum
• Both types measure the same things at different time intervals
• Leading indicators predict future performance; lagging indicators confirm past results (Correct answer)

Correct answer: Leading indicators predict future performance; lagging indicators confirm past results

Leading indicators (e.g., WIP levels) predict future outcomes, while lagging indicators (e.g., velocity) confirm what has already happened.

Question 24: What distinguishes Key Results from tasks or initiatives in the OKR framework?

• Key Results are set annually while initiatives are defined each sprint
• Key Results describe the work to be done while initiatives describe the expected outcomes
• Key Results are measurable outcomes signaling progress toward the Objective, not activities (Correct answer)
• Key Results are assigned to individuals while initiatives are team-wide

Correct answer: Key Results are measurable outcomes signaling progress toward the Objective, not activities

Key Results must be measurable outcomes that signal progress toward the Objective — they answer 'how will we know we succeeded,' not 'what will we do.'

Question 25: An Agile Release Train in SAFe has just completed a Program Increment. Which event allows teams to inspect their practices and identify process improvements at the ART level?

• Sprint Retrospective
• Scrum of Scrums
• System Demo
• Inspect and Adapt (I&A) Workshop (Correct answer)

Correct answer: Inspect and Adapt (I&A) Workshop

The Inspect and Adapt (I&A) Workshop is a SAFe event held at the end of each PI where the entire ART reviews performance and identifies systemic improvements through structured problem-solving.

Question 26: What is the risk of committing to 100% of the team's calculated velocity every sprint?

• It reduces the Product Owner's ability to reprioritize the backlog
• It causes the Definition of Done to become too strict
• It makes sprint planning sessions longer than necessary
• It leaves no buffer for unexpected issues, technical debt, or unplanned work (Correct answer)

Correct answer: It leaves no buffer for unexpected issues, technical debt, or unplanned work

Committing to 100% velocity assumes perfect conditions; most teams reserve a buffer for bugs, meetings, and unforeseen complexity.

Question 27: Which of the following is a leading indicator that an Agile team may miss its release commitment?

• High team satisfaction scores
• Increasing cycle time and growing work-in-progress (WIP) (Correct answer)
• Declining defect density
• Consistent sprint velocity

Correct answer: Increasing cycle time and growing work-in-progress (WIP)

Rising cycle time and WIP signal bottlenecks or scope creep that will erode throughput and threaten the release timeline.

Question 28: How does risk management apply to daily practice in Sprint Planning & Estimation for Agile Product Management professionals?

• Through annual safety audits exclusively
• Only through responding to incidents after they occur
• By avoiding high-risk situations entirely
• Through proactive identification of potential hazards and implementation of preventive measures (Correct answer)

Correct answer: Through proactive identification of potential hazards and implementation of preventive measures

Effective risk management in Sprint Planning & Estimation requires proactive hazard identification and preventive measures, not just reactive responses. This approach reduces incidents, improves outcomes, and protects both professionals and clients.

Question 29: When a conflict arises between standard procedures and a unique situation in User Story Development & Refinement, what should a APM professional prioritize?

• The preference of the client or stakeholder
• Safety and ethical obligations while seeking expert consultation (Correct answer)
• The most cost-effective solution available
• Strict adherence to written procedures without exception

Correct answer: Safety and ethical obligations while seeking expert consultation

Safety and ethics always take priority in User Story Development & Refinement. When standard procedures don't adequately address a unique situation, consulting with experienced colleagues or supervisors ensures both safety and professional standards are maintained.

Question 30: How should teams ensure they are aligned with stakeholders throughout the Agile process?

• By only involving stakeholders at the beginning of the project.
• By delivering the product without seeking stakeholder input.
• By working independently and presenting the final product.
• By regularly engaging stakeholders in sprint reviews and feedback sessions.

To ensure alignment with stakeholders throughout the Agile process, teams must prioritize continuous and active engagement. Regularly inviting stakeholders to sprint reviews allows them to see working increments, provide direct feedback, and understand the product's evolution. These feedback sessions and open communication channels ensure that the product remains aligned with their evolving needs and business goals.

Question 31: A product owner is using the Kano model. Which category describes features that cause dissatisfaction if absent but provide no delight when present?

• Basic (must-be) (Correct answer)
• Performance (linear)
• Indifferent
• Excitement (delighters)

Correct answer: Basic (must-be)

Basic/must-be features are expected by users — their absence causes dissatisfaction, but their presence is simply taken for granted and doesn't increase satisfaction.

Question 32: What does 'assumption mapping' help a product team identify?

• Dependencies between engineering teams
• The sprint schedule for the quarter
• The technical architecture of the system
• Which beliefs about users, market, or business model carry the most risk and uncertainty (Correct answer)

Correct answer: Which beliefs about users, market, or business model carry the most risk and uncertainty

Assumption mapping plots beliefs on axes of risk and uncertainty, helping teams prioritize which assumptions to test first.

Question 33: A Scrum team uses Fibonacci numbers (1, 2, 3, 5, 8, 13...) for story point estimation. Why are non-linear sequences preferred?

• They are easier to calculate during planning poker
• They reflect increasing uncertainty as story complexity grows (Correct answer)
• They allow more precise estimation for large stories
• They are required by the Scrum Guide

Correct answer: They reflect increasing uncertainty as story complexity grows

Non-linear sequences acknowledge that larger, more complex stories carry greater uncertainty, making granular distinctions between large estimates meaningless.

Question 34: What is the recommended time-box for Sprint Planning in a two-week Sprint?

• 8 hours
• 2 hours
• 1 hour
• 4 hours (Correct answer)

Correct answer: 4 hours

Sprint Planning for a two-week Sprint is time-boxed to 4 hours (proportionally half of the 8-hour maximum for a one-month Sprint).

Question 35: Which standard of practice is MOST important for ensuring quality in Retrospectives & Continuous Improvement?

• Strictly adhering to the same procedure in every situation
• Using the most advanced technology available regardless of need
• Minimizing documentation to focus on practical work
• Following evidence-based protocols while adapting to specific circumstances (Correct answer)

Correct answer: Following evidence-based protocols while adapting to specific circumstances

Evidence-based protocols provide a foundation of proven practices, but effective Agile Product Management professionals must also adapt their approach based on specific circumstances and individual case needs within Retrospectives & Continuous Improvement.

Question 36: What is 'capacity-based' sprint planning and when is it most useful?

• Planning based on actual available person-hours, useful when team composition changes (Correct answer)
• Planning based on business value, useful when ROI is the top priority
• Planning based on story priority, useful when the backlog is long
• Planning based on team velocity only, useful for stable teams

Correct answer: Planning based on actual available person-hours, useful when team composition changes

Capacity-based planning calculates available work hours per team member and is especially useful when velocity is unreliable due to team or schedule changes.

Question 37: What should be included in a product vision statement?

• Detailed user stories and technical requirements.
• The product’s purpose, target audience, and problem it solves. (Correct answer)
• A list of features and their specifications.
• The exact release dates for the product’s features.

Correct answer: The product’s purpose, target audience, and problem it solves.

A strong product vision statement clearly articulates the core purpose of the product, identifying who it is for (target audience) and what specific problem it aims to solve. This concise statement provides a foundational understanding for all stakeholders, guiding strategic decisions and ensuring the product remains focused on delivering value. It avoids detailed specifications, which belong in the backlog.

Question 38: A Developer raises an impediment during the Daily Scrum that only the Scrum Master can resolve. What should happen?

• The Developer stops working until the impediment is removed
• The Sprint is cancelled until the impediment is cleared
• The impediment is noted and the Scrum Master addresses it after the Daily Scrum (Correct answer)
• The Daily Scrum is extended until the impediment is resolved

Correct answer: The impediment is noted and the Scrum Master addresses it after the Daily Scrum

Impediments raised in the Daily Scrum are addressed separately after the meeting to keep it within its 15-minute time-box.

Question 39: How does T-shirt sizing differ from story point estimation?

• T-shirt sizing is a rough relative grouping; story points provide more granular relative estimates (Correct answer)
• T-shirt sizing accounts for calendar time; story points do not
• T-shirt sizing is only used for epics; story points are only for stories
• T-shirt sizing uses numbers while story points use letters

Correct answer: T-shirt sizing is a rough relative grouping; story points provide more granular relative estimates

T-shirt sizing (XS, S, M, L, XL) provides quick high-level groupings for early backlog sizing, while story points offer finer granularity for sprint-level planning.

Question 40: What does 'managing up' mean in the context of stakeholder engagement for a product manager?

• Escalating every decision to senior leadership for approval
• Reporting every team issue to management immediately
• Avoiding conflict with senior stakeholders at all costs
• Proactively informing and influencing executives to gain support for product decisions (Correct answer)

Correct answer: Proactively informing and influencing executives to gain support for product decisions

Managing up means keeping executives appropriately informed and building their confidence in the product direction without requiring their involvement in every detail.

Question 41: A Product Owner wants to change the Sprint Goal midway through a Sprint. What should the Scrum Master do?

• Coach the Product Owner that the Sprint Goal should not change during a Sprint (Correct answer)
• Cancel the Sprint immediately
• Call an emergency Sprint Planning session
• Allow the change if the team agrees

Correct answer: Coach the Product Owner that the Sprint Goal should not change during a Sprint

The Sprint Goal should remain stable throughout the Sprint; the Scrum Master coaches the team on this principle.

Question 42: What distinguishes a 'spike' from a standard user story in agile product management?

• A spike is a user story written by the development team rather than the product owner
• A spike represents a non-functional requirement
• A spike is a large user story that spans multiple sprints
• A spike is a time-boxed research task to reduce uncertainty, not deliver working software (Correct answer)

Correct answer: A spike is a time-boxed research task to reduce uncertainty, not deliver working software

Spikes are time-boxed investigation or research tasks used to answer specific technical or design questions that block story refinement.

Question 43: During backlog refinement, a stakeholder insists a low-priority feature should be built immediately. How should the product manager respond?

• Explain the prioritization criteria and show how it ranks against current commitments (Correct answer)
• Add it to the next sprint to keep the stakeholder happy
• Defer the conversation until the sprint retrospective
• Escalate to the development team to make the call

Correct answer: Explain the prioritization criteria and show how it ranks against current commitments

Transparent prioritization criteria help stakeholders understand trade-offs without creating arbitrary exceptions.

Question 44: What is a key benefit of having a prioritized product backlog?

• It ensures that the team focuses on the most important and valuable tasks first.
• It guarantees that all tasks will be completed on time.
• It ensures that the team always works on the easiest tasks first.
• It minimizes project costs.

A key benefit of having a prioritized product backlog is that it provides a clear roadmap for the development team, ensuring they consistently work on the items that deliver the highest value. By ordering items based on business value, customer impact, and other factors, the team maximizes the return on investment and delivers the most critical features early and often. This focus optimizes resource allocation and product outcomes.

Question 45: What is the PRIMARY purpose of continuing education requirements in Scrum Framework & Ceremonies for APM professionals?

• Maintaining current knowledge and competency as the field evolves (Correct answer)
• Networking with other professionals in the field
• Fulfilling mandatory regulatory requirements only
• Earning additional credentials for career advancement

Correct answer: Maintaining current knowledge and competency as the field evolves

Continuing education in Scrum Framework & Ceremonies ensures professionals maintain current knowledge and skills as standards, technologies, and best practices evolve in the Agile Product Management field.

Question 46: What is the key advantage of a 'rolling wave' approach to metrics reporting in large Agile programs?

• It replaces the release burnup chart
• It provides detailed near-term metrics while keeping longer-term projections at a higher level (Correct answer)
• It allows teams to skip metric collection for early sprints
• It eliminates the need for sprint reviews

Correct answer: It provides detailed near-term metrics while keeping longer-term projections at a higher level

Rolling wave reporting gives precise metrics for near-term work and progressively less detailed projections for future work, matching the certainty of information available.

Question 47: What documentation practice is considered essential in Scrum Framework & Ceremonies within the Agile Product Management field?

• Recording actions, observations, and outcomes in real-time or as close to the event as possible (Correct answer)
• Using shorthand notes that can be expanded later if needed
• Completing all documentation at the end of the workday
• Only documenting unusual events or complications

Correct answer: Recording actions, observations, and outcomes in real-time or as close to the event as possible

Real-time or near-real-time documentation in Scrum Framework & Ceremonies ensures accuracy, provides a contemporaneous record, and is considered the gold standard for professional accountability and legal defensibility.

Question 48: What is the key difference between 'usability testing' and 'concept testing' in product discovery?

• Both are identical methods
• Concept testing tests if users can complete tasks; usability testing tests if they want the product
• Usability testing evaluates ease of use on an existing design; concept testing evaluates desirability of an idea (Correct answer)
• Concept testing is done post-launch only

Correct answer: Usability testing evaluates ease of use on an existing design; concept testing evaluates desirability of an idea

Usability testing focuses on how easily users can interact with a design, while concept testing evaluates whether they desire the idea at all.

Question 49: What is the recommended achievement rate for OKRs that signals the goals were appropriately ambitious?

• 70–75% (Correct answer)
• 50–60%
• 90–100%
• Exactly 100%

Correct answer: 70–75%

A 70–75% achievement rate is the widely accepted ideal, indicating goals were stretch targets — ambitious without being impossible.

Question 50: Which Agile technique helps teams split large backlog items (epics) into smaller, deliverable stories?

• Story splitting (Correct answer)
• Dependency mapping
• Velocity tracking
• Release burndown charting

Correct answer: Story splitting

Story splitting techniques — such as splitting by workflow step, data variation, or acceptance criteria — break epics into sprint-sized user stories.

Question 51: When calculating ROI for an Agile initiative, which two elements are essential inputs?

• Stakeholder count and meeting frequency
• Value delivered and cost of delivery (Correct answer)
• Story points completed and defect count
• Team velocity and sprint length

Correct answer: Value delivered and cost of delivery

ROI requires comparing the business value generated (value delivered) against the resources consumed (cost of delivery) to determine return.

Question 52: What is 'relative estimation' and what is its core advantage over absolute estimation?

• Estimating in real hours for accuracy; advantage is precision
• Using team averages to smooth out individual biases; advantage is fairness
• Estimating only relative to the team's top priority story; advantage is focus
• Comparing story size to other stories rather than time; advantage is speed and consistency (Correct answer)

Correct answer: Comparing story size to other stories rather than time; advantage is speed and consistency

Relative estimation leverages the human ability to compare sizes accurately without needing to predict specific durations, making estimates faster and more consistent across team members.

Question 53: Which standard of practice is MOST important for ensuring quality in Kanban & Lean Principles?

• Minimizing documentation to focus on practical work
• Using the most advanced technology available regardless of need
• Following evidence-based protocols while adapting to specific circumstances (Correct answer)
• Strictly adhering to the same procedure in every situation

Correct answer: Following evidence-based protocols while adapting to specific circumstances

Evidence-based protocols provide a foundation of proven practices, but effective Agile Product Management professionals must also adapt their approach based on specific circumstances and individual case needs within Kanban & Lean Principles.

Question 54: How does the Product Owner balance technical debt items with new feature requests in the backlog?

• Technical debt is always deprioritized in favor of features
• Only the development team decides when to address technical debt
• Technical debt should be tracked separately and never mixed with feature work
• Technical debt items should be prioritized based on their impact on future velocity and product quality (Correct answer)

Correct answer: Technical debt items should be prioritized based on their impact on future velocity and product quality

Technical debt must be weighed against feature value because unresolved debt slows future development and reduces product quality over time.

Question 55: A team regularly discovers new requirements while implementing a story during the sprint. What refinement practice would MOST reduce this issue?

• Increasing the sprint length
• More thorough acceptance criteria definition during backlog refinement (Correct answer)
• Using a waterfall-style requirements document
• Assigning the story to the most experienced developer

Correct answer: More thorough acceptance criteria definition during backlog refinement

Thorough acceptance criteria defined before the sprint starts surface ambiguities early, reducing mid-sprint discovery of undiscussed requirements.

Question 56: During sprint planning, the team discovers a user story is too large to complete in one sprint. What should happen?

• Carry the story across multiple sprints
• Skip the story and move to the next backlog item
• Decompose the story into smaller stories that fit within the sprint (Correct answer)
• Extend the sprint to accommodate the large story

Correct answer: Decompose the story into smaller stories that fit within the sprint

Stories that don't fit within a sprint must be decomposed into smaller, independently deliverable pieces before committing.

Question 57: What does 'release scope management' mean in an Agile context?

• Preventing any backlog changes during a sprint
• Continuously evaluating and adjusting which features are included in a release based on value and capacity (Correct answer)
• Freezing all requirements at project start
• Assigning scope only to senior developers

Correct answer: Continuously evaluating and adjusting which features are included in a release based on value and capacity

Agile release scope management is an ongoing negotiation of value vs. capacity, allowing teams to drop or defer low-value items to protect the release date.

Question 58: A team's velocity has been inconsistent over the last 6 sprints due to a major product launch. How should they plan the next sprint?

• Use the highest velocity sprint as the planning baseline
• Abandon velocity-based planning and use team intuition
• Exclude the launch-disrupted sprints and average the remaining data (Correct answer)
• Use the lowest velocity sprint to be safe

Correct answer: Exclude the launch-disrupted sprints and average the remaining data

Outlier sprints caused by exceptional events should be excluded so velocity calculations reflect normal working conditions.

Question 59: When using the Cynefin framework to inform Agile product decisions, in which domain is iterative experimentation (probe-sense-respond) the recommended approach?

• Complicated
• Obvious (Clear)
• Chaotic
• Complex (Correct answer)

Correct answer: Complex

In the Complex domain, cause and effect can only be understood in retrospect, so the Cynefin framework recommends running safe-to-fail experiments (probe-sense-respond), which aligns closely with Agile iteration.

Question 60: Which Agile metric is most useful for predicting when a fixed-scope release will be completed?

• Number of user stories in the backlog
• Velocity combined with remaining story points (Correct answer)
• Daily standup attendance rate
• Team happiness index

Correct answer: Velocity combined with remaining story points

Dividing remaining story points by average velocity gives a predicted number of sprints needed to complete a fixed-scope release.