The correct answer is A - Prioritize the stakeholder feedback, considering the impact on strategic objectives and current workload, and discuss these priorities with the team in the next sprint planning meeting to collaboratively decide on the next steps.
Agile promotes adaptive planning and continuous stakeholder engagement. While feedback is highly valuable, especially from a sprint review, changes to the product backlog must be carefully prioritized and collaboratively discussed with the team. The product owner's responsibility is to maintain and refine the backlog, ensuring alignment with stakeholder needs while also preserving team focus and avoiding unnecessary disruption during an ongoing sprint.
From the PMI Agile Practice Guide:
"Product backlog refinement is an ongoing process in which the product owner and the team collaborate on the details of backlog items. This includes analyzing, estimating, and prioritizing items to reflect the latest feedback and business needs." (PMI Agile Practice Guide, Section 5.2 - Product Backlog Refinement)
"Agile teams embrace change, especially when it delivers value. However, they also maintain sustainable pace and focus by avoiding mid-sprint scope changes unless absolutely necessary. Backlog items are reviewed and reprioritized before the next sprint begins." (PMI Agile Practice Guide, Section 3.4 - Value-Driven Delivery) From Mike Griffiths' PMI-ACP Exam Prep Book:
"While agile encourages responding to change, disrupting sprint commitments can erode team trust and productivity. Sprint planning is the correct forum to reprioritize work based on new stakeholder insights." (Mike Griffiths, Chapter 5 - Adaptive Planning) Why the other options are incorrect:
* B introduces mid-sprint disruption and disregards agile best practices for maintaining sprint integrity and team focus.
* C eliminates team collaboration and risks breakdowns in communication, violating agile's emphasis on transparency and teamwork.
* D disregards valuable feedback and delays addressing important stakeholder needs, which could compromise customer satisfaction and strategic alignment.

According to the PMI Agile Practice Guide (Section 5.2 Requirements and User Stories) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), epics are large user stories that must be decomposed into smaller user stories for accurate planning and inclusion in sprints.
The two main drivers for breaking down epics are:
* Size - Epics are typically too large to be completed in a single iteration and must be divided to create manageable pieces of work.
* Priority - High-priority epics are decomposed early to allow the team to work on the most valuable items first.
This makes Option A the correct answer. The decision to decompose the epic is based on the need to fit it into sprint capacity and to align with backlog prioritization.

The correct answer is C - Non-functional requirements should have been added to the definition of done. Non- functional requirements such as performance, security, or usability criteria apply across stories and should be included in the Definition of Done (DoD) to ensure consistent delivery of quality attributes.
From the PMI Agile Practice Guide:
"The definition of done should incorporate quality standards, including non-functional requirements. This ensures these standards are consistently applied across all deliverables." (PMI Agile Practice Guide, Section 5.2 - Definition of Done) Mike Griffiths further explains:
"Non-functional requirements are often best represented in the DoD so they're applied universally. Without this, teams may deliver functionality that lacks necessary quality characteristics." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A would help but isn't sufficient for global system qualities.
* B is suitable for specific stories but doesn't ensure consistency across the product.
* D is helpful but doesn't guarantee alignment with quality standards.

The correct answer is A - Use the DISC framework with each team member.
The DISC model (Dominance, Influence, Steadiness, and Conscientiousness) is a well-established behavioral assessment tool used to understand communication preferences, motivators, and individual work styles. Agile leaders may use tools like DISC to foster emotional intelligence, improve collaboration, and re-engage disengaged team members.
From the PMI Agile Practice Guide:
"Effective agile leaders understand individual team members ' communication styles and motivations. Tools such as DISC or MBTI can help assess personality preferences and enable better coaching." (PMI Agile Practice Guide, Section 6.2 - Coaching Agile Teams) Mike Griffiths notes:
"Behavioral models such as DISC support the development of emotionally intelligent teams. They help leaders tailor their coaching and communication approaches to individual needs." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 - Team Performance) Why other options are incorrect:
* B (MoSCoW) is a prioritization technique, not a tool for personal engagement.
* C (Hiring a SAFe coach) is overkill and not the most direct or relevant response.
* D (BDUF - Big Design Up Front) is a traditional approach unrelated to team dynamics or motivation.

A value stream map is a tool used to visualize the flow of materials and information through a process, identifying areas of waste and inefficiency. In this case, the business analyst's key observations will include wait times (delays between steps) and cycle times (time taken to complete each step in the process). By analyzing these, the business analyst can identify opportunities to streamline the process, reduce delays, and improve overall efficiency in delivering healthcare services.