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.

The product owner is responsible for managing the product backlog and ensuring that it reflects the priorities and vision of the product. While the Scrum team can suggest changes or improvements during the refinement process, the product owner has the final say on whatchanges are made to the backlog. This ensures that the product backlog aligns with business needs, stakeholder expectations, and the overall product vision.
Therefore, the product owner can reject changes to the backlog if they believe the changes do not align with these priorities.

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.

In agile environments, planning should be flexible and adaptable to changing circumstances. Just-in-time (JIT) refinement refers to the practice of refining the backlog and details of the product features as they become more relevant, rather than attempting to plan everything upfront. This allows the team to respond to changes and new information as they emerge, which aligns with agile principles of iterative development and adaptability.

The correct answer is C - The team realized that some stories were underestimated relative to other stories and reestimated as needed.
According to the data in the chart:
* Backlog started at 500 points.
* Points steadily decreased by 25 points per iteration for the first 3 iterations, reflecting normal velocity.
* At the end of iteration 4, the backlog increased from 425 to 450 points (a 25-point jump), which indicates an increase in estimated remaining work.
In Agile, backlog point totals can increase when work is reestimated-typically because items were originally underestimated or new complexity is discovered. Reestimation reflects the evolving understanding of requirements and is a core principle of adaptive planning.
From the PMI Agile Practice Guide:
"Estimates may change as the team learns more. Agile teams inspect and adapt their understanding of the work during iteration planning and refinement. Story reestimation is normal and may result in backlog point increases." (PMI Agile Practice Guide, Section 5.3 - Adaptive Planning and Estimation) Mike Griffiths writes:
"Backlogs are dynamic. Teams may reestimate stories during grooming or retrospectives if they find that original estimates were off. This helps maintain planning accuracy and backlog integrity." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Estimation and Backlog Refinement) Incorrect options:
* A refers to external factors not reflected in the backlog points.
* B would be better handled by new backlog items, not inflating prior estimates.
* D suggests increased scope/output, which would add stories but not necessarily reestimate existing ones.