The " Life Timeline " exercise is a technique used to build psychological safety and vulnerability-based trust.
According to Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 3: Team Performance), exercises that encourage sharing personal stories and emotional journeys foster deep interpersonal connection, which is foundational to high-performance teams.
The PMI Agile Practice Guide (Section 4.3.2: Building Trust) emphasizes the role of emotional intelligence and trust-building in agile teams, stating that teams become high-performing when they feel safe to express themselves without fear of judgment.
* Option B is correct: the exercise builds vulnerability and trust-key drivers of high performance.
* Option A focuses on trust but doesn ' t emphasize vulnerability, which is central here.
* Option C is too generic.
* Option D misframes the purpose-it's about building connection, not assessing competencies.

Sprint planning or any task-level technical meeting should involve the development team and the product owner, as they are the key players in delivering and clarifying work. According to the PMI Agile Practice Guide (Section 3.3: Agile Roles and Responsibilities) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 3: Team Performance), the Scrum Master facilitates the meeting, while the development team and product owner collaborate on the details.
* Option D is correct: the core team (developers) and product owner are the correct participants for story elaboration and commitment.
* Option A and C involve the customer and sponsor unnecessarily for a technical planning meeting.
* Option B includes " key stakeholders, " which may be overkill unless specific business input is needed.

The correct answer is D - Stop updating the documentation and initiate an analysis to identify its value and act on the findings.
Agile promotes the creation of "just enough" documentation. If a document isn't being used and adds no value, the team should reflect on whether to discontinue or improve it. Retrospectives are the appropriate venue to identify such inefficiencies and implement continuous improvement.
From the Agile Manifesto (referenced in PMI Agile Practice Guide):
"Working software over comprehensive documentation."
From the PMI Agile Practice Guide:
"Agile teams minimize non-value-added work. If documentation is not being used or reviewed, teams should examine whether it is necessary, and if not, discontinue or replace it." (PMI Agile Practice Guide, Section 7.1 - Continuous Improvement) Mike Griffiths adds:
"Documentation should serve a purpose. If stakeholders do not find value in it, the team should discontinue or refactor it to meet actual needs." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 - Continuous Improvement) Why the other options fall short:
* A prolongs the wasteful practice unnecessarily.
* B lacks the analysis needed before eliminating documentation.
* C enforces process over value, which contradicts Agile principles.

The correct answer is A - Jointly meet with the team and product owner to discuss options and determine the end date. Agile promotes collaborative decision-making. When significant changes in performance arise, discussions should occur between the team and product owner to assess impact, explore value delivery, and make informed decisions.
From the PMI Agile Practice Guide:
"Agile teams regularly review performance trends. Changes in velocity should prompt discussions between the team and product owner to evaluate implications and opportunities." (PMI Agile Practice Guide, Section 5.4 - Release Planning) Mike Griffiths states:
"Forecasting must remain collaborative. Teams and product owners work together to determine whether to ship early, expand scope, or adjust timelines." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Incorrect options:
* B skips stakeholder collaboration.
* C assumes backlog expansion without value validation.
* D contradicts agile principles of delivering value early.

The correct answer is B - Ask the team for suggestions. Agile teams are self-organizing. The Scrum Master should facilitate problem-solving by enabling the team to collaboratively decide how to handle bottlenecks.
This approach respects the team's autonomy and encourages shared ownership.
From the PMI Agile Practice Guide:
"Scrum Masters facilitate team collaboration and self-organization. When problems arise, they engage the team in identifying and implementing solutions, rather than solving issues unilaterally." (PMI Agile Practice Guide, Section 4.3 - Servant Leadership and Team Empowerment) Mike Griffiths explains:
"The Scrum Master's role is to facilitate rather than direct. If a team member falls behind, the team should collectively explore options for support, ensuring accountability and transparency." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* A undermines team autonomy and assigns tasks, which the Scrum Master should not do.
* C may help, but addressing issues privately doesn't promote transparency.
* D involves the Product Owner unnecessarily in team internal issues.