CAPM Agile Frameworks and Methodologies Practice Test 7 — 15 Questions

Question 1

Which TWO statements correctly describe characteristics of the Kanban method?

Accepted Answer

Work in progress limits are used to improve flow. Option C is correct because a defining characteristic of the Kanban method is the use of explicit work-in-progress (WIP) limits, which constrain how many items can be in a given workflow state at once and thereby improve flow, reduce multitasking, and expose bottlenecks. Option E is correct because Kanban relies on visualizing the workflow on a Kanban board, typically with columns representing process states and cards representing work items, so the team can see status and manage flow. Option A is incorrect because Kanban does not require a team to be dedicated to a single project; it can be applied to shared or multi-project teams and to ongoing service work. Option B is incorrect because the strict product owner, Scrum Master, and development team roles belong to Scrum, whereas Kanban prescribes no mandatory roles. Option D is incorrect because fixed two-week timeboxed iterations are a Scrum practice, while Kanban is based on continuous flow rather than mandatory timeboxed sprints.

Answer

The team must be dedicated to a single project

Answer

Roles are strictly defined as product owner, Scrum Master, and development team

Answer

Iterations are timeboxed to two weeks

Question 2

According to the Scrum Guide, which THREE of the following are Scrum events?

Accepted Answer

Daily Scrum. The Scrum Guide defines exactly five formal events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Option B (Daily Scrum) is correct because it is the 15-minute daily event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Option C (Sprint Planning) is correct because it is the event that initiates the Sprint, where the Scrum Team defines the Sprint Goal and the work to be done. Option E (Sprint Retrospective) is correct because it is the final event of the Sprint, where the team inspects itself and creates a plan for improvements. Option A (Product Backlog Refinement) is not a Scrum event; it is an ongoing activity for adding detail and estimates to backlog items, and the Guide explicitly calls it an activity, not an event. Option D (Release Planning) is not a Scrum event either; it is a traditional/auxiliary planning practice that is not part of the Scrum framework's defined events.

Answer

Product Backlog Refinement

Answer

Release Planning

Question 3

Which TWO are benefits of using an iterative approach in agile projects?

Accepted Answer

Ability to adapt to changing requirements. Option A is correct because iterative development delivers working increments each iteration, allowing the team to incorporate changing requirements between iterations rather than being locked into an upfront specification. Option C is correct because each iteration produces a demonstrable increment that stakeholders can review, generating frequent and early feedback that guides subsequent work. Option B is not a defining benefit, since agile values working software over comprehensive documentation but does not eliminate necessary documentation. Option D is not guaranteed, as iterative approaches can increase cost through rework and continuous involvement. Option E is incorrect because testing is continuous within each iteration, not postponed to the end.

Answer

Less documentation is needed

Answer

Reduced overall project cost

Answer

Postponed testing until the end of the project

Question 4

A financial services company is adopting Scrum for a critical compliance project. The team has six developers, one product owner, and one Scrum Master. After three sprints, the product owner is frustrated because the team has only delivered 40% of the planned features. The team says they are working full capacity but keep getting interrupted by urgent production support requests from the operations team. The Scrum Master notices that the team’s velocity is dropping each sprint. The product owner insists on increasing the sprint length from two weeks to four weeks to allow more time for delivery. However, the compliance deadline is fixed. The Scrum Master must recommend a course of action. What should the Scrum Master do?

Accepted Answer

Ask the product owner to prioritize production support requests as part of the sprint backlog and limit work in progress. It addresses the root cause of the team's velocity drop: unplanned production support requests. By asking the Product Owner to prioritize these requests into the sprint backlog, the team can formally account for the work, limit work in progress (WIP), and maintain a sustainable pace. This aligns with Scrum's principle of transparency and allows the team to make realistic commitments while still protecting the fixed compliance deadline.

Answer

Instruct the team to work overtime to meet the original sprint commitments

Answer

Increase the sprint length to four weeks to give the team more time to complete work

Answer

Remove the Scrum Master position to save costs and let the team self-manage

Question 5

A startup is using Scrum to develop a mobile app. The product owner has a clear vision and has written detailed user stories for the first release. During sprint planning, the development team estimates that they can complete 40 story points per sprint. However, after two sprints, the team has only completed 30 points per sprint. The product owner is concerned and wants to hold the team accountable. The team says that the estimates were optimistic and that they are still learning the technology. The Scrum Master notices that the team is not using pair programming or test-driven development (TDD) as originally planned. The product owner suggests reducing scope for the next sprint to match the team’s actual velocity. The Scrum Master must decide the best way to proceed. What should the Scrum Master do?

Accepted Answer

Encourage the product owner to use the actual velocity of 30 as the basis for future sprint planning. The Scrum Master should use empirical data (actual velocity of 30 story points) to guide future sprint planning, not the initial optimistic estimate. This aligns with the Agile principle of transparency and adapting based on real team performance, especially when the team is still learning the technology. The product owner can then adjust scope realistically, avoiding overcommitment and fostering trust.

Answer

Replace the team lead to send a message about accountability

Answer

Set a goal of 40 story points and ask the team to be more productive

Answer

Insist that the team adopt pair programming and TDD immediately to improve productivity

Question 6

A newly formed agile team is about to start their first sprint. The product owner has a well-groomed backlog and the team has done relative sizing using planning poker. The team is excited but unsure about the process. They ask the Scrum Master what the primary goal of the first iteration should be. The Scrum Master should explain that the most important goal of the first sprint is to deliver a potentially releasable increment of the product. However, some team members are worried they may not be able to deliver enough due to team formation and learning the codebase. The product owner wants to see a visible outcome. What should the Scrum Master recommend as the primary focus for the first sprint?

Accepted Answer

Deliver a small but complete user story that adds value to the product. In Scrum, the primary goal of every sprint, including the first, is to deliver a potentially releasable increment of the product. Option C is correct because delivering a small but complete user story that adds value ensures the team practices the full Scrum cycle—from backlog refinement to definition of done—while producing a tangible outcome that satisfies the product owner's need for visible progress. This approach balances team learning with value delivery, which is the core purpose of an agile iteration.

Answer

Create a detailed design document for the entire release

Answer

Focus exclusively on setting up the development environment and CI/CD pipeline

Answer

Skip the sprint goal to allow the team to learn without pressure

Question 7

During a sprint review, the team demonstrates a new feature to stakeholders. One stakeholder says, 'This isn't what we wanted. We need a completely different approach.' The product owner is upset because the feature took two weeks to build. The team is frustrated because they followed the product owner's specifications exactly. The Scrum Master observes that the product owner did not involve stakeholders during the sprint and based the user stories on assumptions. The product owner wants to add the rework to the next sprint. However, the team's capacity is already full. The Scrum Master needs to help the team and product owner recover. What should the Scrum Master do first?

Accepted Answer

Coach the product owner to collaborate with stakeholders during the sprint to validate assumptions early. The Scrum Master should first coach the product owner to collaborate with stakeholders throughout the sprint so assumptions are validated early, preventing late-surfacing misalignment. This addresses the root cause — the product owner built user stories on unvalidated assumptions without stakeholder involvement — rather than treating the symptom of rework. Coaching the product owner is a core Scrum Master responsibility and a servant-leadership action.

Answer

Remove the product owner from the project to prevent future miscommunication

Answer

Blame the team for not clarifying requirements during the sprint

Answer

Add the rework to the next sprint and ask the team to work overtime

Question 8

An agile team is using a burndown chart for the first time. After six days of a two-week sprint, the burndown chart shows that the remaining work has increased compared to the previous day. The team is confused. They had completed several tasks, but new tasks were added to the sprint backlog after the sprint started. The product owner says the additions were urgent and necessary. The development team is frustrated because they feel the sprint goal is at risk. The Scrum Master must address this situation. What should the Scrum Master do?

Accepted Answer

Ask the product owner and team to renegotiate the sprint scope, either removing some planned work or deferring the new work to the next sprint. The Scrum Master should facilitate a negotiation between the product owner and the development team to re-evaluate the sprint backlog. In Scrum, the sprint backlog can be clarified or renegotiated with the product owner, but the sprint goal must remain achievable. By asking the team and product owner to either remove planned work or defer the new tasks, the Scrum Master protects the sprint goal and maintains team focus, which is the core responsibility of the Scrum Master in an agile framework.

Answer

Instruct the team to ignore the burndown chart and focus on delivering the original sprint goal

Answer

Explain to the product owner that the sprint backlog is frozen once the sprint starts and cannot be changed

Answer

Manually adjust the burndown chart to show the completed tasks and hide the additional work

Question 9

A Scrum team is preparing for its Sprint Review. The Product Owner wants to know which artifacts the team should present to stakeholders to demonstrate the completed work. What is the most appropriate focus for the Sprint Review?

Accepted Answer

The Increment and the updated Product Backlog. The Sprint Review is a collaborative event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog. The correct answer highlights these two artifacts. The other choices refer to internal tools or traditional documents that are not the focus of this event.

Answer

The Sprint Backlog and the team's velocity chart

Answer

The Definition of Done and the team's burndown chart

Answer

The project charter and the risk register

Question 10

An agile team has been running two-week Sprints for several months. During each Sprint Review, stakeholders provide feedback, but the team notices that the same concerns keep resurfacing and no one owns follow-up actions. The Scrum Master wants to ensure that the team inspects how it is working and adapts its process. Which Scrum event should the Scrum Master focus on to address this?

Accepted Answer

Sprint Retrospective. The Sprint Retrospective is the dedicated Scrum event for the team to inspect how it worked during the Sprint and adapt its process. Recurring concerns with no owner indicate a gap in process improvement, which is exactly what the Retrospective addresses. Sprint Review, Daily Scrum, and Sprint Planning serve product, daily coordination, and planning purposes respectively, so they do not provide the structured process-improvement focus required.

Answer

Daily Scrum

Answer

Sprint Review

Answer

Sprint Planning

Question 11

An agile team is adopting Extreme Programming (XP). A developer asks how the practice of continuous integration differs from simply building the software nightly. Which statement best describes the XP practice of continuous integration?

Accepted Answer

Code is integrated and tested multiple times per day, often with each commit.. XP continuous integration involves integrating and testing code many times a day, often with each commit. This provides rapid feedback and minimizes integration issues. The other options describe less frequent integration practices that do not align with XP's emphasis on continuous feedback and small batches.

Answer

Code is integrated at the end of each iteration after a code freeze.

Answer

Code is integrated only after all unit tests pass on the developer's machine.

Answer

Code is integrated once per sprint during the Sprint Review.

Question 12

A Scrum team is halfway through a two-week Sprint when the Product Owner asks them to add a new high-priority feature that was not in the Sprint Backlog. The team believes they can complete it without jeopardizing the Sprint Goal. According to Scrum, what should the team do?

Accepted Answer

Add the feature to the Sprint Backlog and continue working toward the Sprint Goal.. The Sprint Backlog is a plan by and for the Developers, and it is updated throughout the Sprint as more is learned. Because the team judges that the new feature can be added without endangering the Sprint Goal, they may incorporate it. The Product Owner may influence priority, but the team decides how to manage its own work within the Sprint.

Answer

Reject the request because the Sprint Backlog cannot be changed once the Sprint has started.

Answer

Cancel the Sprint and start a new one with the updated priorities.

Answer

Ask the Project Management Office (PMO) to approve the scope change before proceeding.

Question 13

A Scrum team's Sprint Review is scheduled for Friday afternoon. The team has completed all but two Product Backlog items. The Product Owner asks the Scrum Master whether the incomplete items should be demonstrated during the Sprint Review. What is the most appropriate guidance the Scrum Master should provide?

Accepted Answer

Demonstrate only the items that meet the Definition of Done, and discuss the incomplete items as part of the review's inspection of the Increment.. The Sprint Review inspects the Increment and adapts the Product Backlog. Only work meeting the Definition of Done counts as part of the Increment, so completed items are demonstrated, while incomplete items are discussed to inform adaptation. The Scrum Master should guide the team toward transparency and empiricism rather than hiding or misrepresenting progress.

Answer

Cancel the Sprint Review because the Sprint Goal was not fully met and the Increment is incomplete.

Answer

Ask the Product Owner to move the incomplete items to the next Sprint and exclude them from any discussion during the Sprint Review.

Answer

Demonstrate all items, including the incomplete ones, to show stakeholders the team's full effort during the Sprint.

Question 14

A Scrum Team is struggling with unclear requirements. The Product Owner wants to ensure the team has a shared understanding of a user story before development begins. Which of the following is the most appropriate technique?

Accepted Answer

Hold a backlog refinement session to discuss and split the user story.. Backlog refinement is the Scrum practice for reviewing and updating the Product Backlog, including clarifying and splitting user stories. It provides the shared understanding the team needs before development begins. Sprint Review, Scrum Master-authored specifications, and Daily Scrum discussions occur too late or violate Scrum roles, so they do not adequately address unclear requirements.

Answer

Wait until the Sprint starts and let developers ask questions during the Daily Scrum.

Answer

Ask the Scrum Master to write detailed technical specifications for the story.

Answer

Conduct a Sprint Review to clarify requirements with stakeholders.

Question 15

A Scrum team is struggling with its Daily Scrum. The Scrum Master notices that the meeting often runs long, turns into a status report to the Scrum Master, and does not result in a clear plan for the next 24 hours. Which two actions should the Scrum Master take to improve the Daily Scrum? (Choose two.)

Accepted Answer

Coach the team to focus on inspecting progress toward the Sprint Goal and adapting the Sprint Backlog.. The Daily Scrum exists for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, and it must be self-managed. Coaching the team to focus on these outcomes and to own the event addresses the root causes of long, status-oriented meetings. The Scrum Master serves as a teacher and facilitator, not a chairperson.

Answer

Allow the Product Owner to lead the Daily Scrum to ensure priorities are communicated.

Answer

Extend the timebox to 30 minutes to give everyone enough time to speak.

Answer

Instruct each team member to answer the three standard questions in strict order.