The correct answer is B - Have team members work in pairs to learn from each other and develop new skills.
Pairing encourages collaboration, knowledge sharing, and skill development, which helps reduce dependency on specific individuals and enhances engagement through variety.
From the PMI Agile Practice Guide:
"Pair programming and other collaborative work methods help reduce repetition, promote learning, and improve motivation. These techniques allow for shared ownership and skill diversity." (PMI Agile Practice Guide, Section 4.3 - Continuous Learning and Team Development) Mike Griffiths adds:
"Cross-training and pairing reduce boredom, eliminate knowledge silos, and increase team flexibility. They are effective responses to reduced motivation from repetitive work." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 - Continuous Improvement) Incorrect options:
* A may temporarily help morale but doesn't address the root cause.
* C is more suitable for analyzing inefficiencies, not directly resolving monotony.
* D adds cost and doesn't solve the underlying engagement problem.

The correct answer is B - Create a spike story to analyze the impact of the threshold requirement on current stories.
A "spike" is a research activity used in Agile to investigate a technical or functional uncertainty. In this case, the performance threshold requires exploration to understand its impact on multiple backlog items. Creating a time-boxed spike allows the team to analyze without prematurely committing to changes.
PMI Agile Practice Guide describes spikes as:
"A spike is a user story for time-boxed research or exploration. Teams use spikes when they need more information to estimate or deliver a story." (PMI Agile Practice Guide, Section 5.2 - Types of Backlog Items) Mike Griffiths adds:
"When a new requirement introduces uncertainty, such as performance constraints, creating a spike helps the team determine scope, risk, and impact before incorporating it into backlog stories." (PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Other options:
* A prematurely alters acceptance criteria before understanding the impact.
* C leans toward big upfront design (non-agile).
* D skips the exploration phase and directly breaks into tasks.

The correct answer is B - A product backlog should be created to list the project requirements from all of the project stakeholders.
In Agile, the product backlog serves as a living document where requirements, user stories, and stakeholder feedback are continuously refined. It is the central mechanism for capturing and prioritizing stakeholder needs and ensuring that business value is delivered incrementally.
From the PMI Agile Practice Guide:
"The product backlog is a prioritized list of work for the development team that is derived from stakeholder input, user stories, and emerging needs. It evolves as the project progresses and stakeholder feedback is incorporated." (PMI Agile Practice Guide, Section 5.2 - Product Backlog) Mike Griffiths writes:
"Product backlogs provide transparency into stakeholder priorities. They enable the team to continuously align work with customer expectations and business needs." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Stakeholder Engagement) Why the other options are incorrect:
* A refers to the traditional project charter, which is not commonly updated throughout the agile life cycle.
* C is a misunderstanding-the Agile Manifesto is a set of principles, not a project-specific document.
* D misuses user stories; stories are used for functional requirements, not stakeholder profiles.

When an agile team's velocity is slowing down, it is essential to regularly evaluate and adjust how the team is performing. By using feedback loops in every sprint, the team lead can continuously assess the team's progress, identify bottlenecks, and address issues early on. These feedback loops, typically discussed in sprint retrospectives, provide an opportunity for the team to identify the root causes of challenges, such as miscommunications, and make improvements to ensure better performance in future iterations. This approach promotes ongoing reflection and adaptation, which are core principles of Agile.

Kanban is an approach that focuses on visualizing and managing work in process (WIP) to ensure that there is minimal waste and that teams only work on what they can handle at any given time. It provides a flexible framework for continuous improvement, without the overhead of time-boxed iterations like in Scrum. Kanban allows teams to focus on limiting work in process, streamlining workflows, and improving efficiency while avoiding waste. This approach aligns with the organization's desire to minimize overhead and control WIP to maximize flow and productivity.