PMI Practice Questions, Discussions & Exam Topics by our Authors

A team is preparing to demonstrate new product capabilities to a leadership team. The demonstration will show working software and a listing of the projected value of the capabi...

To ensure the demonstration is successful, the team should prioritize a clear and impactful presentation of both the working software and its value proposition to the leadership team. The goal is to show the practical and tangible value of the product and how it meets stakeholder expectations. Let's break down each option: A) Provide an understanding of business value and customer feedback. - Pros: Business value and customer feedback are critical for demonstrating that the product is solving real problems and adding value. However, the demonstration itself might not fully benefit from just understanding value and feedback unless those elements are clearly connected to the product’s capabilities in the demonstration. - Cons: This option might be somewhat abstract if not directly tied to the product's functionality being shown. While understanding value is important, feedback alone doesn't guarantee alignment with the leadership team's expectations of a working product. B) Align with stakeholder expectations and releasable product increments. - Pros: This is the most directly relevant option. Aligning with stakeholder expectations is key to making the demonstration successful, especially when the product is being presented to leadership. By focusing on releasable increments, the team shows that they are ready to deploy or deliver real functionality to customers soon. This ensures the leadership team sees a product that is practical, usable, and aligned with business goals. - Cons: None significant. This option is strongly aligned with the objective of demonstrating both capabilities and value in...

Author: Leah · Last updated Jul 9, 2026

When working on a new product, what should an agile team do to ensure alignment with external stakeh...

To ensure alignment with external stakeholders, the agile team needs to establish clear communication, expectations, and shared understanding early on. The goal is to ensure the product being built aligns with what stakeholders need and that their expectations are continuously met throughout development. Let’s review each option: A) Hold a kick-off meeting to assign roles. - Pros: A kick-off meeting is useful for setting expectations and aligning the team internally. It can help clarify roles within the team and get everyone on the same page regarding the project’s objectives. - Cons: While a kick-off meeting is important for internal team alignment, it does not directly engage with external stakeholders. It focuses on internal processes rather than ensuring alignment with external partners, users, or business needs. B) Review the project vision statement. - Pros: This is a very effective approach. The project vision statement provides the high-level understanding of the product’s purpose, goals, and intended outcomes. By reviewing and aligning with the vision, the team can ensure they are building the right product that aligns with the stakeholders' needs. It also provides a common reference point for ongoing communication and decision-making, keeping everyone on the same page as the project evolves. - Cons: There aren’t many cons here, as reviewing the vision statement is a foundational practice. However, it must be ensured that the vision statement is regularly updated and revisited throughout the development process. C) Ask the product owner for a detailed product-spec...

Author: Sofia2021 · Last updated Jul 9, 2026

On an agile project, it is important to identify and engage business stakeholders throughout the project and to ensure the team understands the ...

To ensure that the agile team understands the business needs of stakeholders and remains aligned throughout the project, it is important to facilitate ongoing engagement with stakeholders and capture their input in a way that is actionable and keeps the focus on delivering business value. Let's evaluate each option in this context: A) A project charter should be established and reviewed throughout the project life cycle to ensure the accurate documentation of stakeholders' interests and expectations. - Pros: A project charter helps establish the initial understanding of the stakeholders’ interests and expectations. It provides high-level guidance on project goals, scope, and stakeholders’ roles. Reviewing it periodically ensures that the team is aligned with stakeholder expectations as the project progresses. - Cons: While the project charter is valuable at the start of a project, it is often a one-time document and may not support the continuous engagement of stakeholders throughout the project lifecycle. The agile process requires dynamic feedback and iteration rather than rigid documentation. B) A product backlog should be created to list the project requirements from all of the project stakeholders. - Pros: The product backlog is a core artifact in agile, and it directly addresses the need to gather and prioritize requirements from stakeholders. It evolves throughout the project as new insights emerge, and it serves as a dynamic list of business needs and priorities, which ensures ongoing stakeholder engagement and alignment with business goals. - Cons: While the product backlog is a great tool for tracking requirements, it does not by itself ensure active, continuous engagement with stakeholders. The backlog must be refined and adjusted in collaboration with stakeholders, which might not be immediately obvious unless the team actively engages with them during backlog grooming and spr...

Author: Zara · Last updated Jul 9, 2026

A high-profile project team is struggling to meet planned velocity. During a retrospective, the team agreed that their lack of experience in the technology resulted i...

When a project team is struggling with meeting velocity due to lack of experience in the technology, the focus should be on addressing the skill gap and allowing the team to experiment and improve their understanding and approach to the technology. This will help reduce rework and improve the team’s efficiency over time. Let's evaluate each option in the context of this situation: A) Increase the duration of iterations to minimize the frequency of priority changes that are distracting the team. - Pros: Increasing the duration of iterations could give the team more time to complete their work, reducing the pressure of tight deadlines. It might also reduce distractions if there are frequent priority changes. - Cons: The root cause of the problem is not related to iteration length or priority changes, but to a lack of experience with the technology. Lengthening iterations does not address the underlying issue of technical capability. It could also lead to slower feedback cycles, which would be detrimental to learning and improvement in an agile environment. B) Reduce the duration of iterations so that the product owner can reprioritize work to ensure business value alignment. - Pros: Reducing iteration length might help the product owner adjust priorities more frequently, ensuring that the most valuable work is always being tackled. - Cons: This option is more about flexibility in business priorities than addressing the core issue of technical proficiency. Shorter iterations might lead to more frequent sprints, but it doesn’t help the team build the skills needed to reduce rework and improve their velocity. It could also result in more frequent context switching, making it harder to focus on mastering new technology. C) Increase the level of effort in testing to ensure that all defects are identified and properly documented so they can be resolved before the end of the iteration. - Pros: More testing can help identify defects early, but it assumes tha...

Author: James · Last updated Jul 9, 2026

During a retrospective, the team agrees that they have limited competence in using a newly introduce...

When the team identifies that they have limited competence in using a newly introduced tool, the goal should be to increase their proficiency without disrupting the flow of the current work. The team needs a strategy that builds competence over time while ensuring that they don't overburden themselves in the short term. Let’s evaluate each option: A) Explore options for increasing knowledge in the next iteration’s backlog. - Pros: This option is proactive and aligns with agile principles. By exploring knowledge-building activities in the backlog, the team can dedicate time to training or learning in the next sprint without interrupting their current work. This approach gives the team the chance to plan and schedule focused learning activities, such as researching the tool or having team members take courses or attend workshops. - Cons: This option might delay the learning process slightly, as it’s not an immediate fix. However, it ensures that the team systematically builds competence rather than rushing into something unplanned. B) Experiment with the tool's usage by adding extra tasks in the current iteration. - Pros: Experimenting immediately with the tool can help the team learn by doing, which can lead to faster learning and application of the tool. - Cons: Adding extra tasks to the current iteration could disrupt the team's workflow, potentially affecting the completion of existing tasks and diminishing overall productivity. This can also increase the risk of burnout and may not allow enough time for meaningful learning. Experimenting with the tool might not be as effective without proper preparation or support. C) Propose alternative tools that the team is more competent usi...

Author: Zara · Last updated Jul 9, 2026

The agile lead is told by executive leadership that the team needs to work faster because the release date has been moved up three months. The agile lead communicates the updated timeline to the team. One of the junior team ...

In this scenario, the junior team member is facing a conflict between their own perception of the timeline and the need to follow updated expectations from leadership. To determine the best course of action, it’s important to consider the following key factors: 1. Clear communication – Effective communication is crucial in agile teams. A junior member who feels that the timeline is unrealistic should raise their concerns constructively, as this helps the team assess the feasibility of the schedule and avoid potential issues down the line. 2. Understanding team dynamics – In an agile environment, collaboration and transparency are vital. Addressing concerns in a private or one-on-one setting (with the agile lead) is often more effective than confronting the entire team. 3. Team accountability – While individual responsibility is important, the team collectively owns the process and results. Relying on one person to adjust things drastically (e.g., by working more hours) could lead to burnout or diminished team performance, so this is not a sustainable solution. 4. Prioritization and realistic expectations – The timeline might need to be revisited by the agile lead or the team. Simply following the lead without raising concerns could lead to unachievable goals and impact quality. Now, let’s evaluate the options: Option A: Speak to the agile lead about the concerns - Why selected: The most appropriate course of action. The junior team member should express their concerns directly to the agile lead, who can then evaluate whether the updated timeline is feasible and communicate with leadership if adjustments are necessary. This option maintains the flow of communication and keeps the issue within the team structure. - Reasoning: It’s critical to voice concerns early to avoid mistakes or compromises in quality. This option respects the team dynamics and creates an opportunity for dialogue, ensuring that the junior team member’s concerns are heard without disrupting the br...

Author: Olivia · Last updated Jul 9, 2026

After performing three sprints, the product owner and sponsor request an accurate schedule indicating when all releases wil...

In this scenario, the product owner and sponsor are requesting an accurate schedule for when all releases will be delivered. The key challenge is balancing agile principles of flexibility and responsiveness with the need for predictability and delivery deadlines. Let’s analyze each option in detail to understand which approach is most appropriate: Key factors to consider: - Agile principles: In agile, plans are not rigid; they evolve with the project. Teams work in sprints and are generally focused on delivering incremental value rather than locking down a detailed schedule from the start. - Predictability vs. Flexibility: While agile doesn't typically commit to fixed schedules upfront, teams should have an understanding of their velocity and be able to provide rough timelines based on their capacity and remaining work. - Team maturity and velocity: The team's velocity can offer useful insights, but predicting an exact schedule too early can lead to unrealistic expectations. Therefore, an estimated range rather than an exact commitment may be more appropriate. Option A: Calculate velocity based on completed sprints and triangulate the remaining work on the backlog to commit to an accurate schedule - Why rejected: While velocity is an important factor for estimating delivery timelines, committing to an accurate schedule based on this alone is generally not ideal in an agile environment. Agile teams typically avoid giving precise dates, as this can lead to misalignment between what is committed and actual progress. - Reasoning: Agile planning should allow for flexibility. Committing to an “accurate” schedule based purely on velocity from past sprints can be misleading, as it doesn’t account for potential changes in scope, complexity, or team dynamics. This can put pressure on the team and undermine the agile principles of adaptability. Option B: Decompose the product backlog into user stories with tasks/acceptance criteria and estimate to commit to an accurate schedule - Why rejected: This is a very detailed approach and could lead to excessive planning upfront, which contradicts agile principles. In agile, it's better to f...

Author: RadiantPhoenixX · Last updated Jul 9, 2026

A software project is being implemented by a small, colocated team. What should the project manager do to keep the team foc...

To keep a small, colocated team focused and engaged with high-level requirements, it's essential to create an environment where communication, visibility, and team collaboration are prioritized. Let's review each option based on key factors such as team dynamics, agile principles, and the need to stay focused on high-level requirements: Key factors to consider: - Collaboration and Communication: Small, colocated teams benefit from frequent, direct communication, which fosters alignment and engagement. - Visibility and Focus: The team needs to have clear visibility into their progress and work, ensuring that high-level requirements are not lost in the day-to-day details. - Autonomy and Trust: In an agile context, it’s crucial to avoid micromanaging. The team should have autonomy over how they organize and track their work. Option A: Arrange afternoon touchpoints where the team can discuss what they have done during the day - Why rejected: While regular touchpoints can encourage communication, daily touchpoints in the afternoon are likely to disrupt the team's flow and add unnecessary meetings to the schedule. This could lead to wasted time and reduce the focus on high-level requirements. - Reasoning: Agile teams typically have a daily standup to track progress. Adding an additional afternoon touchpoint risks interrupting the team's natural workflow and could lead to fatigue or disengagement, rather than keeping them focused on the big picture. Option B: Request that the project sponsor is present during daily standups to increase commitment from the team - Why rejected: While the presence of a sponsor could encourage accountability, it can also create pressure on the team and reduce the openness and transparency of the standup. Team members may become less comfortable sharing obstacles or challenges if a high-level stakeholder is present. - Reasoning: Agile principles prioritize team autonomy and self-organization. Having the project sponsor present at daily standups could unintentionally shift the foc...

Author: Maya · Last updated Jul 9, 2026

An agile team is having difficulties in obtaining the participation of a true user to be a part of their team. In the absence of a true user, the development manager steps in to act as a proxy for the user...

In this situation, the agile team is facing a challenge: they do not have direct access to a true user, and a development manager is acting as a proxy. While having a true user on the team is ideal, the team can still work to improve value delivery by making strategic adjustments. Let's analyze the options based on key factors such as the need for user feedback, collaboration, and the potential impact on value delivery. Key Factors to Consider: - User-Centric Feedback: One of the core principles of agile is frequent feedback from the end user to ensure that the team is building what is truly valuable. A proxy, even a knowledgeable one, may not have the same insights as the actual user. - Team Collaboration and Roles: Agile teams are cross-functional, and collaboration between different roles is crucial for delivering value. While technical expertise is important, it's essential to keep the team aligned with user needs. - Iteration and Adaptability: Agile iterations should be of a length that allows for continuous feedback and adaptation. The team needs to be able to adjust based on insights and real-time feedback, especially in the absence of direct user involvement. Option A: Improve the velocity of each iteration - Why rejected: Improving velocity might lead to more work getting done faster, but it does not address the key problem: the lack of user feedback. Without understanding user needs, improving velocity risks producing work that is not valuable or aligned with the user’s requirements. - Reasoning: While velocity can help the team increase throughput, it does not directly improve value delivery. In the absence of a true user, the team needs to focus on obtaining relevant feedback from other sources, not just speeding up their work. Option B: Add a variety of skilled programmers and expert testers to the team - Why rejected: While having skilled programmers and testers is important, this does not address the core issue: the absence of a true user to provide feedback on the value being delivered. Technical skills alone will not solve the problem of ensuring that...

Author: Daniel · Last updated Jul 9, 2026

A project has several features that will deliver immediate customer value. The product owner needs to determine which features to include in the upcoming iteration....

In this scenario, the product owner needs to determine which features to include in the upcoming iteration. The key goal is to ensure that the customer is aligned with the priorities that will deliver immediate value to them. To make an informed decision, the product owner must consider the customer's needs and preferences, while balancing technical feasibility and business value. Let's evaluate each option based on this context: Key factors to consider: - Customer Value: The primary goal is to deliver features that provide immediate value to the customer, which requires clear prioritization based on customer needs. - Clarity and Focus: The product owner needs a clear understanding of which features are most important to the customer to ensure that development focuses on the highest-value items first. - Customer Collaboration: The product owner should engage the customer in a way that helps make informed decisions without overwhelming them with excessive detail or technicalities. Option A: Work Breakdown Structure (WBS) - Why rejected: A WBS is a detailed breakdown of the work required to complete a project or feature, including tasks and sub-tasks. While this is useful for project management and execution, it doesn’t help the product owner prioritize features from the customer’s perspective. The WBS is too granular and doesn’t provide the customer with a clear view of the overall value or priorities. - Reasoning: The WBS is focused on the tasks and technical steps involved in delivering features, not the features themselves or their value to the customer. Therefore, it's not helpful for prioritizing features based on customer needs and immediate value. Option B: Description of all features' functions and an estimate of their cost - Why rejected: While this provides some useful information about what the features do and their cost, it may not be the most efficient or customer-centric way to make decisions. The customer is more concerned with which features provide the most immediate value, not just the functionality and cost breakdown. This could overwhelm the customer with too many details. - Reasoni...

Author: Olivia Johnson · Last updated Jul 9, 2026

An agile coach is working with a team that serves clients making product requests by phone. During a daily commitment and replanning meeting, a team member states that they were unable to resolve a client re...

In this scenario, the key issue is that the team member was unable to resolve a client request due to a lack of sufficient product knowledge. This could potentially hinder both the team's ability to meet client needs and the team's overall performance. Therefore, the agile coach should take an approach that encourages team collaboration, knowledge sharing, and self-sufficiency within the team. Option A: Facilitate a team discussion to identify knowledge gaps and determine the best way to address them. - Reasoning: This option fosters collaboration and collective problem-solving. By involving the team in identifying knowledge gaps, the coach helps ensure that the team can work together to come up with solutions that are sustainable. It also helps prevent the knowledge siloing and dependency on a single person for product knowledge. The team will likely have insights into how to share knowledge effectively (e.g., through pair work, documentation, or mentoring). - Why it's the best option: Agile emphasizes collaboration, self-organizing teams, and continuous improvement. This approach encourages the team to take ownership of the issue, and it might help identify systemic issues (such as a lack of documentation or knowledge transfer practices) that need to be addressed in the long term. Option B: Ask the line manager to assign the team member with the required technical knowledge. - Reasoning: While this option may seem efficient, it doesn't fully align with the agile principles of self-management and collective ownership. By relying on a line manager to assign knowledge, the team may continue to depend on external interventions instead of improving internal processes. Additionally, it doesn't address the root cause of the knowledge gap within the team. - Why it's rejected: The agile mindset promotes knowledge sharing and team empowerment. Relying on a line manager to resolve the issue takes away from the team’s responsibility to support each ...

Author: NightmareDragon2025 · Last updated Jul 9, 2026

During the advanced stages of implementing a complex design, an agile practitioner realizes that the architecture is not scalable for user requirements. The architect suggests a workaround that is minimally ...

In this situation, the key concern is that the architecture is not scalable enough for user requirements, and the architect has suggested a workaround that is minimally adequate but may result in performance issues. The agile practitioner needs to balance short-term and long-term needs while adhering to agile principles of flexibility, collaboration, and delivering high-quality, sustainable solutions. Option A: Tell the team that this is unacceptable for the upcoming project. - Reasoning: While it is important to ensure that the architecture is scalable, simply rejecting the workaround may create unnecessary conflict or delay the project. Agile practices encourage adaptability and finding solutions collaboratively. Rejecting it outright may not allow for a deeper investigation into potential solutions or alternatives that could better meet user needs. - Why it's rejected: Agile methodology encourages flexibility and problem-solving. A rigid approach like outright rejection without further discussion or exploration doesn’t foster collaboration or ownership within the team. Option B: Implement the workaround since performance issues can be addressed in the next iteration. - Reasoning: Implementing a workaround may seem like a quick fix, but in the long term, it may introduce technical debt, which can cause more significant issues down the line. Ignoring performance issues in the current iteration can lead to challenges that will be harder to address later. It might also go against the principle of delivering high-quality solutions in each iteration. - Why it's rejected: While agile values delivering functional software quickly, it also stresses maintaining quality. Implementing a suboptimal solution that could harm performance is a short-term fix that may become a significant problem later, potentially leading to rework and performance bottlenecks. Option C: Calculate the cost of redoing the architecture and seek management appro...

Author: Ella · Last updated Jul 9, 2026

An executive notices a kanban board in a highly visible location and expresses concerns to the project manager that too many ...

In this scenario, the executive is concerned about the visibility of the kanban board. As a tool for improving transparency and workflow, the project manager needs to address the concern while maintaining the value of the kanban board for the team. The response should reflect both the value of agile principles (such as transparency, collaboration, and visibility) and the need to respect the executive’s concerns. Option A: Cover up the kanban board every time the project team is not actively updating it. - Reasoning: Covering the board when it’s not in use would defeat the purpose of having a highly visible, accessible tool. The board is meant to maintain transparency at all times. Hiding it when not in use reduces its effectiveness and potentially sends the wrong message about openness or accountability. - Why it's rejected: This option goes against the agile principle of transparency. A kanban board is most valuable when it's easily visible and constantly reflects the team’s progress. Hiding it undermines its purpose and may create confusion or distrust about the team's processes. Option B: Demonstrate how the kanban board is necessary for assigning proper ownership for the work that has been done. - Reasoning: While it’s true that a kanban board helps with ownership and accountability, focusing solely on ownership might not directly address the executive’s concern. This response could be helpful in a broader conversation about the value of the board, but it doesn't fully address the concern about visibility. - Why it's rejected: While demonstrating ownership is important, this option focuses more on explaining internal processes rather than addressing the visibility concern. The executive’s concern is more about public visibility, and simply explaining ownership doesn’t fully address how the board serves the broader transparency and communication goals. Option C: Explain that the kanban board enables the team to complete the work and increases transparency on work that is not done. - R...

Author: Samuel · Last updated Jul 9, 2026

A new stakeholder has recently joined a project. During a meeting with the scrum master, the new stakeholder tries to understand the status of the project and the remaining task...

In this scenario, the new stakeholder is seeking an understanding of the project’s status and the remaining tasks for completion. The scrum master needs to provide this information in a way that is aligned with agile principles and ensures transparency and clarity without overwhelming the stakeholder with too much detail. Option A: Show the stakeholder the latest release breakdown for the project. - Reasoning: While the release breakdown may provide useful information about what has been delivered so far, it typically focuses more on high-level deliverables and milestones. It may not provide the detailed, up-to-date status of the ongoing work and the specific remaining tasks. - Why it's rejected: The release breakdown is useful for understanding high-level project progress but doesn’t fully reflect the current state of the work in progress or give insight into the specific tasks remaining for completion, which is what the stakeholder is asking for. It lacks the real-time visibility that the stakeholder needs. Option B: Invite the stakeholder to attend the next sprint review meeting. - Reasoning: The sprint review meeting is a great opportunity for stakeholders to see the work completed in the current sprint, provide feedback, and understand how the product is evolving. However, this meeting focuses primarily on the completed work from the current sprint, not necessarily on the remaining tasks or the overall project status. - Why it's rejected: Although useful, the sprint review might not be the best way to answer the stakeholder’s immediate question about remaining tasks. The focus is more on what has been done rather than what is left to do or the current state of the project. Inviting the stakeholder to this meeting might be premature if the question is specifically about remaining tasks. Option C: Show the stakeholder the progress radiators for the project. - Reasoning: Progress radiators are visual tools (e.g., task boards, burndown charts, kanban boards) that provide ...

Author: FrostFalcon88 · Last updated Jul 9, 2026

A project team developer has been involved in a large corporate initiative that has negatively impacted team productivity on another project to which they have...

In this scenario, the developer is working on two different projects, and one large corporate initiative has started to negatively impact their productivity on another project. The goal for the developer should be to manage their commitments in a way that balances both projects and aligns with the team's goals, while also maintaining transparency and communication about their capacity. Option A: Worked as planned to meet the team's commitments and participated in other events as time permitted. - Reasoning: This option implies that the developer continued with their tasks without reassessing their capacity. While the intention to meet commitments is admirable, this could be counterproductive. If the developer is spreading themselves too thin, it might result in diminishing returns in terms of quality or team morale. Additionally, if their work on the corporate initiative is impacting productivity, this approach might lead to frustration or burnout. - Why it's rejected: Continuing without adjusting the workload could lead to poor outcomes, and failure to communicate the impact of this initiative on the team's productivity could undermine the success of the project. Agile teams thrive on transparency and collaboration to adapt to challenges, and simply "working as planned" without reassessment isn't aligned with these principles. Option B: Worked extensively on the corporate initiative in order to inform the team of that effort. - Reasoning: Working extensively on the corporate initiative is a form of prioritization, but this option could jeopardize the developer's contributions to the current team’s project. Focusing on one initiative at the cost of the other project may worsen the productivity issue. Furthermore, informing the team about the effort after the fact doesn't solve the issue in real-time. - Why it's rejected: Prioritizing one initiative over the team’s project without aligning with the team’s needs and goals isn’t the best approach. The developer should aim for a balance between the two initiatives, not let one interfere with the other. Simply informing the team without addressing the problem directly doesn’t solve the underlying issue of declining team productivity. Option C: Asked to be relieved of project tasks to maintain team velocity. - Reasoning: This option demonstrates awareness of the problem and suggests a proactive solution...

Author: Vivaan · Last updated Jul 9, 2026

Part way through a project, several team members are in conflict over whether or not a deliverable has been properly comple...

In this scenario, the issue at hand is that several team members are in conflict over whether a deliverable has been properly completed. The agile leader needs to address this conflict in a way that ensures alignment on what "done" means and reduces ambiguity moving forward. The solution should focus on clarifying expectations and fostering collaboration within the team. Option A: Facilitate team agreement on the definition of done (DoD) during the chartering process. - Reasoning: The Definition of Done (DoD) is a key component in any agile project, as it provides a clear and shared understanding of what constitutes a completed deliverable. When conflicts arise over whether a deliverable is finished, it often means the DoD has not been sufficiently defined or agreed upon. By facilitating a team-wide agreement on the DoD during the chartering process (or at the beginning of the project), the team sets expectations from the start. This ensures everyone understands what needs to be accomplished for a task to be considered complete, thus reducing future conflicts. - Why it’s the best option: The DoD is foundational in resolving disputes about whether a deliverable is complete. By addressing this proactively during the chartering process, the agile leader can ensure clarity on completion criteria, which will prevent misunderstandings or conflicts later. It helps the team align on quality standards, testing requirements, and other conditions for completion that might otherwise lead to confusion. Option B: Motivate the team during Tuckman's "storming" phase. - Reasoning: Tuckman’s model of team development includes stages such as forming, storming, norming, and performing. The storming phase is characterized by conflict as team members adjust to different working styles and roles. While motivating the team through this phase can help resolve some interpersonal conflicts, it doesn’t directly address the root cause of the disagreement—ambiguity around the Definition of Done. - Why it's rejected: Motivating the team during the storming phase might ease some interpersonal tensions, but it does not address the underlying issue regarding what constitutes a “done” deliverable. Without clarifying the DoD, the team may continue to experience similar conflic...

Author: Nia · Last updated Jul 9, 2026

Project stakeholders are finding it difficult to know the real-time status of who has been assigned to various stories and the status of each work i...

In this scenario, the project stakeholders are struggling to get real-time visibility into the status of assigned work items and the overall progress of stories. The solution should focus on improving transparency and real-time updates in a way that aligns with agile principles. Option A: Use an information radiator to help increase the transparency of work for key stakeholders. - Reasoning: An information radiator (e.g., a task board, kanban board, or burndown chart) is a tool designed to provide visual, real-time transparency into the status of the work, who is working on what, and the overall progress of the project. It allows stakeholders to quickly assess the status of the project without needing to request updates. This is a central tenet of agile practices, which emphasize transparency and collaboration. It encourages visibility at all times and supports proactive decision-making. - Why it's the best option: Information radiators are highly effective in giving stakeholders quick access to real-time information. It aligns with agile principles of transparency and continuous feedback, allowing stakeholders to monitor progress independently. This reduces the need for constant communication and status updates, saving time for both the team and stakeholders. Option B: Send status updates whenever the stakeholders request them. - Reasoning: Sending status updates on demand can be labor-intensive for the project manager and may lead to delays in providing information. It creates a reactive rather than proactive system of communication. Additionally, stakeholders may not always know when they need an update, and the process of waiting for and responding to requests could lead to inefficiencies. - Why it's rejected: While this option might help stakeholders in the short term, it creates a dependency on the project manager to continuously respond to requests. It also increases the overhead and may lead to bottlenecks in communication. It doesn't foster a self-sufficient or transparent workflow, which is more effective in agile environments. Option C: Hold Scrum meetings more frequently to ensure stakeholders are well informed. - Reasoning: Scrum meetings, such as daily stand-ups and sprint reviews, are designed to ensure the team is ...

Author: Olivia Johnson · Last updated Jul 9, 2026

A team member has made a mistake on a project. How should the scrum master address the mistake?

When a team member makes a mistake, the Scrum Master’s role is to address the issue in a constructive way that fosters learning, growth, and continuous improvement. The response should be rooted in agile principles such as collaboration, transparency, and continuous improvement. The goal is not just to address the mistake but to prevent it from happening again while improving the overall team's performance. Option A: Encourage all team members to follow existing processes. - Reasoning: Encouraging the team to follow existing processes is important for maintaining consistency and quality. However, this response does not directly address the mistake itself or offer a solution for improvement. It assumes that the process is already perfect and does not account for the fact that the mistake may have happened due to a flaw in the process itself, unclear communication, or other external factors. - Why it's rejected: While reinforcing processes is important, it doesn’t provide an opportunity for reflection and learning from the mistake. It focuses on compliance rather than on understanding the root cause of the error. Agile teams are encouraged to continuously inspect and adapt processes, so merely encouraging adherence to them without fostering discussion of the issue might lead to missed opportunities for improvement. Option B: Require team members to complete a peer review of work and deliverables. - Reasoning: A peer review process can help reduce errors by involving others in checking the work before it’s finalized. However, requiring a peer review as a response to one mistake could create a punitive atmosphere. It may shift the focus to the process rather than addressing the underlying reasons why the mistake occurred. Furthermore, peer reviews should be proactive in nature, not reactive to individual mistakes. - Why it's rejected: While peer reviews are valuable for preventing mistakes, requiring them in response to a specific mistake doesn't foster a culture of learning. The team member’s mistake could be a learning opportunity rather than a signal to impose additional layers of scrutiny. Over-reliance on peer reviews might also hinder individual responsibility and collaborative problem-solving. Option C: Facilitate a retrospective to identi...

Author: Julian · Last updated Jul 9, 2026

For what is the MoSCoW method used?

The MoSCoW method is a popular prioritization technique used primarily in project management, particularly in Agile environments. It helps teams prioritize tasks or features based on their importance and urgency. The acronym MoSCoW stands for: - Must have - Should have - Could have - Won't have (this time) Key Factors in Reasoning: 1. Estimating Story Size: The MoSCoW method does not focus on the estimation of effort or size. Estimation typically involves methods like Planning Poker or T-shirt sizing. MoSCoW is more concerned with prioritization than estimation. 2. Prioritizing Stories: MoSCoW is specifically designed for prioritizing requirements or user stories. It helps in determining which tasks are absolutely critical ("Must have"), which ones are desirable but not urgent ("Should have"), which are nice to have ("Could have"), and which are not n...

Author: Olivia · Last updated Jul 9, 2026

An agile team has started to worry because lately they have seen an increase in the number of issues. There seems to be a large variance in the quality of the work items delivered. The team now realizes that a sh...

In this scenario, the team is facing issues with increasing defects and a lack of consistency in the quality of work. The core problem seems to be a shared understanding of quality among team members, which needs to be addressed. Let’s break down the options: Key Factors in Reasoning: 1. A) The team should move to test-driven development as defects are not being detected during testing: - While Test-Driven Development (TDD) is a valuable practice, moving to TDD in response to quality issues might not be the best immediate solution. TDD focuses on writing tests before code, but the issue here seems to be a lack of shared understanding about quality, not necessarily a deficiency in testing. It could be beneficial long-term, but it doesn’t directly address the root cause of inconsistent quality right now. 2. B) The team should account for the increased problems in their velocity forecasts since unexpected changes occur in agile projects: - Accounting for problems in velocity is an important practice, but this solution doesn't solve the core issue of quality inconsistency. Velocity might change due to various factors, but it’s more of an outcome rather than addressing the underlying definition of quality that is causing the variance. Focusing only on velocity would miss the need for clearer quality criteria. 3. C) The team should discuss their definition of done (DoD) and make changes to ensure t...

Author: Aditya · Last updated Jul 9, 2026

One of the senior stakeholders on a project did not want to be engaged on a daily basis. During the iteration, the team encounters complexities but are convinced these issues ca...

Key Factors in Reasoning: In this scenario, the team faces complexities but believes these can be resolved before the demo. However, there is a senior stakeholder who does not wish to be engaged on a daily basis. The agile practitioner needs to decide whether to raise the issues and how to engage with the stakeholders. Let’s evaluate the options: 1. A) Be transparent with all the stakeholders and make them aware of the issues encountered and the current project's status: - Transparency is one of the core values of Agile. Being open and honest about issues, even if they seem solvable, ensures that stakeholders are aware of potential risks and the project’s true status. It helps manage expectations and fosters trust. This option aligns with the Agile principle of early and continuous communication and encourages proactive problem-solving with stakeholders, especially if issues persist. 2. B) Ensure the agile leader documents a risk in the risk register and communicates the risk to the project sponsor: - While risk management is important, the agile framework typically encourages collaborative decision-making rather than top-down risk management. Documenting risks in the risk register is a more formalized approach often associated with waterfall or traditional project management methods. Agile values adaptability and communication more than rigid documentation processes. Also, in this case, the team believes they can resolve the issues, so this might not be necessary yet. 3. C) Support the team's decision, and since the team is confident about being able ...

Author: Kai · Last updated Jul 9, 2026

While planning, what prioritization factors need to be considered for a minimally marketable feature...

When planning for a Minimally Marketable Feature (MMF), the goal is to deliver the smallest piece of functionality that provides value to the market and customers. The MMF should be valuable, feasible, and capable of generating feedback for further development. Here’s a breakdown of the options: Key Factors in Reasoning: 1. A) How much risk is needed to develop an MMF: - Risk is an important factor in any project, but when prioritizing an MMF, the primary focus is on delivering value quickly, not just managing risk. Risk management is part of the process, but the MMF should aim to minimize complexity and risk while delivering a feature that is valuable to the customer. High-risk features could delay time-to-market and increase uncertainty, so risk alone shouldn't be the determining factor for prioritizing MMF. 2. B) How much money the organization will earn or save by having the MMF: - Value is at the core of the MMF. The feature should provide tangible value to the customer or business. The return on investment (ROI) is a critical consideration for prioritization. Features that bring in revenue or reduce costs should be prioritized to maximize the value delivered to the organization. This factor directly aligns with the goal of creating an MMF that offers measurable benefits and aligns with business objectives. The MMF should be prioritized based on business value, ensuring it brings a positive financial impact or operational ...

Author: Lina Zhang · Last updated Jul 9, 2026

A newly formed, colocated team is participating in daily standups, but is otherwise working largely as individual contributors. This has resulted in misalignment of activitie...

Analysis of Each Option: A) Plan activities that will require the team to work collaboratively on a regular basis. - Key Factor: One of the central tenets of Agile is collaboration. Even though planned velocity is being met, a team that works largely as individual contributors is not optimizing its potential for innovation, problem-solving, and learning. The purpose of a team is to leverage the diversity of skills, knowledge, and perspectives that individuals bring, which requires collaboration. - Why Selected: This option directly addresses the core issue — the lack of collaboration. Creating opportunities for collaboration will improve team dynamics, ensure better communication, and foster a shared understanding of the work. It's especially effective for a newly formed team where trust and understanding need to be built. These activities can be in the form of pair programming, joint problem-solving sessions, design workshops, or cross-functional work tasks. B) Set collaboration metrics and evaluate individuals against those metrics. - Key Factor: While it's tempting to quantify collaboration, setting individual metrics for collaboration can undermine the team spirit. Agile focuses on collective accountability, not individual performance. This could lead to unhealthy competition or force behaviors that aren't genuinely collaborative, as individuals may focus on "looking" collaborative for metrics instead of engaging organically. - Why Rejected: This approach risks driving unhealthy behaviors and undermines the principle of collective responsibility. Collaboration in Agile should be encouraged through the environment, culture, and activities, not by penalizing or rewarding individuals based on specific metrics. C) Re...

Author: James · Last updated Jul 9, 2026

An agile team is struggling with an issue. A team member mentions that another team had a similar issue that was resolved, but lessons learned docu...

Analysis of Each Option: A) Suggest that all agile teams share weekly reports on their projects. - Key Factor: Sharing weekly reports might sound like a good way to communicate what’s happening across teams, but it is not a targeted solution to the knowledge-sharing issue at hand. Weekly reports are often high-level and can lack the depth needed to convey meaningful lessons learned. Additionally, without a clear structure or system for capturing and sharing knowledge, this might just result in more documentation that isn't useful. - Why Rejected: Weekly reports can easily become bureaucratic and fail to focus on real, actionable insights. It would also overwhelm teams with reporting requirements without necessarily improving the exchange of knowledge on problem-solving or lessons learned. B) Encourage the team to independently find a solution. - Key Factor: While autonomy is a core Agile principle, the issue here is not just about finding a solution to the immediate problem but also about addressing a broader knowledge-sharing gap across teams. Encouraging the team to work in isolation might solve the immediate problem but could lead to a recurrence of similar issues due to lack of access to previously documented lessons learned. - Why Rejected: This option fails to address the systemic issue of knowledge sharing between teams and the broader organizational challenge of capturing and disseminating insights from previous experiences. It can result in teams solving the same problems multiple times, wasting time and energy. C) Work with the team to create a solution for disseminating team knowledge throughout the company. - Key Factor: This option focuses on solving the root problem — the lack of accessible knowledge and lessons learned from other teams. Working on a systematic solution for knowledge sharing can have a long-term positiv...

Author: Jack · Last updated Jul 9, 2026

Over the last two sprints, a number of potential problems have threatened the team's ability to hit the targeted re...

Analysis of Each Option: A) Deal with the issues in a retrospective if they ever come up again. - Key Factor: Retrospectives are meant to reflect on the past and continuously improve the team’s processes. However, waiting until issues come up again in future sprints may be too late to prevent them from threatening the release date. Retrospectives address the symptoms rather than actively monitoring or mitigating potential risks before they become problematic. - Why Rejected: This option is reactive rather than proactive. Issues that threaten a release date require attention as soon as they arise, not after the fact. By only addressing them in a retrospective, the team risks delaying the resolution and worsening the situation. B) Create a task board to track issues when they appear. - Key Factor: A task board is useful for tracking tasks, but it is typically more suited for day-to-day work, not specifically for tracking risks or issues that might affect the project timeline. It doesn't provide a focused view of potential risks or their potential impact on the release date. - Why Rejected: A task board alone isn’t structured to manage or track risks effectively. While it may help in visualizing issues as they arise, it lacks the context and depth needed to actively track, assess, and mitigate risks in a way that directly informs decisions around release planning. C) Identify and monitor issues through a risk burndown chart. - Key Factor: A risk burndown chart is a tool that specifically tracks the progress of risk mitigation over time. It helps visualize whether risks are being addressed and ...

Author: Liam · Last updated Jul 9, 2026

One of the overseas stakeholders on an agile project has not been actively involved in the project's development. What ...

Analysis of Each Option: A) Increase the frequency of emails and/or try to call the stakeholder. - Key Factor: Increasing the frequency of communication (emails or calls) could potentially result in the stakeholder feeling overwhelmed or burdened, especially if they haven't been actively engaged thus far. Without understanding the root cause of their disengagement, this may not be an effective solution. Over-communication can often lead to frustration or disengagement, especially if the stakeholder feels that the project is not aligned with their priorities or expectations. - Why Rejected: While increasing communication can sometimes help, this approach lacks understanding and does not address the deeper issue of why the stakeholder has been disengaged in the first place. It could potentially add pressure without solving the root cause. B) Remind the stakeholder of their obligation to engage in the project. - Key Factor: This approach focuses on reminding the stakeholder of their responsibilities. While it’s important to clarify roles and expectations, it can come across as confrontational or passive-aggressive if the stakeholder feels that their lack of engagement is due to other reasons (e.g., competing priorities, lack of clarity on value, etc.). Simply reminding someone of their obligation can potentially damage the relationship. - Why Rejected: While the stakeholder may have an obligation, this approach doesn't attempt to understand their needs or motivations. It’s more likely to lead to defensiveness or disengagement, especially if the stakeholder feels that they’ve not been properly supported or involved in a meaningful way. C) Talk to the stakeholder's superior so they can offer coaching and guidance on project involvement. - Key Factor: Involving a superior might be seen as escalating the situation, which could backfire. This could cr...

Author: Olivia · Last updated Jul 9, 2026

The customer asked the IT project manager to change a few specifications for the software being developed, which will affect the project budget. The financial sponsor is having difficulty approving changes to the b...

Analysis of Each Option: A) Explain that agile principles mandate that there should be a contingency budget for agile projects. - Key Factor: While it’s true that Agile projects often involve flexibility and the potential for scope changes, it’s not a standard mandate that projects should always have a contingency budget. Contingency budgeting is a best practice in project management, but it depends on how the project was originally structured and agreed upon. Simply invoking Agile principles may not be sufficient to address the specific concern about budget approval, especially if the financial sponsor is hesitant about change. - Why Rejected: This approach does not directly solve the problem of getting the sponsor to approve the necessary changes to the budget. Additionally, stakeholders may not fully align with the Agile principle in this context if the budget has already been set in a more traditional, fixed-cost framework. B) Request the team work overtime to get the work done on time and within the allocated budget. - Key Factor: While overtime might be a short-term solution, it can lead to burnout, decreased productivity, and quality issues. It may also affect team morale and doesn’t solve the root problem — which is the need to adjust the budget to account for changes. Moreover, overtime can result in increased costs, which would only escalate the financial issue. - Why Rejected: Overtime is typically a poor long-term strategy, especially in Agile. The goal should be to re-negotiate the project scope, timeline, or budget to ensure the project can be completed successfully without negatively impacting team well-being or project quality. C) Encourage the product owner and team to analyze the impact of the changes and prioritize the backlog. - Key Factor: This option directly addresses the core of Agile project management, which is to continuously re-evaluate and prioritize based on new inputs. Encouraging the product owner and the team to analyze the impact of the changes allows them to assess the scope of ...

Author: Lucas Carter · Last updated Jul 9, 2026

What should a scrum master do when an agile team member is behind on their tasks?

When a Scrum team member is behind on their tasks, the Scrum Master’s role is to facilitate and support the team in identifying the root cause of the delay and help them improve their performance without creating additional pressure. Here’s an analysis of each option: A) Ask the team for suggestions - Reasoning: Asking the team for suggestions can be a valuable approach, as it fosters a collaborative and supportive environment. The team may have insights into how to solve the problem or provide ideas on how to help the struggling team member. However, this might not be the most immediate or focused solution. It may take time to gather suggestions, and depending on the urgency of the delay, it might not be effective in getting the team member back on track quickly. - Use case: This can be effective when the team culture encourages open discussion and problem-solving, and the delay isn't critical to the sprint's success. - Why rejected: It’s too indirect for an immediate intervention and may not address the root cause quickly enough. B) Move the tasks to another team member who has spare capacity in the sprint - Reasoning: Moving tasks around is often seen as a reactive measure to “cover” for someone who's falling behind. It can work in situations where the team member is struggling but the sprint’s delivery depends on completing certain tasks. However, this is not a sustainable solution in the long term and might create tension in the team if it becomes a regular approach. It can also lead to burnout or stress for the team member picking up the additional workload. - Use case: This can be used when it is critical to meet the sprint goal and the team member has a legitimate reason (e.g., personal issues, illness) for falling behind, and the delay is not caused by their inability to perform. - Why rejected: It doesn't solve the root cause of the issue and risks overloading another team member. C) Hold a one-on-one meeting to encourage the team member to meet task commitments - Reasoning: Holding a one-on-one meetin...

Author: James · Last updated Jul 9, 2026

In a scrum team, who should be responsible for the budget and release plans?

In a Scrum team, the responsibility for the budget and release plans should be carefully aligned with the roles and accountability structure within the framework. Let’s break down each option: A) The Scrum Master assigns someone on the team to handle the budget, and the Product Owner is responsible for release plans - Reasoning: This approach implies that the Scrum Master delegates responsibility for budget management to someone else on the team. While the Scrum Master is a facilitator and coach, they do not have the authority to assign specific roles within the team beyond guiding processes and helping the team become self-organizing. Additionally, the budget often requires broader organizational context, which the Scrum Master may not have visibility into. - Use case: This could be used if the Scrum team is not yet self-organized and needs external structure, but it does not align with Scrum principles of autonomy. - Why rejected: It goes against the Scrum principle of self-organization and the Scrum Master's role. The Scrum Master doesn't have the authority to assign responsibility for things like budgets. B) The finance department is responsible for the budget, and the Product Owner is responsible for release plans - Reasoning: While it is realistic that the finance department manages the broader budget in an organization, this solution overlooks the collaborative, adaptive nature of Scrum. The Scrum team, especially the Product Owner, needs to have input into budget decisions to ensure that they are able to deliver what is most valuable to the customer. Moreover, if the finance department makes all budget decisions without consulting the team, it could lead to misalignment between the project’s actual needs and financial constraints. - Use case: This might be useful in very large organizations where there are strict financial controls, but it's not a perfect fit for agile principles of flexibility and team accountability. - Why rejected: It doesn’t promote shared responsibility or adaptability within the Scrum team, and it separates the Product Owner from financial decisions that may impact release priorities. C) The Scrum team as a whole, as they are self-organizing and share accountability - Reasoning: The Scrum team, as a self-organizing entity, should take collective responsibility for delivering on commitments, including the budget and release plans. However, it is important to note t...

Author: FrozenWolf2022 · Last updated Jul 9, 2026

A new agile team is forming to address a high-priority project. Team members are dispersed over a wide geographic area. The scrum master and the team are currently defining their working...

When forming a working agreement for a dispersed agile team, there are several key factors to consider, such as communication, collaboration, and maintaining engagement despite geographic separation. Let's break down each option: A) Identify support needed from external vendors to assist dispersed team members - Reasoning: While identifying external support can be useful for specific tools, resources, or infrastructure, it isn't directly related to the internal workings or communication of a dispersed agile team. The working agreement should focus more on how the team can collaborate effectively in the absence of physical proximity, rather than on external vendors. - Use case: This could be useful in cases where the team needs specific technical support from vendors, but it doesn’t address the core challenges of dispersed team communication, coordination, or trust-building. - Why rejected: It’s not directly relevant to the immediate internal challenges of an agile team working across different locations. The team's primary focus should be on communication and process. B) Meet face to face at regular intervals to enhance shared understanding - Reasoning: Regular face-to-face meetings are often considered one of the most effective ways to enhance communication, trust, and shared understanding among team members. However, for dispersed teams, this may not always be feasible due to geographic constraints. While periodic face-to-face meetings (e.g., during sprints or at important milestones) can be beneficial, they should not be the primary strategy for working agreements in dispersed teams. - Use case: This is useful for teams that can manage occasional in-person meetings, but not a scalable solution for fully dispersed teams or when working with global teams. - Why rejected: It may not be realistic for dispersed teams that cannot meet physically on a regular basis. The team needs to focus on building remote communication strategies. C) Designate one person to communicate with all team members working at different locations - Reasoning: Designating one person to communicate with all team members might create a single point of failure. In an agile team, the communication should ideally be transparent and decentralized, with all members in...

Author: Akash · Last updated Jul 9, 2026

A team is building a product in three-week iterations. During the last retrospective, it was identified that there was a 20 percent increase from previous iterations in the number of reported defects and change r...

When a team notices a significant increase in defects and change requests during the retrospective, it indicates that there are issues affecting the quality of the product and its value. The team needs to address the root causes of these defects and take corrective actions to improve product quality and delivery. Let’s evaluate each option: A) Reevaluate the duration of the cycles, as faster cycles may allow for earlier detection of defects - Reasoning: While shortening cycles can allow for faster feedback and earlier detection of defects, it’s not guaranteed that faster cycles will solve the underlying issue of increasing defects. In fact, a faster cycle might put more pressure on the team and reduce the quality of testing and validation processes, potentially leading to even more defects. This could exacerbate the problem, especially if the root cause is related to the quality of the development or testing practices rather than the speed of iterations. - Use case: This could be used in scenarios where the team is very slow to iterate and feedback loops are too long. However, this is not the primary solution to quality issues resulting in defects. - Why rejected: The problem seems to be related to quality or process rather than the duration of the iteration. Simply increasing iteration speed may not help with defect prevention or detection. B) Run a sprint to clear all reported defects before taking new stories - Reasoning: While it’s important to address defects, running an entire sprint dedicated solely to clearing defects may not be an ideal solution. A dedicated sprint for defect resolution can delay the progress of new features and may not tackle the root cause of the defect increase, which could be related to development practices, lack of testing, or unclear requirements. Additionally, focusing entirely on defects might overlook important improvements to the overall development process. - Use case: This could be useful when defects are blocking further progress or if there's a backlog of critical defects that need to be addressed urgently. However, it doesn't necessarily improve the overall development quality. - Why rejected: This approach focuses only on clearing existing defects rather than improving the overall process to prevent defects in the future. It also delays new feature development, which may not align with business goals. C) Change the control mechanism so that items are better tested before delivery - Reasoning: This is one of the most effectiv...

Author: Samuel · Last updated Jul 9, 2026

A team member has asked a question about the responsibilities of the product manager, QA, and the team regarding qua...

When discussing responsibility for quality in an agile team, it's essential to understand how roles and accountability work within the context of Agile principles. Let's evaluate each option: A) The entire team is responsible for quality and each team member is accountable for ensuring the success of every component - Reasoning: While it’s true that the entire team is responsible for quality in Agile, this option oversimplifies the situation. In Agile, each team member contributes to quality, but the responsibility for "ensuring the success of every component" may be too broad and unrealistic. Not every team member will be directly involved with every component at the same depth. For example, developers might focus on coding quality, while QA focuses on testing, and the Product Owner focuses on ensuring that the features align with customer value. The team works together, but the way they contribute to quality might differ. - Use case: This could be used in a scenario where the team has a very collaborative mindset and wants to emphasize shared responsibility. However, it's a bit too generic in addressing specific roles and accountability. - Why rejected: This doesn’t account for role-specific responsibilities, which are important in Agile. The concept of “ensuring the success of every component” isn't practical and may lead to confusion about who is responsible for what. B) The entire team is responsible for quality, but each team member's role may vary as stated in the definition of done (DoD) - Reasoning: This is a well-aligned approach with Agile principles. In Agile, quality is everyone’s responsibility, but each person has a specific role in ensuring that quality is maintained, and the Definition of Done (DoD) helps clarify those roles. For example, the developer ensures code quality, the QA team ensures that tests are thorough, and the Product Owner ensures that the product meets business requirements. The DoD can define when a feature is considered "done," ensuring that each role's contribution to quality is clear. - Use case: This works well when the team has a strong DoD, and each role is clearly defined. It aligns with the idea that while everyone is responsible for quality, how they contribute varies by role and the specifics of the product. - Why rejected: This option should not be rejected. It reflects Agile best practices and clearly distinguishes between shared and individual responsibilities. C) The entire team is responsible for quality and QA is respo...

Author: FrozenWolf2022 · Last updated Jul 9, 2026

A project's product owner asks the scrum master to facilitate the estimation activity. The scrum master then meets with the team and the product owner to clarify the user stories. Following the meeting, the team ...

The technique the team used is Planning Poker. Let me break down the reasoning behind this: Key Factors in the Scenario: - Product Owner's Involvement: The product owner was present to clarify user stories. This is typical in Planning Poker because the team needs to understand the stories in detail, which the product owner usually helps with. - Individual Estimates: The team provides individual estimates. Planning Poker is well-suited for this as it allows each team member to make an independent estimation, promoting a diverse set of views on the effort. - Estimates are provided individually before discussion: In Planning Poker, each participant selects their estimate in isolation, often using cards with Fibonacci numbers (e.g., 1, 2, 3, 5, 8, 13). Once everyone has chosen, the team discusses differences. Explanation of Why Other Options Are Rejected: 1. A) Lessons Learned: - This technique involves reflecting on past projects or experiences to gather insights. It’s more of a retrospective or learning session, not a method for estimating the effort of user stories. - Rejection Reason: There’s no reflection or learning from past work in this scenario; the activity is focused on estimating the current user stories. 2. B) Wideband Delphi: - This is a more formalized estimation process where experts provide their individual estimates and reasons. The facilitator collects these estimates, discusses discrepancies, and refines them over several rounds. Th...

Author: FlamePhoenix2025 · Last updated Jul 9, 2026

After some iterations, the agile practitioner observes that the team is self-organizing in small knowledge silos. Which a...

The correct action in this situation would be D) Advise the team of the risks and invite them to change. Explanation: In agile teams, self-organization is encouraged, but it’s also important to ensure the team remains collaborative and cross-functional. Small knowledge silos indicate a potential risk to effective communication, collaboration, and overall team performance. Key Factors in the Scenario: - Self-organizing Teams: Agile teams are meant to self-organize, so directly forcing a solution (such as reorganizing or imposing rules) may go against the agile principles of autonomy and empowerment. - Knowledge Silos: Knowledge silos happen when individuals or subgroups accumulate expertise in a narrow area without sharing it across the team. This can lead to inefficiencies and create bottlenecks in the long run. Addressing this through dialogue and shared understanding is the most effective way to resolve the issue. - Collaboration and Empowerment: The team is still self-organizing, meaning they can be trusted to find their own solutions once they understand the issue and its risks. It’s essential to raise awareness and guide the team toward a more collaborative and cross-functional way of working. Why Other Options Are Rejected: 1. A) Raise the concern to upper management: - Raising concerns to upper management can be a reactive approach. It can be seen as undermining the team's autonomy and may not directly address the root cause of the problem. - Rejection Reason: This doesn’t empower the team to resolve the issue themselves. In agile, the focus is on continuous improvement from within the team, not necessarily escalating issues to management. 2. B) Establish rules for the team to avoid this situation: - While setting clear expectations or guidelines can be helpful, simply...

Author: Manish · Last updated Jul 9, 2026

In a project, the customer asks for a requirement that clearly deviates from the contract terms. How...

The correct action is B) Discuss the value of the change for the project with the customer. Explanation: The customer is requesting a change that deviates from the agreed-upon contract terms. This situation requires open communication and understanding between the contractor and the customer to evaluate the change's impact. The primary goal is to assess the value of the requested change and decide collaboratively whether it should be incorporated into the project. This approach aligns with agile principles of adaptability and customer collaboration. Key Factors in the Scenario: - Customer Requesting Change: The customer is introducing a requirement that doesn’t align with the existing contract terms, which is a common situation in dynamic project environments. - Flexibility and Collaboration: Instead of rigidly sticking to the contract, it's important to engage the customer to understand the necessity and value of the change. This helps in making an informed decision and potentially negotiating an amendment to the contract if the change is worthwhile. - Impact of Change: Discussing the value of the change allows the contractor and customer to evaluate the business impact, time, cost, and any other constraints together. Why Other Options Are Rejected: 1. A) Proceed with the work only after the contract is amended: - This option is too rigid and could delay the project unnecessarily. Instead of automatically requiring a contract amendment before proceeding, it’s better to have a discussion with the customer first to assess whether the change is valuable and worth pursuing. - Rejection Reason: This response doesn't foster collaboration or flexibility. It may cause unnecessary delays, especially if the change is small and doesn’t drastically affect the scope or contract terms. 2. C) Evaluate effort and impact and ask for steering committee and shareholder approval: - This option may be suitable for large-scale or complex projects, but it involves a formal and bureaucratic pro...

Author: VenomousSerpent42 · Last updated Jul 9, 2026

During team meetings, the team often struggles with making decisions about their technical approach. What should be done...

The best action to improve the quality and timeliness of decisions is A) Work with the team to improve collaboration by fostering group decision making and conflict resolution techniques. Explanation: The issue here is that the team struggles with decision-making during their technical discussions. Improving collaboration and fostering group decision-making can significantly enhance the team’s ability to make better, faster decisions. By actively working on conflict resolution techniques and improving communication, the team can navigate disagreements more effectively and reach consensus without delays. Key Factors in the Scenario: - Team Decision-Making Struggles: The team is having difficulty agreeing on technical approaches, which points to a lack of effective collaboration and decision-making processes. - Group Decision-Making: Encouraging team-wide collaboration allows the team to leverage diverse perspectives, improving the decision quality. It also ensures that everyone has a say, which promotes ownership and commitment to the final decision. - Conflict Resolution: Training the team in conflict resolution techniques helps them address disagreements constructively, reducing decision delays and improving teamwork. Why Other Options Are Rejected: 1. B) Promote team discussion but give the product owner the ultimate decision-making authority: - This approach centralizes decision-making with the product owner, which could undermine the team's autonomy and reduce the collaborative nature of agile teams. It might also make the team dependent on the product owner, leading to bottlenecks in decision-making. - Rejection Reason: While the product owner plays an important role in defining the product vision, technical decisions should generally be made by the development team to ensure they are grounded in feasibility and technical considerations. Giving the product owner ultimate authority may limit team engagement. 2. C) Assign individual team members as decision owners for each key decision to avoid conflict: - While assigning decision owners might seem like a way to streamline decisions, it can isolate team members and reduce collaboration. This could create a fragmente...

Author: Evelyn · Last updated Jul 9, 2026

In a planning meeting, the client does not have a clear understanding of the most beneficial features of a project, because there are too many stakeholders with diffe...

The most appropriate approach for the project manager is B) Suggest the product owner prioritize the work items by feature to maximize value. Explanation: In situations where there are many stakeholders with conflicting or unclear requirements, it’s crucial to prioritize the most valuable features to ensure that the project delivers the highest value first. By suggesting that the product owner prioritize the work items, the project manager ensures that the team focuses on the most important features for the client and stakeholders, providing clarity and direction. Key Factors in the Scenario: - Conflicting Requirements from Multiple Stakeholders: When there are many stakeholders, it’s common for requirements to vary widely. The product owner can help navigate this complexity by prioritizing features based on value, impact, and feasibility. - Maximizing Value: Agile projects focus on delivering value incrementally, and prioritizing features ensures that the most valuable features are delivered early in the project. - Product Owner's Role: The product owner is responsible for managing the product backlog and ensuring that the team works on the highest-priority features. This step will allow the product owner to bring focus to the project and make informed decisions. Why Other Options Are Rejected: 1. A) Define all requirements so value can be added by delivering a high-level plan at the initiation phase: - This option suggests attempting to define all requirements upfront, which is often impractical, especially when stakeholders have diverse and conflicting needs. In agile, it is generally better to prioritize and iteratively define requirements. - Rejection Reason: Defining all requirements upfront can lead to unnecessary delays and a lack of flexibility. Agile encourages evolving requirements and adaptive planning, not rigid upfront planning. 2. C) Ask the customer to define the requirements of all stakeholders and select the most valuable features: - While asking the customer to define requirements is important, this approach places the responsibility on the custome...

Author: GlowingTiger · Last updated Jul 9, 2026

Why is stakeholder engagement important for project success?

Stakeholder engagement is essential for project success because it fosters collaboration, aligns expectations, ensures effective communication, and helps address potential issues early. In the context of stakeholder engagement, each option addresses different aspects of project dynamics. Let's analyze the options and reasons for selecting the best one: A) To participate in establishing a shared vision as a member of the team Stakeholders, when engaged early and continuously, help shape the direction of the project by aligning their perspectives with the project’s goals. This collective vision guides the project’s strategy and ensures that everyone involved has a common understanding of the desired outcomes. This fosters collaboration and reduces the risk of misalignment later on. B) To provide the acceptance criteria for the delivered items While stakeholders may indeed define acceptance criteria, this is typically a more technical or formal activity carried out towards the end of the project, rather than an ongoing process. It is important but does not capture the broader essence of why stakeholder engagement is important for project success. Engagement is more than just agreeing on specific deliverables; it’s about maintaining an ongoing connection and alignment t...

Author: Stella · Last updated Jul 9, 2026

On a complex project with a large degree of uncertainty, the team's velocity is declining. Upon testing, it is discovered that many of the work items reported as complete are not meeting the stakeho...

When dealing with incomplete work, especially in a project with a high level of uncertainty, it's essential to address the root causes of the issue rather than just managing the symptoms. Let's analyze the options and determine the most appropriate course of action. A) Conduct a spike so that the team can focus on defect repair without the distraction of new work items A spike is typically a research or investigation task used to reduce uncertainty in a specific area of the project. While conducting a spike can help the team understand and resolve defects, it doesn't directly address the core problem of incomplete work due to unclear requirements or misunderstanding of expectations. This approach is more about gathering information, and while useful in certain scenarios, it does not directly improve the quality of work or alignment with stakeholder needs. B) Create a burndown chart to ensure the team understands the variance between the current and target velocity A burndown chart helps visualize progress toward completing work, tracking how many tasks are finished relative to the planned work. While this is a useful tool for tracking progress, it doesn’t directly address the underlying issues of incomplete work or quality concerns. It primarily reflects performance but doesn’t provide actionable insights into the cause of incomplete work or misaligned deliverables. In this case, the focus should be more on improving work quality and alignment with requirements rather than just tracking velocity. C) Work with the product owner to reduce the complexity of the work so that the team can improve quality Reducing the complexity of work may help alleviate some pressure on...

Author: Ethan Smith · Last updated Jul 9, 2026

What is the risk of using agile in a distributed team?

When working with distributed teams, Agile introduces several challenges due to the geographic separation, time zone differences, and communication barriers. Let's explore the potential risks of using Agile in such a context and assess each option based on how well it addresses the core risks. A) Frequent integration of work produced Frequent integration is a common practice in Agile to ensure that work is continuously validated and aligned with the overall project goals. While this is a crucial element in any Agile project, the risk of using Agile in a distributed team is not necessarily about the integration frequency itself, but rather the challenges in communication, synchronization, and visibility between geographically separated team members. In fact, frequent integration might be more difficult to manage in a distributed team, but it doesn’t address the specific risk of working remotely or with different time zones. B) Lack of shared knowledge of user stories In a distributed team, one of the major risks is that team members, especially those in different time zones, might not have the same understanding of user stories. This can happen because communication between members can be less frequent or unclear, leading to misinterpretation of requirements, incomplete user stories, or inconsistent work outputs. The lack of shared knowledge about user stories is a significant risk in Agile environments where collaboration and continuous feedback are crucial. If team members are not aligned on the user stories, this can lead to inefficiencies, rework, and incomplete or low-quality deliverables. C) Need for more...

Author: Leah · Last updated Jul 9, 2026

The team is aware that they will need to integrate a new component to their solution in the next few weeks. The team does not have any expe...

When facing the need to integrate a new component that the team lacks experience with, it’s critical to take a structured and proactive approach. The goal is to reduce uncertainty, build the necessary knowledge, and ensure a smooth integration. Let's analyze the options carefully. A) Ask for a team extension so that an engineer with the needed experience can be added to the team This option suggests adding someone with the required experience to the team. While this might be a viable solution, it has several downsides: - It delays the solution, as finding and onboarding an engineer with the required expertise can take time. - It may not be a long-term solution; even with an experienced engineer, the rest of the team might still lack understanding of the component. - The team’s ability to become self-sufficient with the new component might be compromised if they rely too much on an external engineer. Why this is rejected: Adding an external resource might help in the short term but doesn’t help the team develop the necessary knowledge and skills. It’s more of a temporary fix. B) Suggest that the product owner perform the initial investigation and present the outcome to the team This option puts the onus on the product owner, who typically focuses on prioritization, stakeholder management, and ensuring that business value is delivered. While the product owner can provide valuable insights, they may not have the technical expertise needed to perform an in-depth investigation into the new component. - The product owner is not the right person for a technical investigation, especially when unfamiliar technology is involved. - It could result in incomplete or incorrect findings if the product owner doesn't have the technical background. Why this is rejected: The product owner is not the best resource for investigating a new component in a technical environment. This approach could delay or misguide the team in making informed decisions. C) Request that the product owner include a spike in the next iteration's...

Author: Zara · Last updated Jul 9, 2026

A global organization is migrating its IT infrastructure from traditional, physical assets to cloud-based assets. Agile concepts are new to the organization because it currently uses a predictive approac...

When an organization is transitioning from a traditional, predictive approach to Agile, the key challenge is driving cultural change and ensuring alignment at all levels. The organization’s leaders, middle management, and employees all need to understand the value of Agile and how it will impact their work. Let’s evaluate each option in the context of driving this transformation. A) Develop and distribute a high-level summary of how Agile offers greater benefit than predictive to mid-level managers and let them decide if it should be distributed to lower-level workers This option starts by targeting mid-level managers, which is an important group for ensuring the transition is smooth, as they play a critical role in implementing strategy and communicating it down the chain. However, leaving the decision of whether or not to distribute the summary to lower-level workers to mid-level managers could lead to inconsistent communication across the organization. It also skips the need for direct executive involvement, which is crucial for a successful transformation, as executives set the tone and ensure resources are aligned to support Agile adoption. Why this is rejected: This option risks creating fragmented communication and may not fully leverage executive support, which is essential for organizational-wide change. B) Develop and distribute a high-level summary of competing vendors' product alignment and agile project execution to the product owner for approval This option focuses on the product owner and vendor alignment but doesn’t address the broader goal of facilitating a cultural shift towards Agile. The product owner may have a deep understanding of Agile at the project level, but this summary is too narrow and specific. It also doesn't directly engage the organization's leadership or key stakeholders in driving the change. Why this is rejected: This approach is too narrow and specific, and it doesn't tackle the cultural change needed across the organization. It focuses on tactical aspects of Agile rather than the broader adoption. C) Develop and distribute a high-level summary of how Agile offers greater benefits than predictive to all members of the organization This option ...

Author: Oliver · Last updated Jul 9, 2026

Which statement describes the purpose of a burndown chart?

Explanation: A burndown chart is primarily used to visually track the progress of a project over time, typically focusing on work completion and how much remains to be done in relation to a set timeframe. The options can be analyzed based on the specific purpose of a burndown chart in different project management methodologies like Kanban and Scrum, or iteration-based projects. --- Option A: Kanban projects use burndown charts to ensure that work-in-progress (WIP) limitations are not exceeded. - Rejected: Kanban does not typically use burndown charts to track WIP limitations. Instead, Kanban uses WIP limits directly on the workflow to control the number of tasks that can be in each column or stage. Burndown charts are more commonly associated with tracking progress towards completing tasks, not limiting WIP. Option B: Scrum projects use burndown charts to visually manage how stories progress through the workflow and make bottlenecks and work quantities visible. - Rejected: While this statement mentions Scrum, it inaccurately describes the role of a burndown chart. In Scrum, burndown charts track the completion of work (like user stories) over time, but they don't specifically focus on managing workflow stages or bottlenecks. Bottlenecks are often addressed using other tools like Scrum boards or Kanban boards, which track the flow of work through different stages. Option C: Kanban projects use burndown charts to report on the amount of defects remaining after each iteration to ensure high quality at project completi...

Author: CrystalWolfX · Last updated Jul 9, 2026

An agile project manager observes that the Scrum team is falling behind on the completion of a particular sp...

Explanation: In an Agile environment, particularly in Scrum, the focus is on empowering the team to self-organize, identify issues, and continuously improve. When the team falls behind in a sprint, the Agile project manager's role is more about removing impediments and supporting the team, rather than giving direct instructions or creating external pressure. --- Option A: Facilitate by providing directions to the team about how they can get back on track. - Rejected: In Agile, specifically in Scrum, the team is self-organizing and responsible for determining how to complete the work. The Scrum Master (or Agile project manager) should not provide detailed directions on how to get back on track but rather help the team identify solutions themselves. Providing directions would undermine the team’s autonomy and the principle of self-organization. Option B: Request key stakeholders to extend the sprint to enable the team to complete their tasks on time. - Rejected: Extending a sprint is against the principles of Scrum. The length of a sprint is fixed, and extending it could lead to disruption of the regular cadence. The focus should be on delivering the work within the established sprint timeframe. If the team is behind, it’s a signal to reflect and improve in future sprints, not to extend deadlines. Option C: Ask the customers to help the team complete the testing on time to be able to finish their tasks on time. - Rejected: In Scrum, the responsibility for completing tasks, including testing, lies with the team itself. Asking customers to help with testing is not appropriate...

Author: Zara · Last updated Jul 9, 2026

The agile team has failed to meet their iteration goal, and contention has developed between members. The agile leader would like to determine how to improve the team...

Explanation: When the team fails to meet its iteration goal, it often signals underlying issues, such as miscommunication, lack of collaboration, unclear priorities, or external blockers. In this case, the agile leader’s focus should be on identifying and addressing the root causes of the problems, both in terms of productivity and morale. --- Option A: Standup meeting - Rejected: While daily standups are essential for tracking progress, they are not designed to resolve deeper team issues, such as failure to meet iteration goals or internal conflicts. Standups focus on short-term updates, which are helpful for monitoring progress but don’t provide the necessary space for reflection, problem-solving, or addressing team dynamics. Hence, they are insufficient for tackling productivity and morale issues on their own. Option B: Retrospective meeting - Selected: A retrospective meeting is the most appropriate response in this situation. Retrospectives are specifically designed to help teams reflect on their processes, identify what went well, and understand what could be improved. It's a safe space for team members to voice concerns and discuss what is preventing them from meeting their goals. In this context, the retrospective allows the team to address both productivity challenges (such as process inefficiencies or misunderstandings) and morale issues (such as interpersonal conflicts or burnout). The agile leader can guide the discussion to uncover and address these underlying problems, fostering a culture of continuous improvement. - Reasoning: The retrospective is designed to address root causes of issues, such as failures in meeting iteration goals, and it encourages open communication about bo...

Author: Julian · Last updated Jul 9, 2026

An agile team has received several new features to be added to the product backlog. The team is struggling to provide a reasonable estimate for feature development due to a lack o...

Explanation: When an agile team is struggling to estimate the development effort for new features due to a lack of experience, the goal of the experienced agile practitioner is to guide the team in a way that helps them improve their estimation process and provides them with a reasonable estimate. Different estimation techniques can be employed, but the best approach depends on the team's context and the need to balance learning and accuracy in estimation. --- Option A: Add a task to the product backlog to allow the team time to investigate and experiment prior to estimating. - Rejected: While giving the team time to investigate and experiment may help them gain experience with new features, this option doesn't specifically address the estimation process. It's more of an exploratory approach, which may lead to delays and uncertainty around the time it will take to develop the feature. The team will still need structured tools or techniques to facilitate the actual estimation, and this approach doesn't directly lead to quicker or more reliable estimates. Option B: Add a task to the product backlog to allow the team to apply a wideband Delphi estimation technique. - Rejected: The Wideband Delphi technique is a collaborative method where team members provide individual estimates, followed by group discussions and consensus. While it's effective for teams with diverse perspectives, it might be too complex for a team that is still lacking experience in providing estimates. The method also requires a facilitator, and its formal nature may be more than what's needed at this stage. The team would likely benefit more from a simpler, more structured approach first, such as planning poker. Option C: Add a task to the product backlog to allow the team to apply planning poker to estimate the effort. - Selected: Planning poker is a widely used, lightweight, and effective estimation technique that involves team members estimating tasks by assigning points (often using Fibonacci nu...

Author: Olivia · Last updated Jul 9, 2026

A company is planning to launch a new service to improve the customer checkout experience. What should the project manager do to meet the objective of reduc...

Explanation: The objective of the project is to reduce time to market and gain a competitive advantage by launching a new service that improves the customer checkout experience. To meet this objective, the project manager needs to choose an approach that allows for rapid delivery, flexibility, and continuous feedback, which are key components of Agile methodologies. --- Option A: Engage the project stakeholders to assess the best practices to apply and plan the deliverables before implementation. - Rejected: While engaging stakeholders to assess best practices and plan deliverables is important, this approach is more aligned with traditional project management or waterfall. This method typically involves a lengthy upfront planning phase and then executing against a detailed plan, which would slow down time to market. In a competitive environment, agile approaches like iterative development and continuous feedback are more suitable for reducing time to market and quickly adapting to customer needs. Option B: Recommend an agile delivery approach and provide information to the stakeholders on agile values and principles. - Selected: This is the most suitable option. Agile delivery emphasizes rapid iterations, frequent releases, and continuous customer feedback. By adopting an agile approach, the project manager ensures that the team can deliver functional components of the service quickly and continuously improve based on user feedback, resulting in a faster time to market. Introducing stakeholders to Agile values and principles will help set expectations for this iterative, flexible process and build their understanding of how it drives faster delivery, better adaptability, and enhanced collaboration. - Reasoning: Agile methods, like Scrum or Kanban, are designed to enable fast delivery through short cycles (sprints) and iterative improvements. This is cruc...

Author: Sam · Last updated Jul 9, 2026

The project manager has requested that the customer participate in the requirements gathering session for the next release. A conflict comes up regarding the requiremen...

When facing a conflict between the customer and the team regarding requirements, the project manager needs to carefully balance the needs of both parties while ensuring the project stays on track. A) Based on value to the organization, the project manager should decide what can be included or not in the final requirements. - Rejected: While the project manager holds decision-making authority, solely relying on this approach could lead to disengagement from the customer and the team. It risks making the project too top-down and may overlook the customer’s needs and the team’s capacity. The customer’s input is essential for the product’s success and value. A decision made in isolation could alienate stakeholders and negatively affect project buy-in. B) The customer is the end user of the product and should have the authority to decide about the product requirements. - Rejected: While the customer is key in defining the product’s core functionality, giving them total authority without collaboration with the team could lead to unrealistic expectations. Customers may not fully understand the limitations or possibilities that the team is dealing with. It's essential to collaborate with both the customer and the team to ensure the final product aligns with both expectations and technical feasibility. C) The project manager should discuss the requirements with the customer alone so that the team can deliver the prioritized requirements. - Rejected: Excluding the team from the requirements gathering process can lead to misunderstandings about what is technically feasible. The team’s expertise in what can realistically be built within the time, scope, and budget constraints is crucial. Additionally, leaving out the team from discussions could result in delays or quality issues down the line. It's im...

Author: Zain · Last updated Jul 9, 2026

A project is to be started with a team of nine existing and nine new members. The scrum master feels that the team is too large and wants to break it into three teams. The scrum master sets a constraint that each team have an equal number of existin...

When tasked with forming teams, especially in a situation with a mix of existing and new members, the Scrum Master needs to balance experience and skill distribution while fostering effective collaboration. The goal is to set up teams that can work autonomously, collaborate well, and leverage knowledge sharing effectively. A) Ask the team members' functional managers for guidance on how to group the team members. - Rejected: While functional managers might provide insight into individual capabilities, their input could overlook team dynamics and collaboration aspects. The Scrum Master is in the best position to assess how team members will work together and how to ensure that experience and knowledge are shared across the teams. Relying on functional managers may lead to decisions that are not aligned with the project’s goals of self-organization and collaboration. B) Observe which team members are comfortable working together, then assign accordingly. - Rejected: Comfort between team members is important for fostering a positive working environment, but this approach is overly focused on interpersonal preferences. Team success is driven by skill complementarity, shared knowledge, and diverse experience. Relying solely on comfort might result in less optimal skill distribution, which could hinder the team's ability to tackle all aspects of the project effectively. C) Ensure that members begin to self-organize as small teams with efficiently distributed skills. - Selected: This option encourages a self-organizing approach, which is a core principle of Scrum. Allowing team members to self-organize can foster ownership, responsibility, and collaboration. The Scrum Master can guide the process by ensuring that there are enough existing team members in each group to share knowledge and mentor new members...

Author: Leo · Last updated Jul 9, 2026

A key stakeholder feels they do not understand the project at a comprehensive level. What should the...

When a key stakeholder feels that they don’t have a comprehensive understanding of the project, it's essential to address their concerns in a way that promotes clarity, involvement, and collaboration. Each option offers a different approach, and the best choice depends on how to enhance the stakeholder’s engagement with the project’s progress and goals. A) Send daily status emails to let stakeholders know what progress is being made. - Rejected: Daily status emails provide a one-way communication channel that might not fully address the stakeholder's lack of understanding. These emails often only present facts and updates without allowing for meaningful interaction or feedback. This approach doesn't foster deeper engagement or understanding of the project, and may not clarify complex issues or concerns. Stakeholders might feel informed, but not necessarily involved or confident in their understanding. B) Invite stakeholders to attend daily Scrum meetings to get feedback. - Rejected: While involving stakeholders in daily Scrum meetings could provide them with visibility into the team's work, this might overwhelm them with too much detail and not allow enough time for them to process or ask questions. The daily Scrum is intended for the team to synchronize on their work and focus on what they need to do, not necessarily for stakeholder education. Stakeholders may become disengaged or frustrated if the meeting doesn’t align with their needs for understanding. C) Share information via interactive methods such as a brainstorming session. - Selected: This option is highly effective in addressing the stakeholder’s need for a better understanding of the project. Interactive methods like brainstorming sessions or workshops allow stakeholders to ask questions, engage with the team, and clarify any uncertainties they may have. These collaborative sessions foster open communication, address specific concerns, and allow for dir...

Author: Zara · Last updated Jul 9, 2026

What Our Friends Say

What Our Friends Say

PMI Practice Questions, Discussions & Exam Topics by our Authors

A team is preparing to demonstrate new product capabilities to a leadership team. The demonstration will show working software and a listing of the projected value of the capabi...

When working on a new product, what should an agile team do to ensure alignment with external stakeh...

On an agile project, it is important to identify and engage business stakeholders throughout the project and to ensure the team understands the ...

A high-profile project team is struggling to meet planned velocity. During a retrospective, the team agreed that their lack of experience in the technology resulted i...

During a retrospective, the team agrees that they have limited competence in using a newly introduce...

The agile lead is told by executive leadership that the team needs to work faster because the release date has been moved up three months. The agile lead communicates the updated timeline to the team. One of the junior team ...

After performing three sprints, the product owner and sponsor request an accurate schedule indicating when all releases wil...

A software project is being implemented by a small, colocated team. What should the project manager do to keep the team foc...

An agile team is having difficulties in obtaining the participation of a true user to be a part of their team. In the absence of a true user, the development manager steps in to act as a proxy for the user...

A project has several features that will deliver immediate customer value. The product owner needs to determine which features to include in the upcoming iteration....

An agile coach is working with a team that serves clients making product requests by phone. During a daily commitment and replanning meeting, a team member states that they were unable to resolve a client re...

During the advanced stages of implementing a complex design, an agile practitioner realizes that the architecture is not scalable for user requirements. The architect suggests a workaround that is minimally ...

An executive notices a kanban board in a highly visible location and expresses concerns to the project manager that too many ...

A new stakeholder has recently joined a project. During a meeting with the scrum master, the new stakeholder tries to understand the status of the project and the remaining task...

A project team developer has been involved in a large corporate initiative that has negatively impacted team productivity on another project to which they have...

Part way through a project, several team members are in conflict over whether or not a deliverable has been properly comple...

Project stakeholders are finding it difficult to know the real-time status of who has been assigned to various stories and the status of each work i...

A team member has made a mistake on a project. How should the scrum master address the mistake?

For what is the MoSCoW method used?

An agile team has started to worry because lately they have seen an increase in the number of issues. There seems to be a large variance in the quality of the work items delivered. The team now realizes that a sh...

One of the senior stakeholders on a project did not want to be engaged on a daily basis. During the iteration, the team encounters complexities but are convinced these issues ca...

While planning, what prioritization factors need to be considered for a minimally marketable feature...

A newly formed, colocated team is participating in daily standups, but is otherwise working largely as individual contributors. This has resulted in misalignment of activitie...

An agile team is struggling with an issue. A team member mentions that another team had a similar issue that was resolved, but lessons learned docu...

Over the last two sprints, a number of potential problems have threatened the team's ability to hit the targeted re...

One of the overseas stakeholders on an agile project has not been actively involved in the project's development. What ...

The customer asked the IT project manager to change a few specifications for the software being developed, which will affect the project budget. The financial sponsor is having difficulty approving changes to the b...

What should a scrum master do when an agile team member is behind on their tasks?

In a scrum team, who should be responsible for the budget and release plans?

A new agile team is forming to address a high-priority project. Team members are dispersed over a wide geographic area. The scrum master and the team are currently defining their working...

A team is building a product in three-week iterations. During the last retrospective, it was identified that there was a 20 percent increase from previous iterations in the number of reported defects and change r...

A team member has asked a question about the responsibilities of the product manager, QA, and the team regarding qua...

A project's product owner asks the scrum master to facilitate the estimation activity. The scrum master then meets with the team and the product owner to clarify the user stories. Following the meeting, the team ...

After some iterations, the agile practitioner observes that the team is self-organizing in small knowledge silos. Which a...

In a project, the customer asks for a requirement that clearly deviates from the contract terms. How...

During team meetings, the team often struggles with making decisions about their technical approach. What should be done...

In a planning meeting, the client does not have a clear understanding of the most beneficial features of a project, because there are too many stakeholders with diffe...

Why is stakeholder engagement important for project success?

On a complex project with a large degree of uncertainty, the team's velocity is declining. Upon testing, it is discovered that many of the work items reported as complete are not meeting the stakeho...

What is the risk of using agile in a distributed team?

The team is aware that they will need to integrate a new component to their solution in the next few weeks. The team does not have any expe...

A global organization is migrating its IT infrastructure from traditional, physical assets to cloud-based assets. Agile concepts are new to the organization because it currently uses a predictive approac...

Which statement describes the purpose of a burndown chart?

An agile project manager observes that the Scrum team is falling behind on the completion of a particular sp...

The agile team has failed to meet their iteration goal, and contention has developed between members. The agile leader would like to determine how to improve the team...

An agile team has received several new features to be added to the product backlog. The team is struggling to provide a reasonable estimate for feature development due to a lack o...

A company is planning to launch a new service to improve the customer checkout experience. What should the project manager do to meet the objective of reduc...

The project manager has requested that the customer participate in the requirements gathering session for the next release. A conflict comes up regarding the requiremen...

A project is to be started with a team of nine existing and nine new members. The scrum master feels that the team is too large and wants to break it into three teams. The scrum master sets a constraint that each team have an equal number of existin...

A key stakeholder feels they do not understand the project at a comprehensive level. What should the...