PMI Agile Certified Practitioner (PMI-ACP) — Questions and Answers
Question 1: What is a Cumulative Flow Diagram (CFD) primarily used to visualize?
- Customer satisfaction scores
- Individual developer performance rankings
- The project budget burn rate
- Work distribution across stages and flow stability over time (Correct answer)
Correct answer: Work distribution across stages and flow stability over time
A CFD shows how many items are in each stage over time, revealing bottlenecks and growing WIP.
Question 2: Which artifact best helps a team spot trends in WIP, throughput, and lead time over time?
- A Gantt chart
- A cumulative flow diagram (Correct answer)
- A burndown of story points only
- An org chart
Correct answer: A cumulative flow diagram
The cumulative flow diagram visualizes WIP, throughput, and approximate lead time trends together.
Question 3: During the Daily Scrum, the Developers may do which of the following?
- Extend the Sprint length
- Reassign the Product Owner role
- Adjust the Sprint Backlog as needed (Correct answer)
- Change the Sprint Goal
Correct answer: Adjust the Sprint Backlog as needed
Developers can adjust the Sprint Backlog at any time, including during the Daily Scrum.
Question 4: How does Agile handle conflicting priorities between different stakeholders?
- The most senior stakeholder's preference always takes priority
- Conflicts are documented and resolved only during quarterly planning
- The development team votes on which features to implement first
- The Product Owner facilitates discussion and makes final prioritization decisions (Correct answer)
Correct answer: The Product Owner facilitates discussion and makes final prioritization decisions
The Product Owner is accountable for resolving stakeholder conflicts through transparent prioritization that maximizes business value.
Question 5: What does 'transparency' mean in the context of Agile stakeholder communication?
- Sharing all internal team discussions and conflicts with stakeholders
- Ensuring that work, progress, and impediments are visible and honest with all relevant parties (Correct answer)
- Publishing daily status reports to all project participants
- Providing stakeholders with full access to the team's internal tools and code repositories
Correct answer: Ensuring that work, progress, and impediments are visible and honest with all relevant parties
Transparency in Agile means making work and progress honestly visible so stakeholders can make informed decisions and provide meaningful feedback.
Question 6: Why might a new team's velocity be unreliable for the first few sprints?
- Management hasn't approved the metric yet
- The team is still calibrating its shared sense of point sizing (Correct answer)
- Velocity only applies to mature products
- Story points change value over time
Correct answer: The team is still calibrating its shared sense of point sizing
New teams need several sprints to establish a consistent, shared baseline for point sizing.
Question 7: A team repeatedly exceeds its WIP limit 'just this once.' What is the likely consequence?
- Automatic bottleneck removal
- Shorter cycle time
- Faster overall delivery
- Increased multitasking and longer lead times (Correct answer)
Correct answer: Increased multitasking and longer lead times
Routinely breaching WIP limits reintroduces multitasking and overload, lengthening lead and cycle times.
Question 8: In Agile, what is a product demo primarily designed to accomplish?
- Showcase team performance to executives
- Demonstrate compliance with project requirements documents
- Validate that completed features meet stakeholder needs and gather feedback (Correct answer)
- Train end users on new system features
Correct answer: Validate that completed features meet stakeholder needs and gather feedback
Product demos give stakeholders hands-on visibility into working software so they can validate direction and provide actionable feedback.
Question 9: In Planning Poker, why are Fibonacci-like numbers used instead of a linear 1-10 scale?
- They are easier for managers to total
- They reflect growing uncertainty as size increases (Correct answer)
- They force every story to be the same size
- They map directly to calendar days
Correct answer: They reflect growing uncertainty as size increases
The widening gaps acknowledge that larger items carry more uncertainty, discouraging false precision.
Question 10: What is the best way to explain an Agile leader's key role?
- Manage work allocation to team members
- Manage stakeholders
- Manage WBS, schedule and cost of project
- Manage teams without managing their tasks (Correct answer)
Correct answer: Manage teams without managing their tasks
An Agile leader's primary role is to serve the team, fostering an environment where they can be self-organizing and effective. This involves removing impediments, coaching, and providing support, rather than dictating individual tasks or micro-managing their daily activities. By focusing on the team's overall well-being and capability, the leader empowers them to manage their own work and achieve goals.
Question 11: A team finds most of an item's lead time is spent waiting, not working. To improve flow efficiency they should first:
- Reduce wait states and handoff delays (Correct answer)
- Add more columns for status
- Increase the number of items started
- Hire more managers
Correct answer: Reduce wait states and handoff delays
Cutting wait time and handoff delays directly raises flow efficiency more than working faster.
Question 12: Which of the following statements about the differences between burn up charts that also monitor overall scope and burn down charts is false?
- The rate of advancement is separated from the scope fluctuations using burn up charts.
- Changes in the rate of effort are indicated by burn down charts, which show whether the changes are attributable to changes in progress rates or scope. (Correct answer)
- Burn up and burn down charts have a vertical trend in the opposite direction.
- WIP can be added to burn up charts to turn them to cumulative flow diagrams.
Correct answer: Changes in the rate of effort are indicated by burn down charts, which show whether the changes are attributable to changes in progress rates or scope.
Burn-down charts primarily show the remaining work over time, indicating the rate of progress towards completion. While they reflect changes in the rate of effort, they do not inherently distinguish whether these changes are due to progress rate fluctuations or scope changes. Burn-up charts, by showing both completed work and total scope, are better at separating these two factors, as they have distinct lines for total scope and completed work.
Question 13: An Agile team is estimating a large, unrefined backlog for the first time. The goal is to quickly group user stories by size to get a high-level forecast for release planning. Which estimation technique is most suitable for this scenario?
- Absolute Estimation in hours
- Affinity Estimating (Correct answer)
- Planning Poker
- Dot Voting
Correct answer: Affinity Estimating
Affinity Estimating is ideal for quickly sizing a large number of items. The team silently and collaboratively sorts backlog items into groups of similar relative size (e.g., Small, Medium, Large), making it much faster than estimating each item one by one, as is done in Planning Poker.
Question 14: During a project retrospective, team members openly discuss a mistake that led to a significant setback in the last iteration. An Agile mindset supports which of the following responses from leadership?
- Canceling retrospectives as they seem to highlight only negative events.
- Viewing the mistake as a valuable learning opportunity for the entire team to improve its process. (Correct answer)
- Implementing a new, more rigid process to prevent any future mistakes.
- Identifying the individual responsible for the mistake to ensure accountability.
Correct answer: Viewing the mistake as a valuable learning opportunity for the entire team to improve its process.
A core tenet of the Agile mindset is creating a culture of trust and continuous improvement. Mistakes and failures are seen as opportunities for learning and growth, not for placing blame. The retrospective's purpose is to reflect on how to become more effective, and a healthy response is to analyze the process that allowed the mistake and adapt, rather than punishing individuals.
Question 15: In a Kanban system, which of the following is the primary purpose of making process policies explicit?
- To eliminate the need for team meetings and discussions.
- To assign blame when work items are delayed.
- To enforce a strict, unchangeable set of rules for the workflow.
- To create a common understanding of how work flows through the system. (Correct answer)
Correct answer: To create a common understanding of how work flows through the system.
Making process policies explicit, such as defining what 'Done' means for each stage or when an item can be pulled into the next column, creates a shared and transparent understanding for everyone on the team. This clarity helps to reduce ambiguity and ensures consistency in how work is performed, which is essential for managing flow and enabling collaborative improvement.
Question 16: A team consistently delivers but never reflects on its process. Which Agile practice is missing?
- Longer sprints
- Retrospectives for continuous improvement (Correct answer)
- Additional documentation
- More detailed requirements
Correct answer: Retrospectives for continuous improvement
Retrospectives provide the regular reflection needed for continuous improvement.
Question 17: How should an Agile team respond when a major stakeholder expresses dissatisfaction with delivered features?
- Treat the feedback as valuable input and incorporate it into future sprint backlogs (Correct answer)
- Defend the team's work by referencing the original requirements document
- Escalate to the project sponsor to manage the stakeholder's expectations
- Request a change freeze until the stakeholder's concerns are resolved
Correct answer: Treat the feedback as valuable input and incorporate it into future sprint backlogs
Stakeholder dissatisfaction is valuable feedback that Agile teams use to adapt and improve the product in subsequent iterations.
Question 18: A team treats every incoming request as equally urgent and never says no. The likely Kanban-related problem is:
- Reduced lead time
- Demand outpacing capacity, causing overload (Correct answer)
- Higher flow efficiency
- Perfect prioritization
Correct answer: Demand outpacing capacity, causing overload
Accepting unlimited demand without managing capacity overloads the system and degrades flow.
Question 19: When splitting a story, which split typically delivers the most value?
- A vertical slice delivering working end-to-end functionality (Correct answer)
- Splitting by estimated hours
- Splitting by team member
- A horizontal slice by technical layer only
Correct answer: A vertical slice delivering working end-to-end functionality
Vertical slices deliver usable, demonstrable functionality each iteration.
Question 20: A manager wants to motivate an Agile team. Which approach aligns with Agile principles?
- Tie pay strictly to lines of code written
- Give them the environment and support they need, then trust them (Correct answer)
- Assign tasks in detail and monitor every step
- Reduce face-to-face interaction to save time
Correct answer: Give them the environment and support they need, then trust them
Agile builds projects around motivated individuals and trusts them to deliver.
Question 21: Which statement best captures the Agile attitude toward technical excellence?
- Continuous attention to good design enhances agility (Correct answer)
- Quality can be sacrificed to meet deadlines
- Refactoring should be avoided to save time
- Design matters only at project start
Correct answer: Continuous attention to good design enhances agility
Continuous attention to technical excellence and good design enhances agility.
Question 22: Which of the following best describes 'inspect and adapt' as a continuous improvement concept?
- Plan everything upfront and never change
- Regularly examine work and process, then adjust (Correct answer)
- Inspect only the final product at release
- Adapt only when a crisis occurs
Correct answer: Regularly examine work and process, then adjust
Inspect and adapt means frequently examining both product and process and making adjustments.
Question 23: In Agile, how often should stakeholders typically review working software?
- At the end of each sprint or iteration (Correct answer)
- When significant milestones are reached
- Only at project completion
- Monthly, through formal status reports
Correct answer: At the end of each sprint or iteration
Sprint reviews at the end of each iteration give stakeholders regular visibility into working software and opportunities to provide feedback and redirect.
Question 24: How does Agile encourage knowledge sharing within a team?
- Through pair programming, cross-training, mob programming, and collaborative code reviews (Correct answer)
- By rotating team leads each sprint
- By holding quarterly training sessions off-site
- By requiring all team members to write detailed technical documentation daily
Correct answer: Through pair programming, cross-training, mob programming, and collaborative code reviews
Agile promotes pair programming, mob sessions, and collaborative reviews to continuously share knowledge, reduce silos, and build team resilience.
Question 25: A stakeholder requests a feature that conflicts with the product vision. Who is primarily responsible for addressing this?
- The project sponsor, by overriding the stakeholder's request
- The Scrum Master, by facilitating a compromise meeting
- The Product Owner, by managing the backlog and stakeholder expectations (Correct answer)
- The development team, by evaluating technical feasibility
Correct answer: The Product Owner, by managing the backlog and stakeholder expectations
The Product Owner owns the product backlog and is responsible for balancing stakeholder needs against the product vision.
Question 26: A Product Owner is managing a list of all desired features, functions, requirements, enhancements, and fixes for a product. This emergent, ordered list is the single source of work undertaken by the Scrum Team. What is this artifact called?
- The Sprint Backlog
- The Release Plan
- The Product Backlog (Correct answer)
- The Project Charter
Correct answer: The Product Backlog
The Product Backlog is the single source of work for the Scrum Team. It is an emergent, ordered list of everything that is known to be needed in the product. The Product Owner is responsible for its content, availability, and ordering.
Question 27: What is a Definition of Done and why is it important for stakeholder communication?
- A shared understanding between team and stakeholders of what constitutes a complete, releasable increment (Correct answer)
- A checklist used by the Scrum Master to approve sprint backlog items
- A contract requirement specifying the final deliverable
- A list of tasks the team must complete before a sprint starts
Correct answer: A shared understanding between team and stakeholders of what constitutes a complete, releasable increment
The Definition of Done creates a shared, transparent standard that sets clear expectations for stakeholders about what 'complete' means.
Question 28: A team writes extensive documentation before any code. Which Manifesto value does this conflict with?
- Working software over comprehensive documentation (Correct answer)
- Responding to change over following a plan
- Customer collaboration over contract negotiation
- Individuals over processes
Correct answer: Working software over comprehensive documentation
Prioritizing documentation before working software conflicts with valuing working software over comprehensive documentation.
Question 29: Which statement best embodies the Agile principle of building projects around motivated individuals?
- Providing the team with the environment and support they need, and trusting them to get the job done. (Correct answer)
- Assigning individual performance bonuses based on lines of code written.
- Micromanaging team members' tasks to ensure they are always productive.
- Mandating specific tools and processes that every team member must follow without deviation.
Correct answer: Providing the team with the environment and support they need, and trusting them to get the job done.
This principle directly states, 'Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.' This reflects a servant-leadership approach where management's role is to empower the team and remove impediments, fostering an environment of autonomy and ownership.
Question 30: In scaled Agile, what does a Scrum of Scrums primarily coordinate?
- Stakeholder budgets
- A single team's daily work
- Customer support tickets
- Dependencies and integration across multiple Scrum teams (Correct answer)
Correct answer: Dependencies and integration across multiple Scrum teams
A Scrum of Scrums coordinates work and dependencies across multiple teams working on the same product.
Question 31: Elapsed Time is defined by which of the following?
- Is the amount of time the team spent on the iteration
- Is the amount of time that something takes when stripped of all peripheral activities
- Is the same as Ideal Time
- Is the amount of time that passes on a clock or perhaps a calendar (Correct answer)
Correct answer: Is the amount of time that passes on a clock or perhaps a calendar
Elapsed time refers to the actual duration that passes from the start to the end of an activity, as measured by a clock or calendar. Unlike ideal time, which excludes interruptions, elapsed time accounts for all real-world factors like breaks, meetings, and other non-work activities. It represents the total wall-clock time taken for a task or project to be completed.
Question 32: Which of the following is NOT one of Kanban's core practices?
- Visualize the workflow
- Assign story points to every task (Correct answer)
- Limit work in progress
- Manage flow
Correct answer: Assign story points to every task
Assigning story points is a Scrum-style estimation habit, not a core Kanban practice.
Question 33: What does the Japanese term 'Kaizen' represent in Agile continuous improvement?
- Fixed annual process reviews
- Large, infrequent transformations
- Small, incremental ongoing improvements (Correct answer)
- Eliminating all team meetings
Correct answer: Small, incremental ongoing improvements
Kaizen means continuous improvement through small, incremental changes over time.
Question 34: What does the Agile concept of 'empiricism' rely on?
- Following the original plan regardless of results
- Decisions based on detailed long-term forecasts
- Avoiding any measurement
- Decisions based on observation and experimentation (Correct answer)
Correct answer: Decisions based on observation and experimentation
Empiricism makes decisions based on what is observed and experimentally validated.
Question 35: A team is using a burn-up chart to track progress towards a release. Midway through the project, the product owner adds a significant number of new user stories to the scope. How would this event be reflected on the burn-up chart?
- A new chart must be started as the original scope is now invalid.
- Both the completed work line and the total scope line would flatten.
- The line representing completed work would drop down to a lower value.
- The line representing total scope would show a distinct upward step. (Correct answer)
Correct answer: The line representing total scope would show a distinct upward step.
A burn-up chart tracks two key lines: the total scope of work and the amount of work completed. When new scope is added, the line representing the total work will jump up, reflecting the new total. The line for completed work continues to climb from its previous point as the team completes tasks.
Question 36: How should teams handle scope changes during a release in Agile?
- Accept all scope changes to satisfy the customer
- Reject all scope changes once the release begins
- Escalate all changes to the PMO for approval
- Use trade-off analysis to swap in new items by removing equivalent scope elsewhere (Correct answer)
Correct answer: Use trade-off analysis to swap in new items by removing equivalent scope elsewhere
Agile teams handle mid-release scope changes by trading new items against existing ones of equal size to protect capacity and delivery commitments.
Question 37: What is 'feature freeze' in Agile release planning?
- Freezing the product backlog permanently
- A sprint where no new code is written
- Stopping all work until the customer approves the current build
- The point at which no new features are added so the team can focus on stability and quality (Correct answer)
Correct answer: The point at which no new features are added so the team can focus on stability and quality
Feature freeze is the point in a release cycle when no new features are added so the team can focus on stabilizing, testing, and hardening the product.
Question 38: What does 'co-location' mean for Agile teams, and why is it valued?
- Having the product owner sit with developers during sprint planning
- Storing all project files on a shared server
- All team members must be in the same time zone
- Team members physically working in the same location, enabling richer communication and faster collaboration (Correct answer)
Correct answer: Team members physically working in the same location, enabling richer communication and faster collaboration
Co-location means the team works in the same physical space, which enables face-to-face communication, osmotic information sharing, and faster decision-making.
Question 39: Who is primarily responsible for maximizing the value of the product backlog?
- Scrum Master
- Development Team
- Project Sponsor
- Product Owner (Correct answer)
Correct answer: Product Owner
The Product Owner owns and prioritizes the backlog to maximize the product's value.
Question 40: Who is responsible for managing and ordering the Product Backlog?
- Developers
- Scrum Master
- Product Owner (Correct answer)
- Stakeholders
Correct answer: Product Owner
The Product Owner is accountable for effective Product Backlog management and ordering.
Question 41: What is the primary purpose of a product roadmap in Agile?
- To replace the product backlog
- To assign tasks to individual developers
- To communicate the strategic direction and planned evolution of a product (Correct answer)
- To document every sprint's completed work
Correct answer: To communicate the strategic direction and planned evolution of a product
A product roadmap provides a high-level visual summary that communicates the strategic direction and planned evolution of a product over time.
Question 42: What is the purpose of a daily standup (daily scrum) in fostering team collaboration?
- To report progress to management
- To synchronize the team's work, identify blockers, and adapt the day's plan (Correct answer)
- To assign new tasks to team members
- To review and update the product backlog
Correct answer: To synchronize the team's work, identify blockers, and adapt the day's plan
The daily standup synchronizes the team around progress, surfaces impediments early, and enables quick coordination to adapt the plan for the day.
Question 43: According to the Agile Manifesto, what is the most efficient and effective method of conveying information to and within a development team?
- Comprehensive documentation
- Face-to-face conversation (Correct answer)
- Status reports
- Email communication
Correct answer: Face-to-face conversation
The sixth principle of the Agile Manifesto is: 'The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.' This promotes direct, real-time communication to reduce misunderstandings and speed up decision-making.
Question 44: What is a 'team working agreement' in Agile?
- A legal contract between the team and the client
- A list of tasks assigned to each team member for the sprint
- A set of norms and expectations the team creates collaboratively to guide how they work together (Correct answer)
- A formal document approved by the project manager
Correct answer: A set of norms and expectations the team creates collaboratively to guide how they work together
A team working agreement is a collaboratively created set of norms — such as communication preferences and meeting rules — that guides how the team operates.
Question 45: A team adopts a new process change but reverts after one Sprint because results looked worse. What is the likely mistake?
- The change was too small
- They abandoned it before giving it enough time to take effect (Correct answer)
- They documented it too thoroughly
- They involved the whole team
Correct answer: They abandoned it before giving it enough time to take effect
Many process changes need several iterations before benefits appear, so premature abandonment undermines improvement.
Question 46: Which value does the Agile Manifesto place above 'comprehensive documentation'?
- Working software (Correct answer)
- Long-term plans
- Detailed contracts
- Fixed scope
Correct answer: Working software
The Manifesto values working software over comprehensive documentation.
Question 47: According to Little's Law, how can a team reduce average cycle time?
- Add more columns to the board
- Increase the work in progress
- Lengthen the working day
- Reduce the amount of work in progress (Correct answer)
Correct answer: Reduce the amount of work in progress
Little's Law shows cycle time equals WIP divided by throughput, so lowering WIP shortens cycle time at a stable throughput.
Question 48: What is 'swarming' in Agile team practice?
- Assigning one person to monitor team communication channels
- A planning technique for estimating large epics
- Multiple team members simultaneously working on the same item to complete it faster (Correct answer)
- Holding all meetings on the same day to free up the rest of the week
Correct answer: Multiple team members simultaneously working on the same item to complete it faster
Swarming is when multiple team members focus on the same work item simultaneously to remove blockers and complete it quickly, reducing WIP and cycle time.
Question 49: A Kanban team wants to improve the predictability of their delivery. They decide to track the number of work items finished per week to understand their delivery rate. What is this metric called?
- Throughput (Correct answer)
- Work in Progress (WIP)
- Velocity
- Cycle Time
Correct answer: Throughput
Throughput is a key flow metric that measures the number of work items completed within a specific time period (e.g., per day or per week). It provides a direct measure of the team's delivery rate and is often used for forecasting.
Question 50: What is the primary purpose of involving stakeholders early in an Agile project?
- To delegate project ownership to the business side
- To gain continuous feedback and align expectations throughout delivery (Correct answer)
- To ensure stakeholders can approve all design decisions
- To lock in requirements before development starts
Correct answer: To gain continuous feedback and align expectations throughout delivery
Early stakeholder involvement enables continuous feedback loops that help teams deliver value aligned with actual needs.
Question 51: What distinguishes a Kanban cadence from a Scrum cadence?
- Kanban uses continuous flow while Scrum uses time-boxed sprints (Correct answer)
- Kanban forbids any meetings
- Kanban requires a Scrum Master role
- Kanban always uses two-week iterations
Correct answer: Kanban uses continuous flow while Scrum uses time-boxed sprints
Kanban delivers continuously without fixed-length iterations, whereas Scrum organizes work into time-boxed sprints.
Question 52: A team consistently finishes early and has idle capacity. What is the appropriate continuous improvement action?
- Examine whether to take on more work or improve estimates (Correct answer)
- Reduce the team to one person
- Ignore it to keep morale high
- Stop holding retrospectives
Correct answer: Examine whether to take on more work or improve estimates
Consistent idle capacity suggests reviewing estimates or capacity to optimize delivery.
Question 53: Which Agile principle directly addresses building the right environment for teams and stakeholders?
- Build projects around motivated individuals, give them the environment and support they need, and trust them to get the job done (Correct answer)
- Simplicity — the art of maximizing the amount of work not done — is essential
- Deliver working software frequently
- Welcome changing requirements, even late in development
Correct answer: Build projects around motivated individuals, give them the environment and support they need, and trust them to get the job done
This Agile Manifesto principle emphasizes that creating an environment of trust and support is fundamental to successful Agile delivery.
Question 54: How does a 'fixed-date' class of service differ from a standard one?
- It has a hard deadline that influences when it must be prioritized (Correct answer)
- It is exempt from WIP limits permanently
- It is always the lowest priority
- It can never be expedited
Correct answer: It has a hard deadline that influences when it must be prioritized
Fixed-date items carry a firm due date, so they are scheduled and prioritized to avoid missing that deadline.
Question 55: Which of the following is NOT a primary goal of implementing feedback loops (Kanban cadences)?
- To compare individual team member performance for annual reviews and compensation. (Correct answer)
- To provide opportunities for the customer to give input and steer the product.
- To coordinate dependencies and manage the flow of work between different process stages.
- To review and adapt the workflow and policies at regular intervals.
Correct answer: To compare individual team member performance for annual reviews and compensation.
Kanban feedback loops, such as the daily stand-up, service delivery review, and retrospectives, are designed to improve the system, the process, and the flow of value. Using metrics and discussions from these meetings for individual performance reviews is counterproductive, as it can discourage transparency and create a culture of fear, undermining the goal of collaborative process improvement.
Question 56: Which scenario best demonstrates 'customer collaboration over contract negotiation'?
- The team builds only what the signed contract lists
- Changes are blocked unless the contract is amended formally
- The customer is consulted only at project end
- The team and customer adjust priorities together as needs emerge (Correct answer)
Correct answer: The team and customer adjust priorities together as needs emerge
Customer collaboration means working with the customer continuously rather than hiding behind a contract.
Question 57: Which of the following is identified by the Agile Manifesto as the primary measure of progress?
- Hours logged by the development team
- Completed project documentation
- Working software (Correct answer)
- Adherence to the initial project plan
Correct answer: Working software
One of the twelve principles behind the Agile Manifesto explicitly states, 'Working software is the primary measure of progress.' This means the ultimate indicator of success is a functional product that delivers value, not intermediate deliverables like documentation or plan adherence.
Question 58: What is the primary purpose of the Sprint Review?
- Discuss team process improvements
- Assign individual tasks to Developers
- Plan the work for the next Sprint
- Inspect the Increment and adapt the Product Backlog (Correct answer)
Correct answer: Inspect the Increment and adapt the Product Backlog
The Sprint Review inspects the outcome of the Sprint and determines future adaptations.
Question 59: What is the role of trust in the Agile mindset?
- It applies only to managers
- It is irrelevant if processes are strong
- It slows the team down
- It enables self-organization and faster decisions (Correct answer)
Correct answer: It enables self-organization and faster decisions
Trust lets teams self-organize and make decisions quickly without excessive oversight.
Question 60: What is the primary purpose of a Work In Progress (WIP) limit in Kanban?
- To assign more work to idle team members
- To reduce multitasking and expose bottlenecks (Correct answer)
- To set a deadline for each task
- To increase the number of columns on the board
Correct answer: To reduce multitasking and expose bottlenecks
WIP limits cap how much work is active at once, reducing context switching and making bottlenecks visible.
Question 61: A team wants to experiment with a process change safely. Which approach best fits continuous improvement?
- Wait until the project ends
- Roll it out permanently with no review
- Apply it only if management mandates it
- Run it as a time-boxed experiment and evaluate results (Correct answer)
Correct answer: Run it as a time-boxed experiment and evaluate results
Time-boxed experiments let teams test changes and keep or discard them based on results.
Question 62: What does 'T-shaped skills' mean for Agile team members?
- Being trained in both technical and management roles
- Having deep expertise in one area and broad enough knowledge to contribute across disciplines (Correct answer)
- Switching between two roles every sprint
- Avoiding specialization to stay fully cross-functional
Correct answer: Having deep expertise in one area and broad enough knowledge to contribute across disciplines
T-shaped skills describe a team member with deep expertise in one discipline (the vertical bar) and broad capability to collaborate across other areas (the horizontal bar).
Question 63: What does the Agile Manifesto's principle on face-to-face communication emphasize?
- Daily standups held in person only
- Executive-level presentations to key stakeholders
- The most efficient and effective method of conveying information to and within a development team (Correct answer)
- Video conferencing as a replacement for email
Correct answer: The most efficient and effective method of conveying information to and within a development team
The Agile Manifesto states that face-to-face conversation is the most efficient and effective method for conveying information within a development team.
Question 64: Which metric measures the total time from when a work item is requested to when it is delivered?
- Cycle time
- Velocity
- Lead time (Correct answer)
- Story points
Correct answer: Lead time
Lead time spans the customer request to delivery, while cycle time measures only active work.
Question 65: A user story has acceptance criteria but no clear value to the user. Which INVEST trait is most violated?
- Small
- Valuable (Correct answer)
- Testable
- Independent
Correct answer: Valuable
Every user story should deliver clear value to a user or customer.
Question 66: A team's defect rate is rising each release. Which continuous improvement focus is most appropriate?
- Increase the number of features per release
- Investigate and strengthen quality practices (Correct answer)
- Reduce testing to save time
- Lengthen the release cycle only
Correct answer: Investigate and strengthen quality practices
A rising defect rate points to weak quality practices that improvement efforts should strengthen.
Question 67: What is the relationship between the product backlog and release planning in Agile?
- Release planning and the product backlog are managed by different teams
- The product backlog is only used during sprint planning, not release planning
- Release planning replaces the product backlog
- The product backlog is the source from which release content is selected and prioritized (Correct answer)
Correct answer: The product backlog is the source from which release content is selected and prioritized
Release planning draws directly from the prioritized product backlog, selecting the highest-value items to include in the upcoming release.
Question 68: What role does 'working software' play in stakeholder communication?
- It is only relevant after final user acceptance testing
- It serves as the primary measure of progress that stakeholders can directly evaluate (Correct answer)
- It helps the team track velocity more accurately
- It replaces all other forms of documentation and reporting
Correct answer: It serves as the primary measure of progress that stakeholders can directly evaluate
Working software is the most concrete and trustworthy way for stakeholders to evaluate actual progress and validate their investment.
Question 69: In Agile, what is a 'hardening sprint'?
- A sprint where the team increases velocity by working overtime
- A sprint dedicated to adding new major features
- A sprint used to stabilize, test, and fix defects before a release (Correct answer)
- A sprint focused solely on documentation
Correct answer: A sprint used to stabilize, test, and fix defects before a release
A hardening sprint (also called a stabilization sprint) is used to fix defects, improve performance, and prepare the product for a stable release.
Question 70: A product owner keeps adding implementation details to every story before the sprint. Which INVEST principle does this risk violating?
- Valuable
- Testable
- Negotiable (Correct answer)
- Small
Correct answer: Negotiable
Stories should remain negotiable, leaving room for collaborative detail during the sprint.
Question 71: Which of the following is an Agile principle about business and development collaboration?
- Collaboration happens only at milestones
- Developers should never contact business stakeholders
- Business people and developers must work together daily (Correct answer)
- Business people should set requirements then step away
Correct answer: Business people and developers must work together daily
Agile principles state business people and developers must work together daily throughout the project.
Question 72: What is 'team velocity' and how does it support collaboration?
- The average amount of work a team completes per sprint, used to plan collaboratively and set realistic expectations (Correct answer)
- The rate at which new members join the team
- The number of meetings the team holds per sprint
- The speed at which the team resolves merge conflicts
Correct answer: The average amount of work a team completes per sprint, used to plan collaboratively and set realistic expectations
Team velocity measures average story points completed per sprint, giving the whole team a shared, empirical basis for planning future work collaboratively.
Question 73: A pull system in Kanban means that new work is started when:
- A manager pushes it onto the team
- The sprint planning meeting begins
- Downstream capacity becomes available (Correct answer)
- The backlog reaches a certain size
Correct answer: Downstream capacity becomes available
In a pull system, items advance only when the next stage has free capacity, preventing overload.
Question 74: What is the main goal of the Sprint Review ceremony from a stakeholder perspective?
- To formally accept or reject completed work
- To get stakeholder sign-off before moving to the next sprint
- To present metrics on team velocity and performance
- To inspect the increment and adapt the backlog based on stakeholder feedback (Correct answer)
Correct answer: To inspect the increment and adapt the backlog based on stakeholder feedback
The Sprint Review is an opportunity to inspect the working increment and collaboratively adapt the backlog based on stakeholder input.
Question 75: Which technique helps Agile teams identify all relevant stakeholders at the start of a project?
- SWOT analysis
- Sprint retrospective
- Risk register review
- Stakeholder mapping or stakeholder analysis (Correct answer)
Correct answer: Stakeholder mapping or stakeholder analysis
Stakeholder mapping helps identify who has interest in or influence over the project, ensuring no key voice is overlooked.
Question 76: What does a burnup chart add compared to a burndown chart?
- It only tracks defects
- It replaces the product backlog
- It separately shows total scope, revealing scope changes (Correct answer)
- It hides completed work
Correct answer: It separately shows total scope, revealing scope changes
A burnup chart plots scope as its own line, making scope creep visible alongside progress.
Question 77: Unlike Scrum, which uses time-boxed Sprints, the Kanban method is characterized by what kind of delivery approach?
- A release-driven, quarterly cycle
- A continuous flow model (Correct answer)
- A project-based, big-bang delivery
- A phase-gated, sequential model
Correct answer: A continuous flow model
The Kanban method is fundamentally a continuous flow system. Work items are pulled into the workflow as capacity becomes available, rather than being planned in fixed-length iterations like Scrum Sprints. This allows for a more flexible and continuous delivery of value.
Question 78: According to the principles, the best architectures, requirements, and designs emerge from what?
- Self-organizing teams (Correct answer)
- Top-down management mandates
- External consultants
- Detailed upfront plans
Correct answer: Self-organizing teams
The best architectures, requirements, and designs emerge from self-organizing teams.
Question 79: Throughput in Kanban is best described as:
- The number of people on the team
- The total backlog count
- The number of items completed per unit of time (Correct answer)
- The longest cycle time recorded
Correct answer: The number of items completed per unit of time
Throughput measures how many work items the system completes in a given time period.
Question 80: Which of the following statements best describes the Developers on a Scrum Team?
- They report their individual progress and status to the Product Owner daily.
- They are accountable for creating the Sprint Backlog and instilling quality by adhering to a Definition of Done. (Correct answer)
- They can only consist of software engineers and programmers.
- They are a hierarchical sub-team where a 'lead developer' assigns tasks.
Correct answer: They are accountable for creating the Sprint Backlog and instilling quality by adhering to a Definition of Done.
The Developers are accountable for creating a plan for the Sprint (the Sprint Backlog) and ensuring quality by adhering to a Definition of Done. They are a self-managing, cross-functional group with no sub-teams or hierarchies.
Question 81: What is the main risk of estimating user stories in precise hours rather than relative points?
- It removes the need for sprint planning
- It increases team velocity automatically
- It implies false precision and invites unrealistic commitments (Correct answer)
- It is always more accurate
Correct answer: It implies false precision and invites unrealistic commitments
Hour estimates suggest a precision that rarely holds, encouraging over-commitment.
Question 82: Which of the following is an anti-pattern, or misuse, of the team velocity metric?
- Observing a downward trend in velocity as an indicator to investigate potential impediments.
- Comparing the velocity of Team A (30 points/sprint) to Team B (50 points/sprint) to determine which team is more productive. (Correct answer)
- Using historical velocity to create a rough forecast for a multi-sprint release plan.
- Using the average velocity over the last three sprints to help forecast the next sprint's capacity.
Correct answer: Comparing the velocity of Team A (30 points/sprint) to Team B (50 points/sprint) to determine which team is more productive.
Velocity is a team-specific metric based on its unique estimation scale and context. Because story points are relative and not standardized across teams, comparing the velocity of different teams is a meaningless and harmful practice that can lead to unhealthy competition and inaccurate conclusions. [14, 15]
Question 83: Which statement about the Scrum Team's accountability is correct?
- The whole Scrum Team is accountable for creating a valuable Increment each Sprint (Correct answer)
- The Scrum Master is accountable for delivery
- Only the Product Owner is accountable for the product
- Only the Developers are accountable for outcomes
Correct answer: The whole Scrum Team is accountable for creating a valuable Increment each Sprint
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
Question 84: What is the main benefit of conducting regular flow-focused reviews (e.g., service delivery review) in Kanban?
- To inspect flow metrics and drive continuous improvement (Correct answer)
- To replace all visualization
- To assign blame for delays
- To eliminate WIP limits
Correct answer: To inspect flow metrics and drive continuous improvement
Cadenced reviews examine flow metrics and feedback to fuel evolutionary, data-driven improvement.
Question 85: What is a 'minimum viable product' (MVP) in the context of Agile release planning?
- The smallest product that can be sold at any price
- The smallest set of features that delivers value and enables validated learning (Correct answer)
- The version with the minimum number of bugs
- A prototype used only for internal testing
Correct answer: The smallest set of features that delivers value and enables validated learning
An MVP is the smallest set of features that delivers enough value to early users while enabling the team to gather validated learning about the market.
Question 86: One of your stakeholders wants to see how the project is progressing but isn't interested in the details. Which of the following reports are you able to share with this individual?
- Vision Statement
- Burn up chart (Correct answer)
- Release plan
- Weekly demo
Correct answer: Burn up chart
A burn-up chart visually tracks the total amount of work completed against the total scope of the project over time. It provides a clear, high-level overview of progress and any changes in the project's scope. This makes it an excellent tool for communicating overall project trajectory to stakeholders who want to see progress without delving into granular task details.
Question 87: What is 'osmotic communication' in Agile teams?
- A structured daily communication meeting
- Using email to keep all team members informed
- Sharing meeting notes with the entire organization
- Information absorbed passively by team members sitting near each other (Correct answer)
Correct answer: Information absorbed passively by team members sitting near each other
Osmotic communication refers to the passive absorption of relevant information by co-located team members who overhear conversations happening around them.
Question 88: A self-organizing team is best described by which characteristic?
- Decisions require executive approval
- A manager assigns every task
- The team decides how to accomplish its work (Correct answer)
- Roles are fixed and never change
Correct answer: The team decides how to accomplish its work
Self-organizing teams determine the best way to accomplish their work themselves.
Question 89: A backlog refinement (grooming) session is used to:
- Conduct the retrospective
- Add detail, estimates, and order to backlog items (Correct answer)
- Hold the daily standup
- Demo the product
Correct answer: Add detail, estimates, and order to backlog items
Backlog refinement adds detail, estimates, and ordering to keep the backlog ready for upcoming sprints.
Question 90: Which behavior reflects a 'growth mindset' on an Agile team?
- Resisting feedback from peers
- Avoiding any task that might fail
- Blaming individuals for defects
- Treating mistakes as learning opportunities (Correct answer)
Correct answer: Treating mistakes as learning opportunities
A growth mindset treats failures and feedback as chances to learn and improve.
Question 91: What is 'collective code ownership' in Agile engineering practices?
- The entire company owns the IP rights to the code
- Any team member can modify any part of the codebase, shared responsibility for quality (Correct answer)
- Each developer owns and maintains a separate module independently
- Only senior developers are allowed to review code
Correct answer: Any team member can modify any part of the codebase, shared responsibility for quality
Collective code ownership means any team member can change any part of the codebase, distributing responsibility and preventing knowledge silos.
Question 92: In Agile, what is a 'release train'?
- A CI/CD pipeline configuration
- A type of retrospective format
- A metaphor for delivering features one by one
- A scheduled release cadence where teams synchronize delivery on a fixed schedule (Correct answer)
Correct answer: A scheduled release cadence where teams synchronize delivery on a fixed schedule
A release train is a scheduled, fixed-cadence release cycle used in scaled Agile frameworks like SAFe to synchronize multiple teams.
Question 93: How should an Agile team handle a key stakeholder who is frequently unavailable for feedback sessions?
- Proceed with assumptions and document them for later review
- Escalate to project management to enforce participation
- Delay the sprint until the stakeholder becomes available
- Identify a proxy stakeholder who can represent their interests (Correct answer)
Correct answer: Identify a proxy stakeholder who can represent their interests
Identifying a proxy stakeholder ensures the team maintains the continuous feedback needed to deliver value without blocking progress.
Question 94: Which value emphasizes adapting when requirements shift late in development?
- Responding to change over following a plan (Correct answer)
- Following a plan over responding to change
- Documentation over software
- Processes over individuals
Correct answer: Responding to change over following a plan
Agile values responding to change over following a plan.
Question 95: Agile processes promote sustainable development. The sponsors, developers, and users should be able to do what?
- Work overtime indefinitely
- Avoid all meetings
- Finish in one sprint
- Maintain a constant pace indefinitely (Correct answer)
Correct answer: Maintain a constant pace indefinitely
Agile promotes a constant, sustainable pace that can be maintained indefinitely.
Question 96: A stakeholder insists on attending daily standups but frequently derails the meeting with questions. What is the recommended Agile approach?
- Ask the stakeholder to submit all questions in writing only
- Convert the daily standup to a longer weekly status meeting
- Invite the stakeholder to observe silently and schedule separate time for their questions after the standup (Correct answer)
- Exclude all stakeholders from daily standups entirely
Correct answer: Invite the stakeholder to observe silently and schedule separate time for their questions after the standup
Stakeholders may observe standups but questions and detailed discussions should happen after the standup to preserve its timebox and team focus.
Question 97: Which of the following graphs depicts the total number of story points accomplished by each iteration's end?
- Cumulative story point burndown chart (Correct answer)
- Burn up chart
- Iteration burndown chart
- Daily Burndown chart
Correct answer: Cumulative story point burndown chart
A cumulative story point burndown chart, often functioning similarly to a burn-up chart, tracks the total amount of work completed (e.g., in story points) over time. It shows a rising line as story points are 'burned down' or completed across iterations, thereby depicting the accumulated progress of the team. This chart provides a clear visual of the total accomplishment by the end of each iteration.
Question 98: How does Agile differ from waterfall in release planning?
- Agile does not plan releases at all
- Agile requires sign-off from all stakeholders before any release
- Agile supports frequent, incremental releases rather than one big release at the end (Correct answer)
- Agile releases are always annual
Correct answer: Agile supports frequent, incremental releases rather than one big release at the end
Agile encourages frequent, incremental releases that deliver value continuously, rather than a single large release after all development is complete.
Question 99: Which scenario best illustrates 'responding to change over following a plan'?
- Refusing all scope changes after sprint planning
- Reprioritizing the backlog when a competitor releases a new feature (Correct answer)
- Locking requirements at the contract stage
- Rejecting a customer's new market insight to protect the schedule
Correct answer: Reprioritizing the backlog when a competitor releases a new feature
Reprioritizing the backlog in response to market change reflects valuing responsiveness over rigid plans.
Question 100: What is 'flow efficiency' in Kanban?
- The percentage of the team present each day
- The number of items completed per developer
- The ratio of active work time to total lead time (Correct answer)
- The total count of columns in use
Correct answer: The ratio of active work time to total lead time
Flow efficiency compares value-adding time to total elapsed time, exposing how much time items spend waiting.
Question 101: Why is 'maximizing the amount of work not done' considered essential in Agile?
- It reduces the need for any planning
- It lets the team avoid responsibility
- Simplicity focuses effort on the highest-value work (Correct answer)
- It eliminates testing
Correct answer: Simplicity focuses effort on the highest-value work
Simplicity—the art of maximizing work not done—focuses the team on what truly adds value.
Question 102: Which of the following best describes the primary purpose of using story points for estimation?
- To track the business value delivered to the customer at the end of each sprint.
- To measure the individual performance of each developer on the team.
- To create a relative measure of the effort, complexity, and uncertainty of a user story. (Correct answer)
- To provide a precise measure of the development time in hours for a user story.
Correct answer: To create a relative measure of the effort, complexity, and uncertainty of a user story.
Story points are an abstract, relative unit of measure used in Agile. They are not tied to specific hours but instead encapsulate the overall effort required for a task, including complexity, risks, and the volume of work. This relative sizing helps teams make forecasts and plan sprints more effectively without the false precision of time-based estimates.
Question 103: How can throughput (items completed per sprint) be used for forecasting?
- Add all sprint durations together
- Multiply story points by team size
- Divide remaining item count by average throughput (Correct answer)
- Count only the largest stories
Correct answer: Divide remaining item count by average throughput
Forecasting by throughput estimates completion time from how many items finish each sprint on average.
Question 104: Which of the following statements best describes the Kanban principle of 'Start with what you do now'?
- It suggests that the current process is perfect and should not be changed.
- It requires a complete reorganization of teams and roles before implementation.
- It mandates the immediate adoption of specific roles like Product Owner and Scrum Master.
- It encourages understanding the current process and respecting existing roles as the initial step for evolutionary change. (Correct answer)
Correct answer: It encourages understanding the current process and respecting existing roles as the initial step for evolutionary change.
This foundational principle emphasizes an evolutionary, non-disruptive approach. Instead of a radical, revolutionary shift, Kanban implementation begins by first understanding and visualizing the current workflow and respecting the existing structure and roles. Improvements are then made incrementally over time.
Question 105: Within the Scrum Team, who holds a separate 'manager' title that assigns work to individuals?
- The Product Owner
- No one; there are no sub-teams or hierarchies (Correct answer)
- The Scrum Master
- A team lead Developer
Correct answer: No one; there are no sub-teams or hierarchies
The Scrum Team has no sub-teams or hierarchies and is cross-functional and self-managing.
Question 106: An Agile team consistently identifies the same impediment during their Sprint Retrospectives but struggles to resolve it. Which of the following techniques would be most effective for digging deeper to understand the true underlying cause of this recurring issue?
- The 5 Whys (Correct answer)
- Timeboxing the discussion
- Creating a burn-down chart
- Planning Poker
Correct answer: The 5 Whys
The 5 Whys is a root cause analysis technique used to explore the cause-and-effect relationships underlying a particular problem. By repeatedly asking 'Why?', the team can move past surface-level symptoms to uncover the fundamental reason for the recurring impediment, which is crucial for finding a lasting solution.
Question 107: A key stakeholder keeps changing requirements after sprint planning. What is the best Agile response?
- Freeze all requirements at the start of each sprint and reject changes
- Accommodate all changes immediately to maintain stakeholder satisfaction
- Channel change requests into the product backlog for prioritization in future sprints (Correct answer)
- Escalate the behavior to the project steering committee
Correct answer: Channel change requests into the product backlog for prioritization in future sprints
Agile embraces change but manages it through the backlog, allowing the team to complete committed work while scheduling changes appropriately.
Question 108: A backlog item reads 'Make the app better.' Why is this a poor user story?
- It is too small to estimate
- It is vague, not testable, and lacks clear value or criteria (Correct answer)
- It names a specific role
- It has too many acceptance criteria
Correct answer: It is vague, not testable, and lacks clear value or criteria
The item lacks a defined user, goal, benefit, and any way to verify completion.
Question 109: What is the recommended first step when implementing Kanban according to its principles?
- Adopt fixed two-week sprints
- Replace all existing roles with new ones
- Visualize the current workflow as it actually exists (Correct answer)
- Set aggressive deadlines for every task
Correct answer: Visualize the current workflow as it actually exists
Kanban begins by visualizing the existing process so the team can see and then improve real flow.
Question 110: What is the purpose of an Agile information radiator in relation to stakeholders?
- To provide real-time, always-visible project status without needing to request reports (Correct answer)
- To replace sprint review meetings with self-service dashboards
- To limit information access to approved stakeholders only
- To automate stakeholder notification emails
Correct answer: To provide real-time, always-visible project status without needing to request reports
Information radiators give stakeholders on-demand visibility into project progress, fostering transparency without requiring formal reporting cycles.
Question 111: What happens to a Product Backlog item that does not meet the Definition of Done at Sprint end?
- It automatically rolls into the next Sprint Backlog
- It is released anyway
- It is deleted
- It returns to the Product Backlog (Correct answer)
Correct answer: It returns to the Product Backlog
Work not meeting the Definition of Done cannot be released and returns to the Product Backlog.
Question 112: A Scrum Master wants to measure whether retrospective actions actually improve the team. What is the best approach?
- Track relevant metrics before and after changes (Correct answer)
- Hold longer retrospectives
- Ask stakeholders to rate the team
- Count the number of actions generated
Correct answer: Track relevant metrics before and after changes
Comparing relevant metrics before and after a change shows whether the improvement had real impact.
Question 113: What does a story being 'Estimable' (the E in INVEST) require?
- It is broken into exactly five tasks
- It has a fixed deadline
- It is assigned to one developer
- The team understands it well enough to size it (Correct answer)
Correct answer: The team understands it well enough to size it
Estimable means there is enough clarity for the team to assign a reasonable size.
Question 114: A manager who oversees several Scrum teams wants to use velocity as the primary metric to compare their performance. Which of the following is the most significant reason this is a flawed approach?
- Comparing velocities is misleading because each team's estimation scale is unique and relative to that team. (Correct answer)
- Velocity can only be measured accurately using story points, which are subjective.
- Velocity does not account for the quality of the work delivered by each team.
- Teams may artificially inflate their velocity if they know they are being compared.
Correct answer: Comparing velocities is misleading because each team's estimation scale is unique and relative to that team.
Velocity is a measure of a team's capacity based on its own relative estimation scale (e.g., story points). Because each team develops its own understanding of what a 'story point' represents, their scales are not comparable. Comparing the velocity of two teams is like comparing apples to oranges and provides no meaningful insight into performance.
Question 115: How does Agile handle team conflict?
- The scrum master makes all final conflict decisions
- The team is encouraged to resolve conflicts at the lowest level using open communication (Correct answer)
- Conflicts are escalated directly to management to resolve
- Conflict is avoided by assigning tasks individually to prevent overlap
Correct answer: The team is encouraged to resolve conflicts at the lowest level using open communication
Agile encourages teams to surface and resolve conflicts directly and transparently at the team level, supported by the scrum master as a facilitator.
Question 116: Which technique is commonly used in Agile to forecast when features will be completed?
- Velocity-based forecasting (Correct answer)
- Critical path method
- Gantt chart tracking
- Earned value management
Correct answer: Velocity-based forecasting
Velocity-based forecasting uses the team's average story points per sprint to predict when backlog items will be completed.
Question 117: Who is accountable for instilling quality by adhering to a Definition of Done?
- The QA department
- The Product Owner
- The Scrum Master
- The Developers (Correct answer)
Correct answer: The Developers
The Developers are accountable for instilling quality by conforming to the Definition of Done.
Question 118: What does 'Definition of Done' (DoD) mean in the context of release planning?
- A shared agreement on criteria that must be met before an increment is considered releasable (Correct answer)
- A list of features the product owner wants
- A document signed by the project sponsor
- The acceptance criteria for a single user story
Correct answer: A shared agreement on criteria that must be met before an increment is considered releasable
The Definition of Done is a shared, transparent checklist of criteria every increment must meet before it can be considered releasable.
Question 119: Two developers reveal a 3 and a 13 for the same story. What should happen next?
- Skip the story and move on
- The higher estimate automatically wins
- They discuss the reasoning behind the extremes (Correct answer)
- Average the two to get 8
Correct answer: They discuss the reasoning behind the extremes
Wide divergence signals differing assumptions that discussion can surface and resolve.
Question 120: A team has adopted the Kanban method and is using a board to visualize their workflow. They notice that work items are piling up in the 'Testing' column, and developers are frequently idle. Which core Kanban practice should the team implement to address this issue directly?
- Implement feedback loops
- Limit Work in Progress (WIP) (Correct answer)
- Make process policies explicit
- Encourage acts of leadership at all levels
Correct answer: Limit Work in Progress (WIP)
Limiting Work in Progress (WIP) is a fundamental practice in Kanban designed to prevent bottlenecks and improve flow. By setting a limit on the number of items allowed in the 'Testing' column, the team would be forced to address the testing bottleneck before pulling new work into the system, thereby creating a smoother, more predictable workflow.
PMI Agile Certified Practitioner (PMI-ACP)
The PMI-ACP exam validates knowledge of agile principles and practices across frameworks such as Scrum, Kanban, Lean, and XP. It covers mindset, leadership, product management, and delivery competencies required for agile project environments.
Exam Rules
- You can skip questions and return to them later
- Flag questions for review before submitting
- No feedback shown until you submit the entire exam
- Unanswered questions count as wrong — answer everything
- 10 pretest questions are mixed in and don't affect your score
- Timer auto-submits when time runs out
- Your progress is auto-saved every 30 seconds