PMI Practice Questions, Discussions & Exam Topics by our Authors
The product owner wants to build security firewalls into the product.
How can the team members supp...
When a product owner requests to build security firewalls into the product, the team needs to ensure that the solution is feasible, effective, and aligned with the product's goals. Each of the options presents a different approach, and selecting the right one depends on understanding the context and level of detail already available.
A) Add new security features to the backlog and prioritize
This option assumes that the team already has a good understanding of what security features are needed and can prioritize them within the backlog. However, security features are typically complex and require a deeper understanding of both the technical and business requirements. Simply adding them to the backlog without proper research could result in unclear requirements or missed security needs. This approach works well if the security requirements are already well defined, but might not be suitable if the details are still unclear.
Reasoning for rejection: This approach lacks the necessary clarification of what exactly is required in terms of security, making it premature to just add it to the backlog.
B) Execute a spike to research security features for the project
A spike is a time-boxed research activity to explore unknowns or complex features. This is an ideal option when security features need to be thoroughly researched. By conducting a spike, the team can investigate different types of firewalls, explore security best practices, and evaluate how these features should be implemented within the product. This ensures that the team has enough knowledge to make informed decisions.
Reasoning for selection: A spike allows for in-depth exploration, making sure the team understands the requirements and the technical landscape before proceeding with implementation. It also helps reduce risks by gathering insights from security experts or existing frameworks.
C) Ask questions to determine where and how the product owner wants to use the product
This approach focuses on understanding the specific security ...
Author: NebulaEagle11 · Last updated Jul 9, 2026
An agile practitioner becomes a Scrum Master on an established Scrum team.
After introductions, wha...
When an agile practitioner steps into the role of Scrum Master for an established Scrum team, their primary responsibility is to help the team adhere to Scrum practices and improve their processes in a collaborative and supportive way. The first actions they take should focus on understanding the current state of the team, their dynamics, and how well the team is adhering to Scrum. Each of the options provided represents a different approach to initiating that transition, and each has its advantages and drawbacks depending on the context of the team’s maturity and existing issues.
A) Coach team members to improve functional specialties and increase overall velocity
This option focuses on improving individual team members' functional specialties and increasing overall velocity. While it's important to improve team performance, the role of the Scrum Master is not to directly coach individuals to specialize in functional skills. That responsibility typically falls to the team leads or technical managers. Additionally, focusing on increasing velocity early on may lead to a short-term mindset and ignore the longer-term improvements in team collaboration, quality, and process efficiency.
Reasoning for rejection: The Scrum Master’s role is not to focus primarily on improving individual specialties or directly driving velocity. It's about fostering collaboration, self-organization, and continuous improvement, not pushing for faster output without regard to quality or process alignment.
B) Identify where team processes misalign with accepted Scrum practices
This option is about identifying gaps in how the team adheres to Scrum practices. For an agile practitioner becoming a Scrum Master on an established team, it's crucial to understand where processes might be misaligned with Scrum principles. Early in the role, identifying misalignments can be key to ensuring the team is operating effectively within the Scrum framework. However, while identifying misalignments is important, this might not be the best first step, as it could create a confrontational atmosphere if approached too aggressively. It also requires a deeper understanding of the team’s current processes before making significant changes.
Reasoning for rejection: Identifying misalignments is important, but it's typically more effective once the Scrum Master has established trust with the team and understands their unique context. It’s better to first focus on team collaboration and fostering a sense of shared ownership before diving into process misalignments.
C) Facilitate the identification of problems or issu...
Author: Sara · Last updated Jul 9, 2026
A key stakeholder cannot attend the project vision statement development workshop. The stakeholder has emailed their requirements to the agile team lead, and believes that the...
When responding to a situation where a key stakeholder cannot attend a workshop for the project vision statement and believes it may not be critical, the agile team lead must balance the stakeholder's perspective with the importance of the vision in aligning the team and guiding the project's direction. Let's analyze each option in detail to determine the best response.
A) Emphasize to the stakeholder that a common, detailed vision will better ensure team understanding of the project
A clear and shared vision is fundamental in agile projects because it provides the team with a unified purpose and direction. However, emphasizing its importance to the stakeholder may not immediately address their concern about the lack of attendance. The stakeholder might not fully appreciate why the vision workshop is critical and could perceive it as an unnecessary meeting.
Reasoning for rejection: While this is a valid point, it might come across as too theoretical or abstract if the stakeholder is already convinced the vision isn’t critical. This option doesn't engage with the stakeholder directly to understand their perspective or collaborate to address their concerns. It may also risk creating friction if the stakeholder feels their requirements are being sidelined.
B) Personally meet with the stakeholder to understand their requirements, and then share the vision with the team
Meeting with the stakeholder can help to ensure their requirements are understood and captured clearly, which is critical in agile. After gathering the stakeholder’s input, the team lead could then work with the team to create a vision that reflects those requirements. This option helps ensure the stakeholder feels heard and valued. It also preserves the team’s opportunity to collaboratively create a vision while incorporating the stakeholder’s feedback.
Reasoning for selection: This is a highly effective approach because it allows the team lead to address the stakeholder's concerns directly while still ensuring the vision is developed collaboratively. It also demonstrates a proactive approach to inclusivity, as the stakeholder's requirements will be incorporated, even if they miss the workshop. It ensures alignment with the stakeholder's vision while still fostering the team's collaborative effort.
...
Author: Emily · Last updated Jul 9, 2026
During a daily stand up meeting, a developer expresses concerns that the selected technology limits the number of ...
When a developer raises concerns about the selected technology limiting the number of concurrent users, the team must consider several key factors to decide how to address the issue. These include the importance of non-functional requirements (such as scalability), alignment with the project’s goals, and the available options for mitigating the concern. Let's evaluate each option:
A) Ask the team to conduct research to find a viable solution
Asking the team to conduct research can be a proactive way to explore potential solutions to the problem. This is a good approach when the team needs to investigate technical options or workarounds. The research could help in identifying whether there are configuration changes, optimizations, or architectural adjustments that can alleviate the problem. This option is suitable if the technology’s limitations can be addressed through adjustments or if there is a need for more information before making a decision.
Reasoning for selection: This approach encourages the team to take ownership of the issue and find a technical solution, which aligns with the principles of self-organization in agile teams. It also gives the team a chance to explore alternatives and provide the best solution for scalability, which is a valid concern.
B) Select a better technology for team implementation
Switching to a completely different technology is a significant decision and may not always be the best immediate solution. It’s often a costly and time-consuming option that could introduce more problems (e.g., learning curve, integration challenges) than it solves, especially if the team has already made significant progress with the current technology. This drastic change might not be warranted unless the issue is fundamental and insurmountable.
Reasoning for rejection: This option might be too extreme and may not be the most effective way to solve the problem right away. Changing technology can lead to disruption, delays, and could introduce more complexity. It’s better to first explore solutions within the existing framework before considering such a drastic step.
C) Obtain customer input on their technology requirements
While customer input is always valuable, especially regarding the overall product and its functionality, the concern raised is specifically about a tec...
Author: Ravi Patel · Last updated Jul 9, 2026
A project manager is concerned that the team has misaligned expectations with some stakeholders, and that user stories were written only for generic user's perspective. This may lead the team to miss s...
When there are concerns about misaligned expectations and incomplete user stories, especially when the team has only considered generic users and may overlook other user types, the team needs tools that help them better understand and represent different user needs. Let's evaluate the options to identify which tools would be most effective.
A) Information radiators and wireframes
Information radiators are visual tools used to communicate project status, progress, or any other key information to stakeholders in an easily digestible format. Examples include burndown charts, Kanban boards, and dashboards. While useful for transparency and communication, they are not specifically designed to address user story development or user perspective gaps.
Wireframes, on the other hand, are visual representations of the user interface that help in understanding how users will interact with the system. While wireframes can be valuable for design and layout discussions, they do not directly address the issue of creating user stories for different user types or personas.
Reasoning for rejection: While both information radiators and wireframes are helpful in other aspects of agile projects, they do not directly help in capturing the various user perspectives or personas needed to write diverse user stories. These tools focus more on project tracking and design, not on user-centric story development.
B) Information radiators and story maps
Information radiators (as discussed) help keep stakeholders informed, but as noted, they are not particularly useful in solving the issue of misaligned expectations regarding user stories.
Story maps are a powerful tool for visualizing the entire user journey and organizing user stories based on how a user interacts with the product over time. They help ensure that user stories are aligned with the complete flow of tasks that different types of users might undertake. A story map can provide clarity on where gaps exist in the user stories, such as stories for non-generic users, and ensure the team is capturing stories for all relevant personas.
Reasoning for rejection: While story maps are an excellent tool for structuring user stories, they do not address the fundamental issue of capturing different user perspectives as effectively as personas or process flows would. Information radiators, although useful for tracking, do not directly help with developing diverse user stories.
C) Process flows and personas
Process flows are useful for understanding how users will interact with the system, step-by-step. They are helpful for visualizing workflows, understanding dep...
Author: Daniel · Last updated Jul 9, 2026
Based on the chart, what is the current status of the iteration when comparing story points planned ...
To determine the status of the iteration based on the comparison of story points planned versus completed, we need to analyze the key factors that influence each option. Here's a breakdown of the options and their relevance:
A) The iteration is in jeopardy
- When to select: This option is typically chosen if there is a significant gap between the planned and completed story points, indicating that the team is behind schedule. If the progress is slow and the team is not completing as many story points as planned, or if critical tasks are at risk of not being completed, the iteration is in jeopardy.
- Key factor: A large gap between planned and completed points or missing deadlines.
B) The team has removed scope
- When to select: This would apply if the team has removed planned stories or tasks in order to complete the iteration successfully. If the actual story points completed are less than planned, but this difference is due to a deliberate decision to remove scope for focus or realism, this option would be relevant.
- Key factor: Visible reduction in the overall scope, such as fewer stories being worked on or some work being deferred to a later iteration.
C) The iteration is ahead of schedule
- When to select: If the team has completed more story points than planned within the given iteration timeframe, this option would be selected. This would indicate that the team is working efficiently and is ahead of the original plan.
- ...
Author: Lina Zhang · Last updated Jul 9, 2026
The amount of information captured in the project's defects is varying within the development team. Team members are becoming frustrated with the defect quality inconsistencies and t...
To address the issue of varying defect information quality and the frustration it’s causing within the team, let's evaluate the options based on key factors such as urgency, team dynamics, and long-term solutions:
A) Stop the current iteration to discuss defect quality issues and explore solutions
- When to select: This option would be appropriate if the issue is causing immediate and significant disruption in the current iteration, potentially impacting deliverables. If defects are being misreported or poorly documented, it could halt progress and make it necessary to resolve the issue immediately.
- Key factor: Immediate need to fix the problem if the lack of defect quality is severely hindering the iteration. However, it disrupts the current flow of work.
- Rejection Reason: Stopping the iteration can cause delays and disrupt progress on the current work. It may not be necessary unless defects are directly affecting the iteration's ability to deliver quality results.
B) Discuss and explore solutions in the next planning meeting and take corrective actions as required
- When to select: This option can be selected if the team feels that defect quality issues are significant but not urgent enough to stop the iteration. By addressing the issue in the next planning meeting, the team can set clear guidelines for defect documentation moving forward.
- Key factor: The issue isn’t immediately derailing progress, but it’s important to address it in a structured meeting where corrective actions can be planned for the next iteration. This allows for thoughtful planning without interrupting current work.
- Rejection Reason: If the problem is urgent and significantly affecting current work, waiting for the next planning meeting might delay finding a resolution, allowing frustrations to build.
C) Generate insights at the next retrospective and adjust processes as decided by the team
- When to select: This option is ideal for addressing process issues and inefficiencies. The retrospective is the right time to reflect on what went wrong and what can be improved in terms of defect documentation and quality. It encourages team collaboration and continuous improvement.
- Key factor: If the team can tolerat...
Author: Manish · Last updated Jul 9, 2026
An agile team delivered a feature in the last iteration. The product owner, who missed the planning and review meetings, was dissatisfied with feature. The team conducted a retrospectiv...
In this situation, the team has delivered a feature, but the product owner (PO) is dissatisfied with the outcome due to missing the planning and review meetings. The team conducted a retrospective and reviewed the user stories related to the feature. Now, the question is what the team should do next to address the dissatisfaction and ensure better alignment in future work.
Let's evaluate each option carefully:
A) Ensure that the product owner reviews the acceptance criteria for delivered user stories
- When to select: This option would be appropriate if the issue stems from a misalignment between what the PO expected and what was actually delivered. Ensuring the PO reviews and approves the acceptance criteria before work begins is a proactive way to prevent misunderstandings and dissatisfaction.
- Key factor: The dissatisfaction arises from a lack of clarity in expectations. By involving the PO early in the process (such as during the refinement phase or before the start of each iteration), the team can ensure the criteria align with the PO’s vision.
- Rejection Reason: This option assumes the core issue is with the acceptance criteria and not with other aspects like the overall delivery process or the PO's absence from key meetings.
B) Augment the quality assurance and continuous integration processes for delivery
- When to select: This option would be suitable if the feature was delivered with defects or quality issues that the PO didn’t approve of, and the dissatisfaction stems from the technical quality of the feature. It focuses on improving technical processes for more reliable deliveries.
- Key factor: The focus here is on improving internal processes to ensure higher quality output. This is useful if the dissatisfaction is related to bugs, missed requirements, or inconsistent quality.
- Rejection Reason: If the dissatisfaction is not due to quality issues but rather due to misalignment on expectations (because the PO missed key meetings), focusing only on QA and continuous integration may not fully address the root cause.
C) Approach the relevant developers and testers regarding quality issues, in upcoming iterations
- When to select: This option would be relevant if the dissatisfaction stems from poor quality or incomplete work due to insufficient testing or development issues. It could help the team focus on improving specific areas (e.g., testing, development, or code review).
- Key factor: If the dissatisfaction is because the feature didn't meet the expected ...
Author: Daniel · Last updated Jul 9, 2026
A scrum master assumes a project that is essential to organizational growth. The project is expected to be in production fo...
When a Scrum Master assumes a project that is crucial to organizational growth and is expected to be in production for three years, it’s vital to ensure a strong foundation for the project’s long-term success. Let’s break down the options and evaluate which one is the most appropriate for the Scrum Master to prioritize.
A) Work with the customers to build the product backlog and identify their initial requirements
- When to select: This option focuses on understanding the customers’ needs and building the product backlog. It’s useful for making sure that the team delivers exactly what the customers want.
- Key factor: It’s important to gather and prioritize requirements early, but this should not be the first step. The Scrum Master needs to first understand the project’s broader context and vision before diving into the backlog creation.
- Rejection Reason: While building the product backlog is essential, it presupposes that the Scrum Master understands the project’s broader goals, which is something that should be clarified with stakeholders and architects first.
B) Meet with the stakeholders and enterprise architects to understand the project's vision
- When to select: This is the most strategic option. Before jumping into any sprint planning or backlog creation, the Scrum Master should first understand the vision of the project and how it aligns with the organization’s goals. Meeting with stakeholders and enterprise architects is crucial to ensure the project’s objectives, architecture, and long-term goals are clear.
- Key factor: Understanding the project’s vision ensures the team works towards the right goal. This alignment will provide clarity on scope, priorities, technical requirements, and the project’s future direction, which will directly impact backlog creation and sprint execution.
- Rejection Reason: While it may delay direct work on the backlog, it’s absolutely necessary to have the vision, priorities, and constraints in place before starting development. Without this clarity, the team could work towards a misguided or misaligned product.
C) Plan and execute a sprint 0 to establish the project's foundational needs
- When to select: A sprint 0 could be useful for setting up infrastructure, environment, or initial high-level backlog items. It provides a “jump-start” for a project.
- Key factor: Sprint 0 should not be the first thing the Scrum Master does. It’s important to first ...
Author: Nia · Last updated Jul 9, 2026
A development team, new to scrum, questions the need to collect metrics on team performance. While team members understand velocity and burn down, they feel that once velocity becomes s...
When a development team new to Scrum questions the need for tracking metrics like velocity after it has "settled," it’s important to help them understand the value of these metrics beyond just tracking performance. While the team understands velocity and burn-down charts, they may not fully grasp how ongoing tracking can contribute to continuous improvement and long-term success.
Let’s break down the options and evaluate which one is the most suitable:
A) Continuing to track velocity allows functional managers to assess whether or not the team is performing at the desired rate
- When to select: This option focuses on using velocity to assess team performance from the perspective of management. It suggests that tracking velocity helps managers determine if the team is meeting the expected rate.
- Key factor: Functional managers are often interested in measuring productivity and team output. However, in Scrum, the focus should be on the team's own improvement and delivery quality, rather than just meeting external performance targets.
- Rejection Reason: This approach emphasizes management's needs over the team's self-improvement. It could be perceived as micromanagement or a misalignment with Scrum values, which prioritize self-organizing teams and collaboration.
B) The trends will show how the team performs against other scrum teams in the organization
- When to select: This option implies using velocity to compare the team’s performance with other Scrum teams within the organization. It could help identify whether the team is on par with others or if they need more resources or support.
- Key factor: Scrum is meant to be a collaborative, self-organizing framework. Comparing teams based on velocity can create unhealthy competition, misinterpretations of data, and potentially undermine trust and collaboration.
- Rejection Reason: This approach is counterproductive in Scrum. Velocity should not be used to compare teams, as it varies from team to team depending on their context, maturity, and focus. It is about tracking the team’s own progress, not competing with others.
C) Tracking velocity will provide a baseline for the team to see how their continuous improvement efforts are working
- When to select: This option focuses on using velocity as a tool for continuous improvement, which is a key principle in Scrum. By tracking velo...
Author: MysticJaguar44 · Last updated Jul 9, 2026
A team is creating a highly marketed, time-sensitive product. The agile coach is concerned that anything other than exceptional quality will result in bad publicity ...
In this scenario, the agile coach's main concern is ensuring exceptional quality to prevent any negative publicity for the product, which is highly marketed and time-sensitive. Let’s break down the options and analyze the key factors:
Option A: Establish pair programming partners, and regularly perform peer reviews
- Pros:
- Pair programming fosters collaboration, knowledge sharing, and immediate feedback, which can enhance code quality.
- Peer reviews provide an additional layer of scrutiny, helping catch bugs early and ensuring the code adheres to quality standards.
- Continuous collaboration can help prevent the kind of issues that might harm the product's reputation.
- Cons:
- Pair programming might slow down development if not managed properly, and may not be the most efficient for a fast-paced project. However, its benefits in maintaining quality outweigh this drawback in a time-sensitive, high-stakes environment.
- Why selected: Given the need for high quality, pair programming and peer reviews are the most effective ways to ensure the code quality is maintained throughout the development process. They help prevent issues from accumulating and ensure the team is consistently producing high-quality work.
Option B: Perform demos at the end of each iteration
- Pros:
- Demos at the end of each iteration are great for showing progress and getting early feedback.
- Cons:
- This option is focused more on visibility to stakeholders rather than on ensuring code quality. The demo could show features, but it doesn’t guarantee that the underlying code is of the highest quality. Moreover, by the time an iteration is complete, bugs might be harder to address in a timely manner.
- Why rejected: While demos can offer feedback, they don’t directly help in addressing code quality concerns. The feedback from demos usually focuses on functionality rather than the technical quality of the code. Therefore, this is less useful for preventing bad publici...
Author: Henry · Last updated Jul 9, 2026
During mid-sprint changes, an agile facilitator meets with the executive and development teams. During the meeting, executive team members resolve conflicts, and on their own initiative, review the iteration charts to discuss ...
In this scenario, the agile facilitator is meeting with both the executive and development teams during a mid-sprint review where executive members are resolving conflicts and independently reviewing iteration charts. The key action is that the executives are discussing changes to the iteration’s functional goal, which indicates that the facilitator is promoting collaboration and visibility between both teams to ensure that the project stays aligned and healthy.
Let’s evaluate each option based on the scenario:
Option A: Building openness and transparency on the project's health and status
- Pros:
- Openness and transparency are core principles in agile. By having the executive team review the iteration charts and discuss changes, the facilitator is promoting transparency around the project's progress, health, and status.
- This is a key part of any agile project, as it ensures that all stakeholders are aware of where the project stands, and allows for informed decision-making.
- Cons:
- While this is an important practice, it doesn’t completely capture the broader dynamic happening in the meeting, particularly with the focus on resolving conflicts and discussing changes to the iteration's functional goal, which indicates a more collaborative and action-oriented discussion.
- Why selected: The facilitator is certainly promoting transparency, but the key point here is that the executives are actively resolving conflicts and reassessing goals, which points more towards facilitating collaboration and alignment.
Option B: Facilitating conflict resolution among executive team members
- Pros:
- The facilitator is indeed helping the executive team resolve conflicts, but conflict resolution seems to be a minor element in the overall meeting focus. The main purpose appears to be more about collaborating on iteration goals and aligning on the direction, rather than just resolving interpersonal conflicts.
- Cons:
- While conflict resolution is part of the agile facilitator’s role, it’s not the primary focus of this meeting. The meeting is more about aligning on the project’s goals and making adjustments, rather than managing interpersonal conflict.
- Why rejected: Conflict resolution is a piece of the overall puzzle...
Author: Ming88 · Last updated Jul 9, 2026
What can a team use to prioritize stories?
When prioritizing stories, teams need a method that helps them focus on the most important, high-value work first. Let’s evaluate each option to determine which method is most suitable for prioritizing stories.
Option A: MoSCoW Method
- Pros:
- The MoSCoW method is a popular prioritization technique that classifies work into four categories:
- Must-have: Essential for the project to be considered a success.
- Should-have: Important but not essential for the immediate release.
- Could-have: Nice to have but not critical.
- Won’t-have: Not necessary at this time.
- This method is great for prioritizing stories based on their criticality, making it highly useful when trying to decide what to tackle first based on value and necessity.
- Cons:
- This method doesn't give a numerical value or weighting to each story. It’s more qualitative and subjective.
- Why selected: The MoSCoW method is particularly effective when the team is working with multiple stakeholders or customers and needs to quickly categorize work into must-have versus lower-priority items. It offers clear, simple categories that help in immediate decision-making about what to prioritize.
Option B: Planning Poker Technique
- Pros:
- Planning poker is a consensus-based estimation technique where team members estimate the effort or complexity of a user story using cards with values. It helps get a shared understanding of the story’s effort, which is great for estimation purposes.
- Cons:
- This method is primarily focused on estimating effort or complexity rather than prioritizing stories. While it helps to understand the scope, it does not provide a direct way of deciding which stories are more important or should come first in the sprint.
- Why rejected: While useful for estimating the work required for stories, planning poker is not designed for prioritizing stories based on value or importance, which is the core need in this case.
Option C: Weighted Average Calculatio...
Author: BlazingPhoenix22 · Last updated Jul 9, 2026
Business stakeholders of an agile project frequently skip the review meetings.
What should the agil...
When business stakeholders skip review meetings, it can lead to a lack of alignment and insufficient feedback, which are critical in agile projects. The agile practitioner needs to address this issue in a way that encourages active involvement while ensuring the progress and value of the project are communicated clearly. Let’s evaluate each option:
Option A: Ask the product owner to inform all stakeholders about the project's progress
- Pros:
- The product owner is the primary point of contact for stakeholders and has a good understanding of the project’s goals and progress.
- This approach ensures stakeholders are kept in the loop regarding key updates and progress.
- Cons:
- Informing stakeholders after the fact may not be sufficient, as it doesn’t provide the opportunity for them to engage with the team, ask questions, or provide timely feedback.
- This could make stakeholders feel more detached, leading to less engagement in the long term.
- Why rejected: This is a passive solution that keeps stakeholders informed but does not solve the problem of their lack of involvement or engagement in the review meetings. Direct engagement is key to successful collaboration.
Option B: Send meeting notes to all stakeholders after each review meeting
- Pros:
- Sending meeting notes ensures that stakeholders who missed the meeting can still catch up on the discussions, decisions, and progress made.
- Cons:
- While sending notes provides some level of communication, it is still one-way. Stakeholders miss out on the real-time interaction and feedback exchange that typically happens during the review meetings.
- Review meetings are intended to be a collaborative, interactive process, and sending notes after the fact doesn’t promote active participation.
- Why rejected: While notes can be helpful, they don’t foster real-time collaboration and feedback, which is crucial in agile. Stakeholders need to be part of the conversation, not just passive recipients of information.
Option C: Include the results of the review meetings in the information radiators
- Pros:
- Information radiators (e.g., boards, charts, dashboards) display key information in a visual, easily accessible...
Author: Isabella · Last updated Jul 9, 2026
After three iterations, it is identified that a project's underlying security structure architecture is unstable. While there is a technical solution, all work to date is flawed. This will impact severa...
In this scenario, the project has identified a flawed security architecture after three iterations, which is crucial for the product’s long-term success. The issue will impact future business services, so it is important to address it promptly to avoid further risks and losses. The product owner must take action to resolve the issue while managing the team’s resources and the overall direction of the project.
Let’s evaluate each option:
Option A: Ask the development team to address the issue since it is in their domain
- Pros:
- The development team is responsible for delivering the technical aspects of the project, including security.
- This approach would allow the team to dive into fixing the technical issue directly.
- Cons:
- This option does not account for the broader implications of the flaw, particularly on future service offerings or on the project's business alignment. It’s important for the product owner to involve stakeholders and the team in a more strategic discussion about how to move forward.
- Just addressing the issue within the development team without aligning with stakeholders could lead to misalignment with business goals, as this is not just a technical problem, but a business-critical issue.
- Why rejected: While the development team should be involved in solving the technical issue, this approach doesn't involve the necessary discussions with stakeholders to align on the larger impact. It risks not addressing the business consequences adequately.
Option B: Review the project's risk matrix, and follow the steps outlined in the risk mitigation plan
- Pros:
- The risk matrix is a valuable tool for identifying and assessing the impact of issues, and following the risk mitigation plan is a structured approach to resolving problems.
- It provides a holistic view of the risks and allows the team to prioritize actions to mitigate future impacts.
- Cons:
- While reviewing the risk matrix is a good step, it may be too late if the architectural flaw has already been identified as impacting future service offerings. The focus needs to be more on immediate corrective action rather than just risk assessment.
- Following the risk mitigation plan might be part of the solution, but this approach is reactive, focusing on process rather than addressing the immediate need for rework and realignment of the project.
- Why rejected: Reviewing the risk matrix is a reactive step and may not directly help in aligning the team and stakeholders around immediate corrective actions. It's important to directly address the impact on business offerings rather than just managing risks.
Option C: Meet with the team and s...
Author: Grace · Last updated Jul 9, 2026
A scrum team has eight developers, but only two are database engineers. During the last few retrospectives, the team identified that most sprint stories are dependent upon database engineers. This ...
Analysis of the Options
Let's break down the options one by one, considering the key factors of team capacity, skill development, sprint velocity, backlog management, and the urgency of the problem.
---
A) Have other team developers attend training to learn database skills
Pros:
- Long-term solution: By increasing the number of database-skilled developers, you can reduce dependency on the two database engineers over time.
- Improved team versatility: Other team members will be able to handle database tasks, increasing the overall flexibility of the team.
Cons:
- Learning curve: Training may take time, and new skills might not be immediately applicable in the next sprint. The team may face additional delays while developers get up to speed.
- Potential impact on velocity: During the training period, developers might be less effective in their usual roles, which could temporarily affect sprint progress.
- Not immediate: While it's a great long-term solution, it doesn’t immediately address the current sprint's challenges.
When to use: If you anticipate that this problem will continue for several sprints, investing in skill development makes sense. However, it’s not ideal if the bottleneck needs to be solved quickly for the current sprint.
---
B) Monitor the retrospectives of two additional sprints before taking action
Pros:
- Data-driven decision-making: This option suggests waiting to gather more data, which could help in identifying if the problem is recurring or if it’s just a temporary fluctuation.
Cons:
- Delayed response: The team is already aware of the issue from the past retrospectives, so waiting two more sprints may result in ongoing inefficiency and frustration.
- Missed opportunity for improvement: The team would continue to be blocked, and productivity could suffer in the meantime.
When to use: This option might make sense if the team isn't entirely sure that the issue is a recurring bottleneck and feels like it could be a short-term fluctuation. However, given that the problem has already been identified in multiple retrospectives, immediate action is preferable.
---
C) Plan fewer stories for the sprint to reduce the database engineer's workload
Pros:
- Short-term relief: This option could immediately alleviate the workload of the database engineers, ensuring they aren’t overloaded and that they can complete the most critical tasks.
- Focused work: The remaining team members can focus on non-database tasks while the database engi...
Author: Elijah · Last updated Jul 9, 2026
An agile project has three more iterations before the release. There is lot of report functionality to be created and defects to be cleared. During a daily scrum, a team member suggests a timebox spik...
Analysis of the Options
To determine the most appropriate course of action, we need to consider key factors such as current team velocity, project timeline, remaining work (both features and defects), risk of delaying release, and long-term efficiency improvements.
---
A) Encourage the team to self-organize and determine how to best complete their existing work and this spike
Pros:
- Team autonomy: Encouraging self-organization can lead to a motivated and empowered team that makes decisions based on the immediate needs and context.
- Flexibility: The team can assess the trade-offs of working on the spike versus completing the existing tasks and make decisions accordingly.
- Ownership: The team is responsible for choosing how to balance immediate needs with longer-term improvements, fostering collaboration.
Cons:
- Risk of distraction: If the team prioritizes the spike without clear guidance, they might get distracted from the primary goal, which is to complete the release with the current work and defect fixes.
- Lack of structure: Without a clear direction from the project leader, the team may struggle to effectively allocate time between report functionality, defect fixes, and the spike.
When to use: This approach works well when the team is highly experienced and capable of making strategic decisions independently. However, in this case, given that the release deadline is approaching, a more guided approach might be necessary to ensure focus.
---
B) Encourage the team to complete their just existing work since the team velocity indicates they are already struggling to meet the release goal
Pros:
- Focus on critical work: With the release deadline in sight, completing existing work, especially defect fixes, is essential. This ensures that the team stays focused on the most important tasks.
- Prevent scope creep: By discouraging the spike, the team avoids adding new work that might compromise the sprint goals or release readiness.
Cons:
- Short-term thinking: While focusing purely on existing work is important for meeting the release goal, this approach overlooks potential long-term efficiency improvements that could help reduce future bottlenecks.
- Missed opportunity: If the spike can lead to a more efficient reporting process, deferring it until later might increase technical debt, causing further delays in future iterations.
When to use: This option is suitable when the team is already behind on velocity and needs to focus exclusively on completing the existing work and fixing defects to meet the release. It works when the current iteration’s priority is to ensure stability and readiness for the release.
---
C) Direct the team to defer the spike until the next release and add the action on the backlog for prioritization
Pros:
- No disruption to the current releas...
Author: Olivia · Last updated Jul 9, 2026
While attending a conference, an agile practitioner learns of a new user interface (UI) framework that could benefit th...
Analysis of the Options
When introducing a new framework or tool, it’s important to evaluate its fit for the team’s current needs, the impact on ongoing work, and whether it aligns with the team's goals. The key factors here are team readiness, prioritization (does this fit into the current backlog?), feedback loops (how does the team feel about this?), and how it impacts the release cycle.
---
A) Identify a team member to do a proof of concept using this framework
Pros:
- Hands-on evaluation: A proof of concept (PoC) allows the team to test the framework in a controlled way, understanding whether it meets their needs without committing fully.
- Team involvement: Involves a team member in hands-on experimentation, which could generate more buy-in and practical insights into the framework's effectiveness.
Cons:
- Requires time and resources: Depending on the team’s capacity, dedicating a member to a PoC could temporarily divert attention from current sprint goals and backlog items.
- Potential delay in feedback: This approach might delay team-wide adoption or feedback since it focuses on one person’s perspective first, rather than gathering the team’s collective opinion early.
When to use: This approach works well if the framework seems promising and the team has the bandwidth for experimentation. However, it may not be the best first step without a broader discussion of the team’s needs and priorities.
---
B) Email the team directing them to immediately begin using this new framework
Pros:
- Immediate action: The team would start using the framework right away, potentially improving their workflow if it’s as effective as it appears.
Cons:
- Lack of buy-in: Simply directing the team to use a new framework could lead to resistance if the team isn’t convinced of its value. It might be seen as top-down imposition rather than a collaborative decision.
- Disruption to ongoing work: Adopting a new framework mid-sprint could cause disruption, requiring rework, training, or adjustments to existing tasks.
- No time for evaluation: The framework might not fit the team's needs or goals, and rushing into its adoption without understanding its relevance could waste valuable time and resources.
When to use: This approach could be useful if the framework is critically important to the product’s success and the team is already highly familiar with similar tools, so no training or transition period is needed. However, that’s rarely the case, and it can lead to unnecessary disruptions.
---
C) Obtain feedback from team members on the new framework, and then suggest that the product owner create a backlog item to do a spike on it
Pros:
- Inclusive approach: Getting feedback from the team ensures that everyone has a say in whether the framework is worth pursuing.
- Data-driven decision: Instead of rushing into adopting the framework, this option involves gathering insights from the team, which helps make an informed decision.
- S...
Author: Grace · Last updated Jul 9, 2026
The agile practitioner has determined that two different team members are working on addressing the same major issue on the pr...
Analysis of the Options
The key problem here is that two team members are addressing the same major issue, which can lead to inefficiency, confusion, and duplicate work. The agile practitioner must ensure clarity in task assignment, effective collaboration, and reduction of wasted effort. Let’s analyze each option with these factors in mind.
---
A) Implement a burnup chart and add the issue resolution as a task to the product backlog for the customer to prioritize
Pros:
- Customer visibility: By adding the issue to the product backlog, the customer gains visibility into the work, which aligns with the agile principle of customer collaboration.
- Tracking progress: The burnup chart is useful for tracking progress over time, particularly to understand how much work has been completed versus how much remains.
Cons:
- No immediate resolution: This option doesn’t address the immediate problem of duplicated work or clarify ownership of the issue. The two team members may continue working on the same task without clear direction, leading to inefficiencies.
- Additional administrative work: Adding this issue to the backlog and tracking it with a burnup chart might add overhead and doesn't solve the core issue at hand.
- Lack of focus: The main concern right now is the duplication of effort, which needs immediate attention, not additional tracking or backlog grooming.
When to use: This would be useful for longer-term visibility and tracking but doesn’t resolve the immediate conflict of two team members working on the same issue. It can be done after addressing the immediate task allocation issue.
---
B) Add the issue to the kanban board and assign the issue to the team member who has made the most progress on resolving it
Pros:
- Clarifies ownership: By assigning the issue to one team member, it resolves the ambiguity and helps prevent further duplication of effort.
- Kanban integration: Using the Kanban board ensures the issue is visually tracked, making it clear who is responsible for resolution and what stage the task is in.
Cons:
- Potential for unfinished work: If both team members have already made progress, simply choosing one person may leave the other feeling like their work is undervalued, which can affect morale.
- Possible disruption: The other team member may need to switch focus, which can be disruptive if the initial work was meaningful or close to completion.
When to use: This is appropriate if the issue is well-defined and can be assigned to a single owner. It works well when one team member has already made clear progress and needs support to complete the work efficiently, without causing major disruption to the current iteration.
---
C) Conduct a root-cause analysis on the issue and identify related risks and risk response owners at the next retrospective
Pros:
- Deep dive: A root-cause analysis will help the team understand why this issue occurred and what led to the duplication of effort, po...
Author: FrostFalcon88 · Last updated Jul 9, 2026
An executive requests information regarding a sprint status.
What action should the product owner t...
Analysis of the Options
When an executive requests sprint status information, the product owner needs to ensure that the request is addressed in a way that is efficient, transparent, and aligned with agile principles. The key factors to consider are transparency, timeliness, stakeholder engagement, and avoiding disruptions to the team's workflow.
---
A) Invite the executive to the stand-up
Pros:
- Direct visibility: The executive will see firsthand the team's progress, blockers, and interactions, which may provide a deeper understanding of the team's work.
- Transparency: It demonstrates transparency, allowing the executive to be involved in the ongoing work and see how the team is operating in real-time.
Cons:
- Disruption to the team: Stand-ups are meant to be short, focused meetings for the development team. Inviting an executive could disrupt the team's flow and make members feel uncomfortable, as it might change the dynamics of the meeting.
- Not the right forum: The stand-up is typically focused on the team’s immediate work. It may not provide a detailed status update that an executive would be looking for, and could end up deviating from the intended purpose of the meeting.
When to use: This approach is suitable in cases where the executive is highly familiar with the team’s work and just needs an informal, quick update. However, it’s generally not ideal due to the potential disruption and limited context provided in a stand-up.
---
B) Direct the executive to the information radiator
Pros:
- Self-service: The information radiator (e.g., a visible chart or board showing sprint progress, burndown charts, task status, etc.) allows the executive to access up-to-date information on the team’s progress without disrupting the team.
- Transparency: It aligns with agile values of transparency and ensures that stakeholders can easily track progress.
- Efficiency: The executive can independently view the information without needing a meeting or interaction, saving time for both the executive and the product owner.
Cons:
- Lack of context: While the information radiator provides visibility, it doesn’t offer deeper context or answers to specific questions the executive might have about the sprint.
- Potential misinterpretation: Without context, the executive may misinterpret the data on the information radiator, leading to confusion or unnecessary follow-up questions.
When to use: This option works well when the executive is familiar with the product and understands how to interpret the information. It's ideal for those who value self-service and quick access to status updates without requiring additional explanations.
---
C) Personally meet with the executive
Pros:
- Tailored information: A personal meeting allows the product owner to directly address the executive’s specific needs and provide a more detailed, customized status update.
- Engagement: It’s a good opportunity for building a relationship with the executive and providing clarity on any concerns or questions they may have.
- Direct communication: It...
Author: Liam · Last updated Jul 9, 2026
Agile team A struggles to deliver committed stories due to technical dependencies with team B, which continuously fails to meet its d...
When an Agile team faces technical dependencies that hinder its ability to deliver committed stories—particularly when one of those teams (team B) is not meeting its delivery commitments—it's important to address both the root cause and the impact on team dynamics. Let's analyze each option to understand their effectiveness:
A) Create a new team to deliver the dependencies, and bring team B under performance management
- Pros: Creating a new team could directly address the dependency problem by isolating the bottleneck and focusing on the critical task of delivering the dependencies. Performance management for team B might push them to improve.
- Cons: Introducing a new team could lead to more complexity and overhead in terms of coordination and communication. Additionally, putting team B under performance management may hurt morale and further complicate collaboration rather than promoting healthy, Agile team behavior. It doesn't solve the underlying collaboration or technical issue; it only redirects it.
- Scenario: This option might work if the dependency issue is solely related to a lack of resources or a critical dependency that cannot be handled within the current teams. However, it’s unlikely to be a long-term solution, as it bypasses the Agile principle of team self-sufficiency and accountability.
- Rejection Reason: Over-complicates the situation by creating new teams and focusing on punitive measures rather than collaboration.
B) Conduct a vision-sharing session with the teams to communicate the project's overall goals
- Pros: A vision-sharing session can help teams align on the bigger picture, which might create better understanding and collaboration. If teams know how their individual work contributes to the overall project, they may become more motivated and proactive in resolving issues, including dependencies.
- Cons: While communication is crucial, simply sharing the vision doesn't directly address the immediate issue of unmet delivery commitments or dependencies. It's a necessary but insufficient action if there are deeper technical or coordination issues at play. It’s a good step toward team alignment but doesn't provide practical solutions to the problem.
- Scenario: This option would be helpful if the teams are misaligned or lack an understanding of the broader goals, but it won't resolve technical bottlenecks or team performance issues directly.
- Rejection Reason: Important for alignment but does not directly tackle the technical dependencies or delivery failures.
C) Swap team members from both teams so that deliveries are better supported
- Pros: Swap...
Author: RadiantJaguar56 · Last updated Jul 9, 2026
An agile team discovers a new risk and identifies that its impact may be severe.
What should an agi...
When a new risk is discovered that could have a severe impact on an Agile team’s work, the team needs to respond quickly and effectively to mitigate or address the risk. Let’s analyze each option:
A) Add a goal to the current iteration to fully mitigate or control the risk
- Pros: Adding a goal to mitigate or control the risk within the current iteration demonstrates a proactive approach. It ensures the team directly addresses the risk without delay.
- Cons: Mitigating or controlling a severe risk might require significant time or resources that the team may not have available in the current iteration. Adding such a goal could potentially disrupt the planned work for the iteration, jeopardizing commitments and team velocity. Agile teams should avoid overloading iterations with additional objectives that could lead to failure to deliver on committed work.
- Scenario: This option might work if the risk is directly tied to a deliverable that is already in progress and needs immediate action. However, this could be risky if the team is already stretched and introducing a new goal would reduce their ability to deliver on other important work.
- Rejection Reason: While the approach is proactive, it may introduce too much disruption to the current iteration's planned work and priorities.
B) Balance risk reduction and value-adding activities in the next iteration
- Pros: Balancing risk reduction with value-adding activities in the next iteration is a sensible approach because it allows the team to continue delivering value while also addressing the risk. Agile is about incremental progress, and this approach avoids overly focusing on one at the expense of the other. By planning to reduce the risk while still delivering on prioritized features, the team can maintain momentum.
- Cons: The balance between risk mitigation and value delivery needs to be carefully considered. If the risk is severe, it may be tempting to focus too much on risk reduction, which could delay important features. However, this approach offers flexibility and room for negotiation.
- Scenario: This option is ideal when the risk is significant but not immediately threatening to the project. It allows the team to make progress on both fronts and reassess priorities.
- Rejection Reason: It might not immediately reduce the risk if it’s very severe and needs an urgent response. However, it’s a balanced, sustainable approach if the risk can be mitigated over time without major disruption.
C) Continue with the current plan to maintain team velocity
- Pros: Continuing with the current plan could maintain team velocity, allowing the ...
Author: Isabella · Last updated Jul 9, 2026
The team underestimated the complexity of a story, resulting in new decomposition of the work to be delivered in the current sprint and items to be...
When the team underestimates the complexity of a story and must rework the plan in the current sprint, the Scrum Master’s role is to guide the team in handling the situation and improving their processes for the future. Let's analyze each option:
A) Ask the project manager to work with the product owner to help generate clearer stories in the future
- Pros: Involving the project manager and the product owner can be helpful if there are gaps in the understanding of story requirements or if there are issues with how the stories are written. It might help improve clarity in the future.
- Cons: The Scrum Master should focus on facilitating the team’s self-improvement and collaboration, not delegating responsibility to external roles. The issue is not necessarily with how stories are generated but with how the team is estimating and breaking down work. Also, this step doesn’t directly address the current situation.
- Scenario: This could be relevant in cases where there is a lack of collaboration between the Scrum Team and the Product Owner. However, it's less about the team's internal processes and more about external delegation of responsibility.
- Rejection Reason: The issue at hand is internal to the Scrum Team, and solving it requires self-improvement, not external delegation.
B) Develop guidelines to prevent future occurrences
- Pros: Developing guidelines could help prevent the same mistake in future sprints, particularly if the team repeatedly faces similar issues with estimation.
- Cons: Guidelines might not be enough to solve the root cause of the issue. The problem could be with the team's estimation techniques, lack of communication, or failure to decompose work correctly. A more interactive approach such as reflection and improvement is generally more effective. Additionally, guidelines might be seen as rigid and may not fully adapt to the team’s evolving needs.
- Scenario: This might be useful if the team has a consistent problem with estimation or decomposition. However, guidelines are only useful if they are informed by team insights, which requires reflective practices.
- Rejection Reason: Creating guidelines might miss the opportunity for the team to reflect on the root cause, learn, and improve through collaboration and dialogue.
C) During the retrospective, discuss the issue and create an action plan to avoid it in the future
- Pros: This is the most Agile and Scrum-compliant option. The retrospective is specifically designed for the team to reflect on what went wrong, why it happened, and how to improve. The team can use this opportunity...
Author: Emma · Last updated Jul 9, 2026
A scrum team has conducted regular retrospectives to discuss immediate concerns and the implementation of improvement actions. Despite this, after a few iterations, the same concerns...
When the same concerns keep resurfacing in retrospectives despite the team discussing them and implementing improvement actions, it signals a deeper issue in the team's approach to retrospectives and continuous improvement. Let's analyze the options available to improve the retrospective outcomes:
A) Invited subject matter experts (SMEs)
- Pros: Subject matter experts can bring fresh perspectives or provide advice and insights on specific problems the team is facing. They could offer specialized knowledge that the team may not have.
- Cons: Inviting SMEs might be useful in some scenarios, but it's not directly aligned with the core purpose of retrospectives. The focus of retrospectives should be on the team’s internal reflection and self-improvement, not necessarily external experts. SMEs may provide solutions, but they won’t necessarily help the team identify or address systemic problems that are within their control.
- Scenario: This approach might be useful if the team is struggling with a specific technical or process-related issue that requires expertise beyond the team’s current knowledge. However, it doesn't help in identifying underlying patterns or root causes of recurring issues.
- Rejection Reason: The primary focus should be on improving team dynamics and processes through introspection rather than relying on external expertise. SMEs may offer short-term solutions but not long-term systemic change.
B) Conducted problem detections to determine root causes
- Pros: Identifying the root causes of recurring issues is key to breaking the cycle of repeated problems. A surface-level solution might resolve a symptom, but without addressing the underlying causes, the problem is likely to resurface. Root cause analysis helps the team understand why certain issues persist and design more effective solutions.
- Cons: This option might require more time and effort initially, as it involves digging deeper into problems rather than implementing quick fixes. However, the long-term benefits of tackling the root cause far outweigh the short-term time investment.
- Scenario: This is the most appropriate option for teams that are repeatedly facing the same issues. If the same problems are arising despite previous improvement actions, it's clear that a deeper examination of the issues is needed. Methods like the "5 Whys" or fishbone diagrams can be useful here.
- Rejection Reason: None. Root cause analysis is a fundamental technique in Agile and retrospectives, particularly when recurring issues are present.
C) Measured and reported the outcome of improvement actions to the team
- Pros: Tracking and reporting the outcomes of implemented actions ensures accountability and visibility into whether improvements are working. This...
Author: RadiantPhoenixX · Last updated Jul 9, 2026
During backlog refinement meeting, the new developer on the team asks the product owner to discuss a new performance threshold requirement and how ...
In this situation, a new developer on the team has raised an important point regarding a new performance threshold requirement and its potential impact on the stories in the backlog. It's important for the team to address this concern properly to ensure that any necessary changes to the backlog or stories are made in a way that preserves the integrity of the work while ensuring the performance requirements are met. Let’s evaluate the options:
A) Add this threshold requirement request as acceptance criteria in all impacted stories
- Pros: Adding the threshold as acceptance criteria in all impacted stories seems like a quick solution and ensures that the performance requirement is considered when accepting each story.
- Cons: This approach may not be sufficient without understanding the full impact of the performance threshold on the current stories. The team may need more information to assess how the requirement will affect the implementation of the stories. Simply adding the requirement to acceptance criteria without proper analysis might lead to incomplete or ineffective solutions. Additionally, it could result in incorrect assumptions about the complexity or scope of the change needed to meet the new threshold.
- Scenario: This could work in a scenario where the performance requirement is straightforward and well-understood, and the team is confident that simply adjusting the acceptance criteria is sufficient.
- Rejection Reason: Adding it directly to the acceptance criteria without investigating the full impact could result in a superficial approach that doesn’t adequately address the complexity of the change.
B) Create a spike story to analyze the impact of the threshold requirement on current stories
- Pros: Creating a spike is a great way to dedicate time for research and exploration. A spike story allows the team to investigate the impact of the new performance requirement in a focused, time-boxed manner. This ensures that the team can evaluate the technical challenges, assess how the requirement might impact the existing backlog, and identify the work needed to meet the performance threshold. After the spike, the team will have a clearer understanding of how to adjust the stories.
- Cons: A spike may delay the immediate progress of other stories, as it will require time and resources to investigate the issue. However, this time investment is crucial for making informed decisions about how to proceed, and the knowledge gained will pay off in the long term.
- Scenario: This is an ideal approach if the performance threshold is complex, if its impact on the current stories isn’t fully understood, or if the team needs more clarity before making decisions on how to adjust the backlog.
- Rejection Reason: None. Creating a spike is the most appropri...
Author: Aarav · Last updated Jul 9, 2026
What is the first thing an agile development team should do when planning an iteration?
When planning an iteration in an Agile development process, the first thing an Agile team should focus on is establishing the next sprint's goal. This step is crucial because it sets the direction for the team and provides a shared understanding of what needs to be accomplished in the upcoming iteration. Here's why the other options are either less relevant or inappropriate at this stage:
Option A: Assign the tasks to one team member
- Why it's rejected: Assigning tasks prematurely can lead to a lack of flexibility and may cause unnecessary micromanagement. It’s essential to focus first on understanding the broader goals and scope before diving into task assignments. The team should collectively discuss the tasks, the scope, and the necessary skills to complete them before making assignments.
Option B: Separate the stories into tasks
- Why it's rejected: While breaking down user stories into tasks is important, it should come after establishing the sprint goal. Without knowing the goal, the team might break down stories in ways that don't align with the overall objectives of the sprint. Also, if the goal isn't clear, some tasks may become irrelevant or less prioritized.
Option C: Estimate the stories' tasks
- Why it's rejected: Estimating should come after understanding the user stories and breaking them down into tasks. This helps...
Author: Amira · Last updated Jul 9, 2026
During a retrospective, team members suggest process improvement ideas. The agile team lead knows that, while many of these ideas are different from standard pr...
In this scenario, the best approach for the agile team lead is to encourage the team to try the ideas, even if failure may be the outcome. Here’s why:
Option A: Require the team to try only those ideas that will ensure success
- Why it's rejected: Agile is based on a mindset of experimentation, learning, and continuous improvement. Requiring only ideas that ensure success contradicts this philosophy. It undermines the value of testing new approaches and learning from failures, which are vital to Agile practices. The team should be empowered to experiment and learn, even if the outcome isn't guaranteed. This option is too risk-averse and limits innovation.
Option B: Allow the team to try ideas, but remind them that results will be reviewed by high-ranking executives
- Why it's rejected: While transparency is important, introducing the pressure of executive review could undermine the experimental nature of Agile. Team members may be less likely to suggest or try new ideas if they fear negative judgment from executives. The goal of a retrospective is to foster open communication and trust within the team, not to introduce external pressure that might inhibit creativity and growth. This option introduces unnecessary stress and could discourage risk-taking.
Option C: Associate idea successes and failures with the team's incentive plan to ensure accountability
- Why it's rejected: Tying the success or failure of process improvements to the team's incentive plan can create unintended consequences. It may shift the focus from learning and improvement to just achieving specific outcomes. The fear of failure could als...
Author: ThunderBear · Last updated Jul 9, 2026
During the implementation of a story, a scrum team notifies the scrum master of a technical challenge that is causing a del...
When a Scrum team encounters a technical challenge that is causing a delay, the Scrum Master should advise the team to create a spike to finalize the story's technical approach. Here's why:
Option A: Implement the story since the team is running behind schedule
- Why it's rejected: Rushing through the implementation without solving the technical challenge can result in poor quality and technical debt. The Scrum framework encourages delivering high-quality, potentially shippable increments at the end of each sprint. Pushing the team to complete the story without addressing the technical issue properly would likely compromise quality and increase risks later.
Option B: Create a spike to finalize the story's technical approach
- Why it's selected: A spike is a time-boxed research activity used to explore a technical problem, uncertainty, or complexity. This is the most appropriate response when the team encounters a technical challenge that is blocking progress. By creating a spike, the team can dedicate focused time to investigating and resolving the technical issue, which enables them to proceed with more confidence once the challenge is resolved. Spikes help the team gain clarity and make informed decisions, ensuring that the story can be completed successfully later. This solution aligns with the Agile principle of responding to change and uncertainty while maintaining a high level of technical integrity.
Option C: Transfer the story to a scrum team experienced in solving similar problem
- Why it's rejected: Transferring the story to another team may not always be the best solution. While other teams may have relevant expertise, the Scrum Team should ideally be self-sufficient and responsible for solving challenges within the scope of the sprint. Passi...
Author: Maya · Last updated Jul 9, 2026
The project team is ahead of schedule and beginning to gold-plate the feature included in the current spri...
When a project team is ahead of schedule and starting to gold-plate a feature (i.e., adding unnecessary enhancements or polishing beyond what is required), the best approach for the Agile Project Manager is to notify the product owner and have the product owner verify the backlog priority, then encourage the team to continue working on the backlog. Here's why:
Option A: Since the team has extra time, notify the product owner and secure approval for the extra work on this feature
- Why it's rejected: While it's important to inform the product owner, gold-plating typically adds unnecessary work that may not provide significant value. Approving additional work on the current feature might lead to diminishing returns, where the added effort isn't proportional to the value gained. Agile values delivering working software that meets the customer’s needs, not perfection or excessive refinement. Adding features without clear priority could disrupt the focus on what truly matters.
Option B: Encourage the team to document the improvement and prioritize it for the upcoming iteration, instead of building it now
- Why it's rejected: This option encourages the team to hold off on improvements, but it could lead to lost opportunities for delivering value within the current sprint. While documenting the improvement is a good idea for future consideration, the team is already ahead of schedule and has the capacity to address other backlog items. Pushing the team to document for later can be wasteful and delays progress on important work that needs to be done sooner.
Option C: Instruct the Scrum Master to have the team use the extra time to complete the extra feature work in the current iteration
- Why it's rejected: This option can lead the team do...
Author: Olivia · Last updated Jul 9, 2026
An agile team and a traditional development team are working together on a project. Each team exceeds expectations regarding deliverables; however, issues arise when ...
In this scenario, the best option for the agile practitioner is to foster stronger communication by hosting cross-organizational meetings between the two teams. Here's why:
Option A: Foster stronger communication by hosting cross-organizational meetings between the two teams
- Why it's selected: The issue seems to stem from integration difficulties, which are often caused by misalignments or misunderstandings between teams. Hosting cross-organizational meetings ensures that both teams have a clear, shared understanding of each other’s work, expectations, and challenges. These meetings can facilitate continuous feedback, align on integration strategies, and allow for troubleshooting integration issues in real-time. Communication is key, especially when teams with different methodologies (Agile vs. traditional) collaborate, as they may have different assumptions, workflows, and expectations. This approach promotes collaboration and creates a feedback loop to address any emerging issues.
Option B: Suggest merging the teams to avoid misunderstandings
- Why it's rejected: Merging teams may seem like a solution, but it could introduce significant challenges. Agile and traditional development practices are fundamentally different, and trying to merge the two teams could cause friction and reduce productivity, especially if there is no clear plan for how to integrate these two different methodologies effectively. It could lead to confusion, loss of autonomy, and even burnout. Instead, fostering communication and cooperation between the teams is more effective than forcing a merger that may not address the root cause of integration issues.
Option C: Create stories from full technical specifications to avoid ambiguity
- Why it's rejected: While creating detailed specifications might seem like a way to prevent ambiguity, it goes against Agile principles,...
Author: SilverBear · Last updated Jul 9, 2026
The executive leadership wants to understand ways to better deliver on time and on budget.
What can the project team...
To achieve the organizational goal of delivering projects on time and on budget, the project team should focus on strategies that enable continuous improvement, proactive issue management, and accountability. Let’s evaluate each option based on these objectives:
Option A: Maintain and review a lessons learned repository to improve delivery of future projects
Reasoning:
Maintaining a lessons learned repository allows the project team to capture valuable insights from completed projects, including what worked well and what didn’t. By systematically reviewing and applying these lessons to future projects, teams can avoid past mistakes, streamline processes, and improve delivery timelines and budget management. This approach builds on the knowledge accumulated over time and enhances decision-making, which is essential for long-term improvement.
Scenario:
This approach is particularly useful in organizations with a history of recurring challenges, where knowledge sharing and standardizing good practices can significantly improve efficiency. It also supports a culture of continuous improvement and helps in setting realistic project expectations based on previous experiences.
Option B: Ask each team member to post corrective action to the backlog
Reasoning:
While encouraging team members to identify corrective actions can be valuable for addressing issues during a project, posting corrective actions to the backlog is more reactive and may not necessarily lead to immediate resolution or prevent similar issues from arising in future projects. This option may delay resolution as it requires prioritization and may only address symptoms of problems rather than root causes.
Scenario:
This approach could be useful in environments where issues are emerging rapidly during the project execution phase. However, it may not help in creating a proactive culture that focuses on long-term improvements. It could also overwhelm the backlog if not managed properly.
Option C: Engage the project management office (PMO) to take responsibility for identifying lessons learned on projects
Reasoning:
While the PMO can play a crucial role in cap...
Author: ShadowWolf101 · Last updated Jul 9, 2026
A new agile team ember notices that the team's current process involves excessive documentation.
Wh...
When a new agile team member notices that the team's process involves excessive documentation, the best course of action is to address this issue in a way that aligns with agile principles—particularly focusing on delivering value over adhering to unnecessary processes. Let’s evaluate each option:
Option A: Teach the team the appropriate agile principle, obtain consensus, and drive adoption
Reasoning:
This option aligns directly with agile values and principles, which prioritize working software, collaboration, and flexibility over rigid processes and documentation. The new team member can help the team understand that excessive documentation may hinder progress and slow down delivery. By teaching the team the value of "working software over comprehensive documentation" and encouraging open dialogue, the team can align on what documentation is truly necessary and what can be streamlined or eliminated.
Scenario:
This approach is most appropriate when the team has room for improvement in its understanding of agile principles or when there’s a need to realign the team to core agile values. It fosters collaboration, ensures that everyone is on the same page, and can lead to a more efficient process.
Option B: Allow another team member to prepare those documents that do not appear to bring value
Reasoning:
While this option seems like a quick solution, it doesn’t address the root cause of the issue—the team’s overall process and mindset towards documentation. Passing the responsibility to another team member doesn’t solve the core problem, which is the excessive documentation itself. Moreover, it could lead to inefficiencies or even frustration within the team, as the fundamental issue remains unresolved.
Scenario:
This approach might work temporarily to reduce some documentation workload, but it’s not a sustainable or collaborative solution. It would be more effective in a scenario where the team member is simply looking for relief from excess work, but it won’t lead to the necessary process change.
Option C: Notify the project manager about other documentation techniques, and identify which documents bring value and which do ...
Author: MysticJaguar44 · Last updated Jul 9, 2026
A team working with a new technology faces a significant amount of uncertainty about its ability to deliver stories ...
When a team is facing significant uncertainty due to technical issues while working with new technology, the best approach is one that addresses the risks, promotes visibility, and encourages proactive problem-solving. Let’s evaluate each option:
Option A: Capture risks and make them visible, and use a burndown chart to focus on reducing risks early in the project
Reasoning:
This is a highly agile approach. By capturing risks early and making them visible, the team can be proactive in managing uncertainties. A burndown chart is a great tool for tracking progress, but it can also be used to visualize and reduce risks over time. This approach ensures that the team keeps the focus on mitigating issues that might prevent successful delivery and can identify potential roadblocks early, allowing for course corrections.
Scenario:
This approach is ideal when the team is working on complex or uncertain tasks. It ensures that risks are tracked as part of the process, and the team can address them as they arise, rather than waiting until it’s too late. It’s particularly effective in fast-paced, high-uncertainty environments.
Option B: Ask the scrum master to extend the sprint's duration to allow more time to work through technical issues
Reasoning:
Extending the sprint duration may seem like an immediate fix, but it’s not in line with agile principles, which emphasize regular, consistent delivery and the ability to respond quickly to change. Extending the sprint could create a false sense of security and delay addressing the root causes of technical issues. It may also lead to sprint fatigue or undermine the team’s ability to adapt and solve problems quickly.
Scenario:
This option might be useful if the team is genuinely struggling with a technical bottleneck and there’s a critical need to finish specific tasks within a certain timeframe. However, it’s not recommended as a general solution because it disrupts the rhythm of regular sprint cycles and does not address the underlying risks effectively.
Option C: Place the impacted stories on the storyboard, and use daily standups to make the product owner aware of the technical issues
...
Author: Benjamin · Last updated Jul 9, 2026
Unable to meet a sprint's committed velocity, an agile team approaches the agile coach to define the next sprint...
When an agile team is unable to meet a sprint's committed velocity, the key issue likely revolves around either over-committing in the past or an unrealistic expectation of what can be accomplished within a sprint. The agile coach’s advice should focus on fostering a sustainable, realistic approach to planning future sprints while addressing underlying issues. Let’s analyze each option:
Option A: Split each story into multiple stories to meet the desired velocity
Reasoning:
While splitting stories into smaller ones might seem like a solution to increase the number of stories completed in the sprint, it doesn't solve the underlying problem of over-committing or inaccurate estimation. Splitting stories just for the sake of increasing velocity can lead to artificially inflating numbers and misrepresenting the team’s true capacity. It may also result in more fragmented work, which can reduce the overall quality or coherence of the sprint deliverables.
Scenario:
This approach might be tempting when trying to "catch up" to the desired velocity, but it’s not sustainable in the long run. It may work in the short term if the stories are truly independent and can be broken down meaningfully. However, it risks distorting the actual work that needs to be done.
Option B: Set the velocity to the delivered story points of the last sprint
Reasoning:
This is the most sensible and realistic option. The velocity of the last sprint reflects the team’s actual capacity and performance, taking into account any challenges faced during that sprint (such as technical difficulties, blockers, or other constraints). Setting the next sprint’s velocity based on this number aligns future expectations with actual performance and avoids over-committing. It’s also an iterative approach that allows for continuous improvement over time.
Scenario:
This approach is ideal when the team is still adjusting to a new environment or facing challenges in estimating capacity. By using the actual velocity from the last sprint, the team can set a more achievable target for the next sprint, ensuring that the workload is appropriate to their real capacity and focusing on sustainable delivery.
Option C: Use different estimation methods for stories and...
Author: Noah Williams · Last updated Jul 9, 2026
After seeing the planned features for an upcoming release, a customer notes that a vitally important and complex one is missing. The team estimates that this feature sig...
When a customer highlights a missing but vitally important and complex feature for an upcoming release, the team must address this in a way that balances customer needs with the team's capacity. The key is to ensure the feature is delivered while maintaining the integrity of the agile process. Let’s evaluate each option:
Option A: Break down the feature into smaller parts, and commit to complementing the minimum value product
Reasoning:
This is an excellent solution because breaking down a complex feature into smaller, manageable parts aligns with the agile principle of delivering incremental value. By decomposing the feature, the team can focus on delivering the most important, valuable portions first. This also allows the team to adjust their plans to meet the customer’s needs while respecting their velocity constraints. The team can ensure that the minimum viable product (MVP) is met by delivering value as early as possible.
Scenario:
This is ideal when the feature is critical, but its complexity exceeds the team’s capacity in the short term. Breaking it down ensures that the customer gets value incrementally, and the team doesn’t overcommit to an unrealistic workload. It’s most useful in a scenario where the feature is indeed vital but can be delivered in phases.
Option B: Complete the iteration to which they have already committed, and include the feature in the next release
Reasoning:
While this option respects the team’s current commitments, it may delay the delivery of a key feature that is vital to the customer. Waiting until the next release could lead to dissatisfaction if the feature is a priority for the customer. It’s also not the most agile response, as it doesn’t focus on delivering value sooner, especially when the team has the ability to adjust.
Scenario:
This might work if the feature isn’t immediately critical, or if there’s enough time between releases. However, it’s not ideal when the feature is considered essential by the customer and would significantly impact their experience or expectations.
Option C: Change the planned features to inc...
Author: Noah · Last updated Jul 9, 2026
During an iteration planning meeting, the team suggests changes to add product vale that will require extra work and impact t...
When the team suggests changes that will add product value but impact the schedule, the Agile project leader must weigh several factors, including the project's overall objectives, customer needs, team capacity, and the product owner's input. Let's break down each option and explore the reasoning behind selecting the best course of action.
A) Re-estimate the project
- Reasoning: This option involves revisiting the timeline and cost estimates to account for the changes. This is useful if the team believes the changes will significantly alter the scope, effort, or resources required. Re-estimating helps the team understand the impact of the changes and provides more clarity to both stakeholders and the development team.
- When to use: If the scope of the changes is substantial and affects the schedule, resources, or overall project goals, re-estimating the project will give a clear view of what adjustments need to be made.
- Drawbacks: This option can lead to delays if the re-estimation process is lengthy, and it could be seen as a redirection of focus away from delivering value quickly. If not handled properly, it might frustrate the team or stakeholders.
B) Finish the product as it was initially planned
- Reasoning: This option implies that the project will proceed according to the original plan, without incorporating the suggested changes. This could be the best option if the changes are deemed unnecessary or if it is critical to deliver on time without deviating from the initial scope.
- When to use: Use this option if the suggested changes don’t offer sufficient value or if the schedule and product delivery deadlines are non-negotiable.
- Drawbacks: Rejecting valuable changes may lead to a product that doesn’t meet the most current customer needs, potentially decreasing product value. It might also affect stakeholder satisfaction if they believe the changes should be prioritized.
C) Try to include as many changes as possible
- Reasoning: This option suggests a more flexible, "yes-man" approach, where the team tries to accommodate...
Author: StarlightBear · Last updated Jul 9, 2026
Why should an agile coach model agile principles and behaviours, become self-aware, and be present?
When it comes to why an Agile coach should model Agile principles, become self-aware, and be present, the essence of the role is about facilitating and guiding teams through a transformation rather than directing or controlling. Let’s analyze each of the options and the key factors that drive the most effective choice:
A) To better listen, serve, and help the team grow their strengths individually and as a team
- Reasoning: This option aligns with the core values of Agile, which emphasize collaboration, individual empowerment, and continuous improvement. An Agile coach who is self-aware and present is more attuned to the team's needs, allowing them to foster an environment of trust and psychological safety. By modeling the principles of Agile, the coach is able to better listen, serve, and help the team unlock its full potential. The focus is on helping the team grow, both individually and collectively, which is essential for building high-performing teams.
- When to use: This is the foundational role of an Agile coach and applies in all situations where the goal is to build a collaborative, self-organizing team that can work together effectively and improve continuously.
- Drawbacks: There are no significant drawbacks to this approach, as it embodies the true purpose of an Agile coach—facilitating growth rather than imposing solutions.
B) To convince people what they need to do
- Reasoning: This option suggests that the Agile coach's role is to convince or persuade the team about specific actions or behaviors. While coaching may involve some influence, the role of an Agile coach is not about telling people what to do but about empowering the team to make decisions, discover their own solutions, and own the process.
- When to use: This approach could be seen in more directive environments or with teams new to Agile, but it is not aligned with true Agile principles. Agile values self-organization and empowerment, and convincing someone what to do contradicts these principles.
- Drawbacks: The coach can easily slip into a command-and-control approach, stifling the team's autonomy and initiative. It could also damage trust between the coach and the team, as the coach becomes more of a dictator than a facilitator.
C) To help better disguise the command and control approach
- Reasoning: This option suggests that the coach would attempt to disguise a command-and-cont...
Author: GlowingTiger · Last updated Jul 9, 2026
There is a database feature requiring three members of a seven person team. A meeting is scheduled at the beginning of the sprint to go over technical needs to c...
When a Scrum Master is planning a meeting at the beginning of a sprint to go over technical needs for a feature, the goal is to ensure that the team has the necessary knowledge, understanding, and clarity about the work to be done. It is important to invite the right people to ensure that all aspects of the technical requirements and the product goals are clear. Let’s evaluate the options:
A) The core team and the customer
- Reasoning: The core team should be included because they are the ones responsible for completing the technical work. The customer, however, is not typically involved in detailed technical discussions unless the product owner believes that their input is needed at a high level. The customer might be more interested in the outcome of the sprint rather than the specific technical details of a feature.
- When to use: This could work if the customer is involved in providing direct feedback on the product’s functionality or if the team needs a strong understanding of the customer's perspective on the technical feature. However, this is more common in review meetings than in technical meetings.
- Drawbacks: Inviting the customer could lead to a less focused meeting on technical details and cause confusion if the customer doesn't have a technical background. It could also create unnecessary pressure to explain things at a higher level.
B) The product owner and key stakeholders
- Reasoning: The product owner should always be included because they are responsible for ensuring the team understands the priorities and requirements of the feature. However, key stakeholders may not be necessary unless their input is essential for the technical decisions at hand. The product owner has a solid understanding of the user needs, and they act as the bridge between stakeholders and the development team.
- When to use: This would be a good choice if the meeting involves alignment on business priorities or if there are specific stakeholders whose input could help clarify the feature. However, in a purely technical meeting, key stakeholders are often not required unless they have specialized knowledge that is relevant to the task.
- Drawbacks: Having too many stakeholders can clutter the conversation with non-technical feedback that is not necessary for the technical work at hand.
C) The customer and the spons...
Author: Maya · Last updated Jul 9, 2026
As user stories are developed, what should be done to record and update acceptance criteria?
In Agile, acceptance criteria play a crucial role in defining what is required for a user story to be considered complete. As the user stories are developed, it’s important to ensure that the acceptance criteria are clear, updated, and aligned with the evolving requirements. Let’s analyze each option and determine the best course of action:
A) Add more user stories
- Reasoning: Adding more user stories could be part of backlog refinement if the original user story has evolved or if new requirements emerge. However, acceptance criteria are tied to the specific user story rather than being a reason to add new user stories. Simply adding more stories doesn't necessarily address the need to update or refine the acceptance criteria.
- When to use: This option is useful when new functionality or additional features emerge, but it doesn't directly address updating acceptance criteria for existing stories.
- Drawbacks: Adding more user stories without revisiting and refining acceptance criteria might result in incomplete or misaligned requirements. This doesn't solve the issue of ensuring the current stories are correctly defined.
B) Use sprint retrospectives
- Reasoning: Sprint retrospectives are focused on improving the team's processes and collaboration, not on refining specific user stories or their acceptance criteria. While retrospectives can help the team reflect on what’s working and what’s not, they are not the right forum for updating acceptance criteria.
- When to use: Sprint retrospectives are valuable for addressing process-related issues like how to improve communication, sprint planning, or how to handle roadblocks. It’s not the place to update or document acceptance criteria for user stories.
- Drawbacks: Retrospectives are not focused on the technical details of the work. They are unlikely to provide the right context for refining user stories and their acceptance criteria.
C) Update current user stories
- Reasoning: This is the most appropriate option. As user stories evolve or are further developed, the acceptance criteria should be updated to reflect any changes in the requirements or understanding of the feature. The product owner, in collaborati...
Author: RadiantJaguar56 · Last updated Jul 9, 2026
Midway through a two-week sprint, an agile team realizes that the features cannot be delivered within the sprint. The team determines that another week will be r...
In Agile, the team is committed to delivering the agreed-upon work within the sprint timebox. However, if the team realizes midway through the sprint that they won’t be able to deliver the committed features, it’s important to reflect on the situation, identify root causes, and make decisions that ensure sustainable work practices. Let's evaluate each option in detail:
A) Plan for overtime, and include the effort as part of the estimation
- Reasoning: Planning for overtime might seem like a quick solution to meet deadlines, but it is not sustainable. Agile practices emphasize sustainable pace, which means the team should avoid working excessive hours over long periods, as it can lead to burnout and decreased productivity in the future. Moreover, overtime is not considered a best practice in Agile, as it can create unhealthy work environments and may reduce overall team morale.
- When to use: This might be used in urgent situations where external deadlines force the team to push through, but it’s not recommended as a long-term solution in Agile environments.
- Drawbacks: Overtime can lead to burnout, affect quality, and harm team morale. It also doesn't address the root cause of the issue. Estimating with overtime may give a false sense of security but doesn’t solve the underlying problems with planning or capacity.
B) Increase team velocity to deliver more story points
- Reasoning: While the goal of increasing velocity is often discussed in Agile, it’s important to understand that velocity is a reflection of the team’s capacity and ability to deliver based on previous performance. Trying to artificially increase velocity mid-sprint to catch up may lead to over-commitment, poor-quality work, and is not sustainable. Velocity increases naturally over time as the team improves, but it shouldn’t be forced to meet a short-term deadline.
- When to use: Velocity increases through continuous improvement, better planning, and team collaboration, but it’s not something that can be artificially accelerated mid-sprint.
- Drawbacks: Trying to increase velocity by pushing the team too hard can lead to lower quality, missed deadlines, and team burnout. It also doesn’t address the root cause of the problem.
C) Identify the reason for over-commitment to the sprint and create an action plan for the following sprint
- Reasoning: This option aligns with the Agile principle of continuous improvement. If the team is unable to complete the sprint's work, it’s essential to understand why this happened, whether it was due to unrealistic estimates, scope creep, unclear req...
Author: Noah · Last updated Jul 9, 2026
On what should an agile team work to achieve predictable flow?
In an Agile team, achieving predictable flow involves ensuring that work moves smoothly through the system, reducing delays, and providing consistent throughput. Each of the options you provided has its own merits, but we need to identify the one that most directly impacts flow predictability, considering key Agile principles such as reducing complexity, limiting work in progress, and focusing on delivering value frequently. Let's analyze each option in this context:
A) Small user stories
- Reasoning: Smaller user stories are easier to estimate, implement, and deliver within short iterations (sprints). They help teams break down large, complex features into manageable pieces, which reduces uncertainty and enables more predictable delivery. The smaller the story, the easier it is to understand the scope and avoid scope creep.
- Scenario Use: This option is best when trying to streamline delivery and reduce delays caused by large, unwieldy user stories.
- Key Factors: Reduces complexity, easier to estimate, quicker delivery, and lower risk of blockages.
B) Simple acceptance criteria
- Reasoning: Simple acceptance criteria define clear expectations for what constitutes "done" for a given user story. While this is essential for quality and alignment, it doesn't directly influence flow as much as smaller, more manageable user stories. Clear acceptance criteria can improve quality and reduce rework, but it may not be the key factor in achieving predictable flow.
- Scenario Use: This option is best for improving quality and ensuring clear communication, but its impact on flow predictability is less significant.
- Key Factors: Clarifies what needs to be done but doesn't directly reduce cycle time or help in creating predictable flow.
C) Lean features
- Reasoning...
Author: Lina Zhang · Last updated Jul 9, 2026
An agile team has been given a complex project with a basic set of requirements which need further elaboration and review.
How should the team iterati...
When an Agile team is given a complex project with a basic set of requirements, and these requirements need further elaboration and review, the team needs to adopt an approach that facilitates ongoing collaboration with stakeholders while ensuring that the backlog evolves as more details become clear. Let’s evaluate the options provided:
A) Conduct a requirement gathering workshop
- Reasoning: A requirements gathering workshop involves bringing key stakeholders together to collaboratively identify and elaborate on requirements. This is a highly effective approach in Agile since it emphasizes collaboration, shared understanding, and the ability to immediately address any questions or ambiguities. The workshop format allows for a dynamic conversation where both the team and the stakeholders can explore and clarify details iteratively, ensuring that the backlog is built in an adaptive, collaborative manner.
- Scenario Use: This option is ideal at the beginning of the project and can be repeated iteratively throughout the project to refine requirements as needed. It enables ongoing interaction and flexibility, especially in cases where requirements are vague or evolving.
- Key Factors: Collaboration, shared understanding, rapid clarification, iterative refinement.
B) Deliver the basic requirements iteratively
- Reasoning: Delivering the basic requirements iteratively means starting with the simplest, high-level requirements and then progressively elaborating and refining them. This approach works well in Agile, as it allows for continuous feedback and improvement over time. However, this option is more about how to deliver than about how to gather or refine the backlog. While iterative delivery can help refine requirements over time, it doesn’t directly address the need for initial collaboration and clear backlog creation upfront.
- Scenario Use: This option is suitable after the initial backlog creation, where the team begins implementing basic features and gathers feedback to refine the backlog.
- Key Factors: Continuous feedback, learning by doing, but lacks structured upfront collaboration to flesh out the details.
C) Have the product owner fill out the requirements backlog
- Reasoning: The product owner is responsible for maintaining the backlog and prioritizing it, but ...
Author: Zara · Last updated Jul 9, 2026
A scrum master is part of a project team using technologies overseen by the IT department. The IT director oversees several company initiatives and is unfamiliar with the details of each one.
A...
In a Scrum environment, different meetings serve specific purposes for team collaboration, alignment, and feedback. Given the context where the IT director is an active stakeholder but may not be deeply familiar with the project details, the best option for inviting the IT director should allow them to gain insight into the progress and outcomes of the project without overwhelming them with too much detail or frequency. Let’s evaluate each option:
A) Planning
- Reasoning: The Sprint Planning meeting is where the team sets the objectives for the upcoming sprint and decides which backlog items they will focus on. This meeting is highly detailed and involves deep discussions about tasks, priorities, and dependencies. Since the IT director oversees multiple initiatives and may not be familiar with the specific technical details, this meeting may be too granular and time-consuming for them. Additionally, their presence in planning could shift the focus away from the team's direct decision-making and lead to unnecessary complexity.
- Scenario Use: While they could be invited to ensure alignment on high-level priorities, this meeting might not be the best fit since it involves in-depth technical and task-level discussions that may not be necessary for the IT director.
- Key Factors: High level of detail, team-focused, and might be overwhelming for someone not familiar with the specifics of the project.
B) Daily Scrum
- Reasoning: The Daily Scrum is a 15-minute stand-up meeting where team members share their progress, challenges, and next steps. It’s designed to be quick and focused on the team's immediate work. The IT director’s attendance at this meeting would likely be unproductive, as the discussions are typically tactical and operational, not strategic. Additionally, since the IT director oversees several initiatives, attending these meetings daily would be inefficient and may not provide the strategic value they are looking for.
- Scenario Use: This option is not ideal for an executive stakeholder like the IT director, as they do not need to be involved in the day-to-day operational updates unless there’s an escalated issue.
- Key Factors: Brief and tactical in nature, not suited for high-level oversight or ...
Author: Amelia · Last updated Jul 9, 2026
A globally distributed project team is using email and phone calls as the only way to share information. Delays in resolving issues often occur due to misinterpreted communications, leading to a lower ...
When managing a globally distributed project team, the primary challenge is ensuring effective communication across different time zones, cultures, and communication platforms. The current reliance on email and phone calls can lead to delays, misinterpretations, and a lack of real-time collaboration, all of which negatively impact team velocity. Let’s evaluate each option based on its ability to address the root causes of poor knowledge sharing:
A) Meet individually with each team member to identify the issues and relay information to the remaining members through status reports
- Reasoning: This option involves a highly centralized approach where the project leader gathers information from individual team members and then communicates it to others. While this may address some communication gaps, it introduces several problems:
1. It still relies on the project leader as the central communication hub, creating bottlenecks and delays.
2. Status reports are typically one-way communication and lack the collaborative, real-time engagement needed to resolve issues quickly.
3. It doesn’t address the fundamental issue of team collaboration and knowledge sharing.
- Scenario Use: This could be a short-term solution to gather insights but does not improve the overall communication process and team collaboration.
- Key Factors: Centralized, slow, and one-way communication that limits team interaction and problem-solving.
B) Establish a live video feed between the dispersed teams to enable spontaneous engagement and collaboration on issues
- Reasoning: This option directly addresses the core issue of delayed communication and misinterpretation by fostering real-time engagement among team members. A live video feed or a similar synchronous communication tool (such as video conferencing platforms like Zoom, Teams, or Skype) allows for immediate clarification of misunderstandings, spontaneous collaboration, and quicker resolution of issues. It also enables face-to-face interaction, which can improve the quality of communication and strengthen team cohesion, even across different locations.
- Scenario Use: This is the most effective solution for improving knowledge sharing because it encourages real-time problem-solving and reduces the delays caused by asynchronous communication methods like email. It's particularly beneficial for teams who need to resolve issues quickly and efficiently across time zones.
- Key Factors: Real-time, collaborative, reduces miscommunication, and fosters engagement.
C) Request that the custom...
Author: Liam · Last updated Jul 9, 2026
How can a scrum team obtain more feedback from a minimally responsive outside stakeholder?
When working with a minimally responsive outside stakeholder, it’s essential to find a balance between gathering useful feedback and respecting the stakeholder’s time and availability. The challenge is to encourage more engagement without overwhelming or pressuring the stakeholder. Let’s examine each option and determine which one is most effective:
A) Keep sprints short
- Reasoning: Shorter sprints typically increase the frequency of feedback cycles and may improve the likelihood of receiving timely input from stakeholders. However, while this could encourage quicker turnaround for feedback, it does not directly address the issue of minimally responsive stakeholders. If the stakeholder is already not highly engaged, shortening sprints might just lead to more frequent, but still unresponsive, opportunities for feedback without necessarily improving their participation.
- Scenario Use: This option could work well if the stakeholder is generally responsive but just needs more frequent touchpoints. However, if the issue is a lack of availability or interest in engagement, simply shortening sprints won’t solve the problem.
- Key Factors: May increase frequency of feedback, but doesn’t address responsiveness directly.
B) Invite the stakeholder to the daily stand-ups
- Reasoning: Inviting the stakeholder to daily stand-ups might seem like a good way to get constant feedback, but it’s not an effective approach in Agile. The Daily Stand-up is a short, focused meeting for the team to synchronize their work and remove blockers. It’s not designed to involve external stakeholders, especially ones who may not be actively engaged. Furthermore, daily meetings can be seen as burdensome or unnecessary for stakeholders who are not deeply involved with day-to-day tasks, possibly leading to reduced responsiveness or even frustration.
- Scenario Use: This option is not suitable for a minimally responsive stakeholder as it could overwhelm them with unnecessary meetings and won’t lead to meaningful feedback.
- Key Factors: Not a good fit for external stakeholders, leads to potential frustration or disengagement.
C) Ask the stakeholder for estimates for each user story
- Reasoning: Asking a minimally responsi...
Author: RadiantJaguar56 · Last updated Jul 9, 2026
An agile team has only one database administrator with the necessary knowledge of database-related tasks. The project manager identifies the risk that if this person leaves, ...
Key Considerations for Selection:
- Risk of Knowledge Loss: The primary risk here is the loss of a key person with specialized knowledge, and the potential for a significant decrease in team velocity.
- Team Dependency: The team is currently dependent on this individual for their expertise.
- Knowledge Transfer: The need for the team to build knowledge and skill in database management so that they are less dependent on the sole database administrator.
- Impact on Team Velocity: Any action taken should minimize the impact on team performance and ensure that the team can continue delivering without significant disruption.
- Long-Term Sustainability: Solutions should address the risk of future dependency on a single individual in the long term.
Option Evaluation:
A) Start the hiring process for a new, equally skilled database administrator as a replacement
- Pros: This ensures continuity by replacing the key person with another who can take over the specialized work.
- Cons: Hiring takes time, and the new hire may not immediately fit in with the team’s culture and processes. There's also the risk of not finding an equally skilled replacement quickly, which could still leave the team vulnerable.
- Conclusion: While this is a reasonable long-term solution, it doesn’t address the immediate knowledge sharing and team dependency issues. It's a reactive solution rather than proactive.
B) Move this database administrator to another team so that team members learn database-related tasks
- Pros: This helps spread the knowledge to the rest of the team, making the team less dependent on one individual.
- Cons: Moving the database administrator could cause a temporary reduction in team velocity, as the administrator will no longer be available to contribute fully to their current team’s database tasks. Furthermore, the rest of the team may not immediately be able to take over such a specialized role.
- Conclusion: While knowledge transfer is important, this approach could create more immediate risks, such as reduced prod...
Author: Arjun · Last updated Jul 9, 2026
An agile team is working well together, but productivity has been flat.
What can the project leader...
Key Considerations for Selection:
- Team Morale and Collaboration: Since the team is already working well together, it's crucial not to disrupt their dynamics unnecessarily but rather focus on fostering continuous improvement and productivity without overburdening them.
- Root Causes of Stagnation: Understanding why productivity has plateaued is key—whether it's due to technical issues, process inefficiencies, or something else.
- Sustainable Improvement: Solutions should be aimed at long-term improvement rather than short-term boosts that may not be sustainable.
- Team Autonomy and Engagement: Solutions that empower the team to identify their own areas of improvement are likely to result in more sustainable and self-driven growth.
Option Evaluation:
A) Review the burndown chart to identify ways to increase efficiency
- Pros: Reviewing the burndown chart helps the team visualize progress, identify bottlenecks, and adjust their workflow to improve efficiency. It is a data-driven approach.
- Cons: Focusing solely on the burndown chart might overlook other factors affecting productivity, such as team morale, skills gaps, or external dependencies. Also, it may give the impression that the team is being micromanaged rather than empowered to find their own solutions.
- Conclusion: While useful, this is more of a diagnostic tool rather than a solution to drive improvement. It lacks a focus on the team's autonomy or collective engagement in improving their work process.
B) Chair a weekly team retrospective focusing on identifying areas for continuous improvement
- Pros: Retrospectives are a core agile practice that directly fosters a culture of continuous improvement. By having regular retrospectives, the team can openly discuss challenges, identify root causes for stagnation, and agree on actionable improvements. It empowers the team to take ownership of their performance and fosters team engagement.
- Cons: If not managed well, retrospectives can become repetitive or result in vague action items that aren't fully implemented. The quality of the retrospective is crucial to its success.
- Conclusion: This option is highly effective because it directly involves the team in their own improvement process. It is both short-term (actionable insights) and long-term (cultivates a culture of continuous improvement). This option ...
Author: Oliver · Last updated Jul 9, 2026
A new CIO advocates an agile framework for new IT projects, but the team has reservations.
How should the CIO...
Key Considerations for Selection:
- Team Buy-in: Since the team has reservations, the CIO should focus on gaining team support and understanding of agile, rather than enforcing it.
- Cultural Change: Implementing an agile framework often requires a shift in mindset. Any change should support and encourage collaboration rather than feeling like a top-down mandate.
- Experimentation and Flexibility: Teams may be more open to change if they have an opportunity to experiment and adjust based on their experiences, rather than being required to follow a rigid new process from the start.
- Sustainability: Any action taken should ensure long-term adoption and alignment with agile values, not just a short-term push.
Option Evaluation:
A) Obtain executive team buy-in by conducting a meeting to present the advantages of agile principles and processes
- Pros: Securing executive buy-in is crucial for supporting any large-scale change initiative. This option ensures the leadership team is aligned, which can help with resource allocation, support, and overcoming resistance.
- Cons: While important, this doesn’t directly address the team’s reservations. The team is the one that will have to implement agile, so they need to be convinced, not just the executive team.
- Conclusion: This is a good step for overall support, but it’s not sufficient on its own to ensure alignment with the team that will be doing the work.
B) Issue a memo of understanding that agile principles should be implemented for all new projects
- Pros: It is a clear, top-down directive that mandates agile implementation across projects. It could be a good tool to formalize the expectation.
- Cons: This approach may create resistance, particularly from a team that is already hesitant. It doesn't foster engagement or understanding; rather, it imposes a change, which might cause resentment or disengagement. Teams may be more likely to follow the process reluctantly, and it could affect long-term success.
- Conclusion: While a memo can communicate the decision, it fails to address the core issue: getting team buy-in and ensuring the team is ready and motivated to adopt agile principles.
C) Introduce agile principles and processes, then make the...
Author: Ava · Last updated Jul 9, 2026
An agile team is unable to complete all its planned sprint user stories, which results in a decrease of its pl...
Key Considerations for Selection:
- Accurate Velocity Measurement: Velocity should reflect the team's actual capacity and performance, not artificially inflated numbers.
- Continuous Improvement: The team needs to identify the root causes of the decrease in velocity and make adjustments to improve future performance.
- Prioritization and Adaptation: Any approach should focus on helping the team adjust and plan more effectively in the future, rather than forcing changes that mask underlying issues.
- Sustainability: Any solution should be sustainable in the long term, ensuring that the team maintains realistic expectations about their capacity and can plan appropriately for future sprints.
Option Evaluation:
A) Re-estimate the sprint's completed stories to increase and adjust the sprint's velocity
- Pros: Adjusting the velocity to reflect completed stories may seem like a quick way to maintain the team’s apparent performance.
- Cons: This is not an honest reflection of the team’s actual capacity. Re-estimating completed stories just to artificially inflate velocity creates a misleading picture of the team's ability and could distort future sprint planning. It doesn’t address the root cause of the problem and can lead to incorrect expectations.
- Conclusion: This is not a sustainable or honest solution. It would undermine the purpose of velocity as a metric for predicting future sprint capacity.
B) Increase the duration of the next sprint to accommodate the incomplete user stories and maintain velocity
- Pros: Extending the sprint might allow for the completion of unfinished work, potentially preventing any disruption to the flow of the project.
- Cons: Increasing the sprint duration goes against agile principles of time-boxing, which emphasizes working in fixed iterations to provide predictability and focus. It could lead to scope creep and unhealthy work habits by allowing too much flexibility, ultimately impacting the team’s ability to deliver consistently over time.
- Conclusion: This approach is not aligned with agile best practices, as it r...
Author: Leah · Last updated Jul 9, 2026
An agile project leader is delivering a team kick-off session. The first exercise is a `Life Timeline` `" a story-telling exercise where each team member tells their life story, explains how they experienced the highs and lows of...
Key Considerations for Selection:
- Trust and Vulnerability: The exercise described is highly personal and invites team members to be open about their life journeys, which requires a significant level of trust and vulnerability.
- Team Dynamics: For the team to work effectively together, there needs to be a foundation of trust and mutual understanding. This foundation allows for more open communication, better problem-solving, and increased collaboration.
- Agility and High-Performance Teams: Agile teams thrive on collaborative relationships, where individuals feel comfortable taking risks, sharing ideas, and supporting one another. The exercise should help create this environment.
- Personal Insights: The goal is to understand not only professional strengths and weaknesses but also personal histories and emotional experiences that can influence team dynamics.
Option Evaluation:
A) A safe space for team members to learn to trust one another, leading to collaborative relationships
- Pros: Trust is the cornerstone of effective collaboration. By sharing personal stories, team members begin to see each other as people, which can build empathy and foster a collaborative environment.
- Cons: While trust is important, this option doesn’t capture the full essence of what the "Life Timeline" exercise aims for. The exercise encourages deeper vulnerability, which isn’t just about trust—it’s also about openness and emotional connection, not just collaboration.
- Conclusion: This is a solid option, but it underestimates the role of vulnerability and emotional openness in building high-performance relationships.
B) A safe space to team members to learn to be vulnerable, leading to high-performance relationships
- Pros: This option directly addresses vulnerability, which is central to the "Life Timeline" exercise. Being open about personal experiences and emotions is a powerful way to create authentic connections. When team members are vulnerable, it leads to stronger, more high-performance relationships based on trust and understanding.
- Cons: While this option accurately captures the essence of the exercise, it could be ...
