25 Questions — PMI - CAPM : Certified Associate in Project Management - Domain 3 - Agile Frameworks/Methodologies

Expand any question to reveal the correct answer and explanation.

1. 1 A team utilizing Kanban observes that the work-in-progress (WIP) limit for the 'Testing' column has been reached, while the 'Development' column has several items ready to move. What is the most appropriate action for the developers to take according to Kanban principles?

   Consider the core objective of limiting work-in-progress in a pull-based system.

   Collaborate with the testers to help clear the Testing backlog before starting new development tasks.

   Kanban encourages a 'stop starting, start finishing' mindset where team members swarm on bottlenecks to restore flow.

   • ✗ Temporarily increase the WIP limit of the Testing column to maintain development momentum.

     Increasing WIP limits to accommodate bottlenecks defeats the purpose of identifying and resolving flow constraints.

   • ✗ Continue developing new features but keep them in a 'Ready for Testing' buffer outside the board.

     Creating hidden buffers obscures the true state of work-in-progress and violates the principle of visualization.

   • ✗ Alert the Product Owner that the Testing phase is under-resourced and request additional personnel.

     While long-term resource issues may exist, the immediate Kanban response is to manage the flow of the current work within existing constraints.

2. 2 In the Scaled Agile Framework (SAFe), the 6.0 update modified the core values. Which of the following is now explicitly listed as one of the four Core Values of SAFe 6.0?

   Think about the value that emphasizes a constant drive toward organizational and process evolution.

   Relentless Improvement

   Relentless Improvement replaced the previous value of 'Program Execution' in the SAFe 6.0 update.

   • ✗ Built-in Quality

     While essential to SAFe, Built-in Quality is a core principle/practice set rather than one of the four revised Core Values in 6.0.

   • ✗ Program Execution

     This was a core value in SAFe 5.0 but was replaced in the 6.0 version to emphasize the mindset of continuous growth.

   • ✗ Customer Centricity

     Customer Centricity is a mindset and a focal point of the framework, but it is not formally categorized as one of the four Core Values.

3. 3 A project manager is analyzing a burn-down chart during the middle of a Sprint. The 'Remaining Work' line is currently trending significantly above the 'Ideal' line. What does this visualization indicate to the team?

   Focus on what the vertical distance between the actual work line and the target line represents.

   The team is behind schedule and may not complete all items in the Sprint Backlog.

   When the actual work remaining is higher than the ideal trend, it signals that work is being completed slower than planned.

   • ✗ The project scope has decreased, and the team will likely finish early.

     A line trending above the ideal path suggests that more work remains than originally planned for that point in time.

   • ✗ The team's velocity is higher than estimated in the previous Sprint.

     Higher velocity would typically result in the remaining work line trending below the ideal line.

   • ✗ The Product Owner has successfully reprioritized the backlog to deliver higher value.

     Reprioritization within a Sprint doesn't necessarily change the burn-down trend unless items are removed from the Sprint scope entirely.

4. 4 During a Sprint Retrospective, the team identifies that code quality has been declining due to 'heroic' last-minute efforts. Which Extreme Programming (XP) practice would be most effective to recommend for improving real-time quality and knowledge sharing?

   Look for a practice that specifically involves two people working together on the same task.

   Pair Programming

   Pair programming involves two developers working at one station, providing immediate code review and collective problem-solving.

   • ✗ Continuous Integration

     While it helps catch errors early, it does not provide the same level of immediate peer-to-peer knowledge sharing as other practices.

   • ✗ Test-Driven Development

     TDD improves design and quality by writing tests first, but the 'heroic efforts' and knowledge silos are better addressed through collaboration.

   • ✗ Collective Code Ownership

     This is a mindset that allows anyone to change code, but without a specific practice like pairing, it can actually lead to quality inconsistencies.

5. 5 An Agile team is calculating their progress. They define the time from when a work item enters the 'In Progress' column until it reaches 'Done' as which metric?

   Distinguish between the total time since the request was made and the actual duration of the 'work phase'.

   Cycle Time

   Cycle time is the specific duration from the moment work begins on an item until it is completed.

   • ✗ Lead Time

     Lead time measures the total time from a customer's request (entering the backlog) to the delivery of the item.

   • ✗ Throughput

     Throughput measures the number of items completed over a specific period, not the time taken for a single item.

   • ✗ Velocity

     Velocity measures the amount of work (usually in story points) completed per iteration, rather than the duration of individual tasks.

6. 6 In Scrum, who is primarily responsible for the 'Grooming' or refinement of the Product Backlog, including the prioritization of items to maximize business value?

   Identify the role that acts as the primary bridge between stakeholders and the technical team.

   The Product Owner

   The Product Owner is the single individual accountable for managing the Product Backlog and ensuring it reflects the product vision.

   • ✗ The Scrum Master

     The Scrum Master facilitates the process but does not make decisions on the content or priority of the backlog.

   • ✗ The Development Team

     The team provides estimates and technical input during refinement, but they do not own the priority of the items.

   • ✗ The Project Manager

     Standard Scrum does not define a Project Manager role; these responsibilities are distributed among the three Scrum roles.

7. 7 A team is transitioning from a predictive approach to an adaptive one. They are trying to determine how to translate their Work Breakdown Structure (WBS). What is the most logical transformation for a WBS in an adaptive environment?

   Consider which adaptive artifacts are used to manage and decompose project scope.

   The WBS is mapped into Product Backlog items and User Stories.

   Adaptive projects decompose scope into backlogs and stories that can be prioritized and delivered in iterations.

   • ✗ The WBS is replaced by a Gantt chart with fixed milestones.

     Gantt charts are traditional predictive tools and do not support the iterative nature of adaptive delivery.

   • ✗ The WBS becomes a set of fixed work packages that cannot be changed once the first iteration starts.

     This approach is still predictive; adaptive delivery requires the flexibility to change and refine scope throughout the project.

   • ✗ The WBS is converted into a Resource Breakdown Structure to manage team assignments.

     While resources are important, the WBS specifically represents scope, which in Agile is managed via the backlog.

8. 8 The Agile Manifesto prioritizes 'Responding to change' over 'Following a plan.' In a practical project scenario, how is this value most accurately applied?

   Think about the relationship between structure and flexibility in the Agile mindset.

   The team acknowledges the value of a plan but prioritizes adapting to new information and stakeholder feedback.

   This reflects the manifesto's balance: there is value in the items on the right (planning), but more value in the items on the left (responding).

   • ✗ Plans should be avoided entirely as they restrict the team's ability to be agile.

     Agile teams still plan (e.g., Sprint Planning, Release Planning), but they do not treat the plan as immutable.

   • ✗ The team should follow the initial project plan unless a formal Change Control Board approves a deviation.

     Formal Change Control Boards are characteristic of predictive methodologies, not adaptive ones.

   • ✗ Change requests should only be accepted if they do not impact the current iteration's goal.

     While the Sprint goal is protected, the broader project is always open to adaptation based on value.

9. 9 Which of the following scenarios best justifies the use of an adaptive (Agile) approach over a predictive (Waterfall) approach?

   Identify the environment characterized by the highest levels of uncertainty and the need for rapid feedback.

   The project involves developing a new mobile app where user preferences are unknown and technology is evolving rapidly.

   High uncertainty and the need for frequent feedback make adaptive, iterative delivery the most suitable choice.

   • ✗ The project involves building a bridge where the blueprints and regulations are strictly defined.

     Stable requirements and well-understood technology in a physical construction context favor predictive approaches.

   • ✗ The project is a large-scale government data migration with a fixed budget and zero tolerance for scope changes.

     Fixed scope and high regulation often necessitate the rigorous upfront planning of predictive models.

   • ✗ The project requires a sequential phase-gate approval process to unlock funding for each department.

     Phase-gate approvals and sequential department involvement are hallmarks of traditional predictive life cycles.

10. 10 In a Scrum environment, what is the primary purpose of the Daily Scrum meeting?

    Consider the meeting's duration and its intended audience: the self-organizing team.

    For the Development Team to synchronize activities and create a plan for the next 24 hours.

    The Daily Scrum is a 15-minute time-boxed event for the team to inspect progress toward the Sprint Goal and adapt their plan.

    • ✗ To provide a detailed status report to the Product Owner and external stakeholders.

      The Daily Scrum is for the developers to sync, not for status reporting to management.

    • ✗ To allow the Scrum Master to assign specific tasks to team members for the next 24 hours.

      Agile teams are self-organizing; the Scrum Master does not assign work.

    • ✗ To conduct a technical deep-dive and solve complex architectural issues identified in the Sprint.

      Deep-dives and problem-solving should happen outside the 15-minute Daily Scrum to keep it focused and efficient.

11. 11 An adaptive project is using MoSCoW prioritization. If a requirement is categorized as a 'Should Have,' how should it be treated relative to 'Must Have' requirements?

    Think about the priority level that sits just below 'vital for launch'.

    It is important but not vital; it should be delivered if time and resources allow after 'Must Haves' are secured.

    'Should Haves' are high priority but have workarounds or are not immediately critical for a viable release.

    • ✗ It is essential for the product to be considered a success and must be delivered in the current increment.

      Essential requirements that are non-negotiable for success are 'Must Haves'.

    • ✗ It is a low-priority item that will only be considered if all other categories are completed early.

      Low-priority items that are desirable but not critical are usually 'Could Haves'.

    • ✗ It is a requirement that the stakeholders have agreed will not be delivered in the current release cycle.

      Requirements deferred to future cycles are 'Won't Haves' (for now).

12. 12 What is the primary function of a 'Definition of Done' (DoD) in an adaptive project?

    Consider the difference between requirements for one feature and quality standards for the whole product.

    To provide a checklist of technical and quality criteria that every increment must meet to be considered potentially releasable.

    The DoD ensures a common understanding of what 'finished' work looks like, maintaining transparency and quality.

    • ✗ To serve as a contract between the team and the customer regarding project scope.

      Adaptive projects avoid rigid contracts on scope and use the DoD to ensure quality standards instead.

    • ✗ To document the final sign-off from the Project Sponsor at the end of the project life cycle.

      The DoD is applied at the end of every iteration or for every work item, not just at the end of the project.

    • ✗ To list the specific business requirements that must be met for a single User Story.

      Specific requirements for a single story are 'Acceptance Criteria'; the DoD applies globally to all work items.

13. 13 A team is transitioning to 'flow-based agile' (Kanban). They want to identify bottlenecks in their process by visualizing work across different stages. Which tool is most effective for this specific purpose?

    Look for a chart that represents the 'accumulation' of work in different phases over time.

    Cumulative Flow Diagram (CFD)

    CFDs show the distribution of work items across stages, making it easy to spot widening bands that indicate bottlenecks.

    • ✗ Burn-down Chart

      Burn-down charts track work remaining over time but do not show where work is piling up in specific process stages.

    • ✗ Velocity Chart

      Velocity charts track output per iteration but provide no insight into internal process flow or bottlenecks.

    • ✗ Risk Register

      Risk registers track uncertainties, not the actual flow of work items through a development pipeline.

14. 14 How does the role of a 'Servant Leader' differ from a traditional Project Manager in an Agile environment?

    Consider which role emphasizes 'removing blockers' and 'coaching' over 'assigning tasks'.

    The Servant Leader focuses on removing impediments and supporting the team's needs rather than commanding and controlling tasks.

    Servant leadership emphasizes service to the team, facilitation, and coaching over traditional directive management.

    • ✗ The Servant Leader is responsible for making all technical decisions to protect the team from distractions.

      Agile teams make their own technical decisions; a servant leader facilitates the environment for them to do so.

    • ✗ The Servant Leader acts as a proxy for the Product Owner to ensure the team is working on the right priorities.

      The Product Owner interacts directly with the team; the servant leader (like a Scrum Master) ensures the process is followed.

    • ✗ The Servant Leader has no authority and simply observes the team to provide feedback during retrospectives.

      Servant leaders have the authority to enforce process rules and are active in removing organizational roadblocks.

15. 15 During Sprint Planning, the team is struggling to estimate the effort for a complex User Story. Which estimation technique is commonly used in Agile to compare the relative size of stories using a non-linear scale?

    Recall a collaborative, consensus-based method that uses cards and relative values.

    Planning Poker

    Planning Poker uses relative sizing (often the Fibonacci sequence) to reach a consensus on effort without the pressure of hourly estimates.

    • ✗ Three-Point Estimating

      Three-point estimating is a predictive technique using optimistic, pessimistic, and most likely values.

    • ✗ Critical Path Analysis

      Critical Path Analysis determines the longest sequence of tasks in a predictive schedule, not the size of individual stories.

    • ✗ Bottom-Up Estimating

      Bottom-up estimating involves summing detailed task estimates, which is less common in the high-level relative sizing used in Agile planning.

16. 16 Which Agile ceremony is specifically designed for stakeholders to inspect the increment and for the Product Owner to update the Product Backlog based on feedback?

    Identify the event that focuses on 'what' was built rather than 'how' the team worked together.

    Sprint Review

    The Sprint Review is a collaborative session where the team shows what they built to stakeholders to gather feedback and adapt the backlog.

    • ✗ Sprint Retrospective

      The Retrospective is for the internal team to inspect their process, not for stakeholders to inspect the product.

    • ✗ Daily Stand-up

      The Daily Stand-up is an internal 15-minute synchronization for the development team.

    • ✗ Backlog Refinement

      Refinement is an ongoing activity to prepare stories for future sprints, not a formal ceremony for stakeholder inspection of a finished increment.

17. 17 An Agile team identifies a risk that a third-party API may not be ready in time for the next Sprint. In an adaptive framework, how should this risk primarily be managed?

    Consider the Agile principle of rapid feedback and the Scrum Master's role in removing blockers.

    Discuss the impediment in the Daily Scrum and have the Scrum Master work to resolve the external dependency.

    In Agile, risks are treated as potential impediments and addressed through daily synchronization and servant leadership.

    • ✗ Include the risk in the formal project risk register and wait for the monthly risk review meeting.

      This is a predictive approach; Agile requires more frequent and immediate risk management.

    • ✗ Update the Gantt chart to show a mandatory lag and notify the sponsor of a likely milestone delay.

      Adaptive projects typically avoid Gantt charts and focus on adjusting the backlog and iteration plans instead.

    • ✗ Instruct the developers to work overtime to build a mock API to bypass the dependency.

      Overtime is not a sustainable Agile practice; the focus should be on resolving the root dependency or adjusting the plan.

18. 18 In the context of the Agile Practice Guide, what is the purpose of an 'Agile Suitability Filter'?

    Think about the tool used during project initiation to choose a development life cycle.

    To help project professionals evaluate whether a project is better suited for predictive, adaptive, or hybrid delivery.

    The suitability filter assesses factors like culture, team size, and requirements uncertainty to recommend a delivery model.

    • ✗ To screen potential team members for their knowledge of Scrum and Kanban.

      The filter is for project approaches, not for hiring or personnel evaluation.

    • ✗ To automatically remove low-priority items from the Product Backlog.

      Backlog prioritization is a human decision made by the Product Owner, not an automated filter.

    • ✗ To determine the maximum number of story points a team can take into a Sprint.

      This is determined by team capacity and velocity, not by a suitability filter.

19. 19 A team is using a 'Burn-up Chart' instead of a 'Burn-down Chart.' What unique information does the Burn-up chart provide that the Burn-down chart typically does not visualize clearly?

    Consider which chart shows a line for the 'finish line' moving over time.

    The relationship between total scope and completed work, including scope creep.

    Burn-up charts have a separate line for 'Total Scope,' allowing stakeholders to see if the project is taking longer because of poor performance or increased requirements.

    • ✗ The team's velocity over the last three iterations.

      Velocity is usually tracked in a separate bar chart; both burn charts imply it but don't show the specific calculation as well as a dedicated chart.

    • ✗ The number of bugs identified during the testing phase.

      Defect tracking is managed through bug reports or quality metrics, not through standard burn-up charts.

    • ✗ The specific names of the developers assigned to each task.

      Burn charts are high-level progress indicators and do not track individual resource assignments.

20. 20 Which adaptive framework emphasizes 'Visualizing the workflow,' 'Limiting WIP,' and 'Managing Flow' as its core practices, without requiring fixed-length iterations?

    Identify the methodology often used for maintenance or support work where priorities change daily.

    Kanban

    Kanban is a flow-based method that focuses on continuous delivery rather than time-boxed iterations.

    • ✗ Scrum

      Scrum requires fixed-length iterations called Sprints.

    • ✗ Extreme Programming (XP)

      XP typically uses iterations and focuses heavily on technical engineering practices like TDD.

    • ✗ Waterfall

      Waterfall is a predictive methodology, not an adaptive framework.

21. 21 In an Agile project, what is the role of the 'Project Management Office' (PMO) compared to a traditional PMO?

    Think about how a centralized office can 'serve' rather than 'command' project teams.

    The Agile PMO focuses on providing value-based metrics, coaching, and supporting self-organizing teams.

    An Agile PMO acts more as a center of excellence, facilitating knowledge sharing and removing organizational obstacles.

    • ✗ The Agile PMO enforces strict adherence to the project management plan and baselines.

      Agile PMOs are more supportive and adaptive, moving away from rigid enforcement of upfront plans.

    • ✗ The Agile PMO is responsible for selecting the specific tasks for the team's next iteration.

      Agile teams and the Product Owner decide on iteration content; the PMO does not intervene at that level.

    • ✗ The Agile PMO is usually disbanded because Agile teams do not require organizational governance.

      PMOs still exist in Agile organizations but their focus shifts toward governance through value and supporting decentralized decision-making.

22. 22 A team is practicing 'Iteration-based Agile.' They have just finished their first Sprint and their velocity was 20 points. For the second Sprint, the Product Owner adds 50 points of new items to the Product Backlog. What should the team do regarding the second Sprint's capacity?

    Consider the principle of using past performance to predict future results in a self-organizing team.

    Commit to approximately 20 points based on their demonstrated capacity from the first Sprint.

    Agile planning is based on empirical data; velocity from previous increments is the best predictor for future iterations.

    • ✗ Commit to 50 points for the second Sprint to match the Product Owner's new requirements.

      Teams should not commit to more work than their proven velocity allows.

    • ✗ Split the team into two groups to handle 25 points each, ensuring all new items are addressed.

      Adding people or splitting teams does not immediately increase capacity and can actually decrease it due to the 'Brook's Law' effect.

    • ✗ Ask the Scrum Master to decide how many points the team should take to ensure project milestones are met.

      The team determines its own capacity; the Scrum Master facilitates the planning but does not decide on the commitment.

23. 23 Which of the following is a key characteristic of 'User Stories' in Agile project management?

    Look for an acronym that defines the quality of an Agile requirement.

    They should follow the 'INVEST' criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable.

    The INVEST acronym describes the quality characteristics of a well-formed user story.

    • ✗ They must be written by a technical architect to ensure they are feasible for development.

      User stories are typically written from the perspective of the end-user or customer to focus on value.

    • ✗ They represent fixed, detailed requirements that replace the need for further conversation.

      User stories are 'placeholders for a conversation,' not comprehensive documentation.

    • ✗ They are only used in predictive methodologies to define work packages.

      User stories are a primary tool in adaptive/Agile methodologies for managing requirements.

24. 24 A project involves multiple Scrum teams working on a single product. How is coordination typically handled between these teams to manage dependencies and shared resources?

    Identify the technique used to 'scale' the daily synchronization ceremony.

    A 'Scrum of Scrums' meeting is held where representatives from each team sync on progress and blockers.

    Scrum of Scrums is a standard scaling technique for multi-team coordination.

    • ✗ All team members attend a single 4-hour Daily Scrum to ensure full transparency.

      This would be highly inefficient and violates the 15-minute time-box of the Daily Scrum.

    • ✗ The Project Sponsor makes the final decision on all cross-team resource conflicts.

      Sponsors provide governance but are too far removed from daily operations to manage inter-team dependencies effectively.

    • ✗ The individual Product Owners merge their teams into one large development group.

      Scrum teams should remain small (typically 10 or fewer); very large teams suffer from communication overhead.

25. 25 In an adaptive project, what is the primary purpose of 'Spikes'?

    Think about what a team does when they encounter a technical 'unknown' that prevents estimation.

    To conduct time-boxed research or prototyping to reduce technical uncertainty or refine estimates.

    Spikes are used when the team needs to learn more about a technology or requirement before they can estimate or build it reliably.

    • ✗ To deliver a high-value customer feature early in the project life cycle.

      Features are delivered via standard user stories; spikes are for exploration, not production features.

    • ✗ To provide a buffer at the end of the project for unexpected bug fixes.

      Agile teams fix bugs as they go; spikes are proactive research tools, not reactive buffers.

    • ✗ To punish the team for failing to meet their Sprint commitment.

      Agile environments are supportive; 'spikes' are technical tools, not disciplinary actions.