The requirement for the home button to be recognizable is subjective and requires clarification from a design perspective. The team should consult the design team or subject matter experts (SMEs) who have expertise in user experience (UX) and interface design. These experts can provide specific guidelines or criteria for what constitutes a recognizable home button, such as color, shape, placement, or icons. This ensures that the team can create an appropriate, measurable test for the requirement.

The correct answer is A - Speak to the agile lead about the concerns.
Agile encourages transparency, collaboration, and open communication across all levels of the team. If a team member identifies a risk or concern, the most agile-aligned approach is to raise it directly and constructively with the agile lead or Scrum Master, who is responsible for protecting the team and facilitating problem- solving.
From the PMI Agile Practice Guide:
"Agile teams promote a culture of openness where team members are encouraged to speak up and raise concerns. Effective leadership listens and collaborates to resolve issues." (PMI Agile Practice Guide, Section 4.1 - Agile Mindset) Mike Griffiths further adds:
"Team members should be empowered to express concerns and challenge assumptions respectfully.
Continuous communication and feedback improve project outcomes."
(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 - Team Performance)
Why the other options are not ideal:
* B promotes blind compliance, which is contrary to agile empowerment.
* C suggests overwork, which contradicts sustainable pace.
* D may escalate unnecessarily without first engaging the proper leadership channel.

Agile promotes cross-team collaboration and shared understanding of goals, especially when dependencies exist. The PMI Agile Practice Guide (Section 4.3.1: Team Collaboration and Alignment) recommends using vision alignment and shared objectives to reduce silos and improve coordination. A vision-sharing session ensures that all teams understand the business context and mutual interdependencies, helping build accountability and improve collaboration.
* Option B is correct: shared vision fosters alignment and commitment.
* Option A is punitive and against agile values of collaboration.
* Option C disrupts team stability and should not be a first step.
* Option D addresses the symptom (delivery delay) but not the root cause (lack of shared vision
/accountability).

One of the pillars of agile is early and continuous customer feedback to ensure that the product being delivered meets stakeholder expectations. According to the PMI Agile Practice Guide (Section 5.3: Reviews and Feedback Loops) and Mike Griffiths ' PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), frequent customer reviews (e.g., sprint reviews) ensure alignment and early identification of quality or value issues.
* Option D is correct: regular customer engagement during reviews ensures delivery effectiveness and customer satisfaction.
* Option A is inappropriate-daily stand-ups are for internal team coordination.
* Option B reflects a waterfall approach.
* Option C misplaces the responsibility-requirements evolve and are refined throughout, not fixed up front.

A user story that is too large to complete in one sprint is considered an epic. Agile teams should split it into smaller, valuable, testable stories. The PMI Agile Practice Guide (Section 5.2: User Stories and Decomposition) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend breaking down large stories and renegotiating sprint scope collaboratively with the product owner.
* Option C is correct: this aligns with collaborative planning and story decomposition.
* Option A is rigid and dismisses collaboration.
* Option B promotes unsustainable practices.
* Option D violates the principle of fixed-length iterations.