Spikes are meant for experimentation and learning, not guaranteed outcomes. According to the PMI Agile Practice Guide (Section 5.2 Spikes), if a spike does not lead to a clear solution, the team can extend or reframe it, especially when aiming for a sustainable long-term solution. Agile supports encouraging experimentation and learning from failure.
Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Problem Detection and Resolution) recommends adapting when a spike's results are inconclusive-redefining the scope and collaborating as a team increases the chance of a valuable outcome.
* Option B is correct: it continues learning and promotes team collaboration.
* Option A undercuts team ownership.
* Option C prioritizes a short-term fix and undermines agile values.
* Option D is not needed at this early stage-root cause analysis is better for recurring or systemic issues.

If a story isnot completed, it isnot counted toward the current sprint velocity. When carrying the story forward to the next sprint, teams shouldre-evaluate the story size, especially if part of the work is already done. According to thePMI Agile Practice Guide (Section 5.4: Velocity and Estimation)andMike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), agile teams are encouraged tore- estimatesuch items based on remaining work.
* Option Dis correct: incomplete stories should be re-estimated based on new size or effort.
* Option Aviolates velocity principles-onlyfully completedstories count.
* Option Bundermines the fixed-length timebox principle of sprints.
* Option Cis not directly relevant unless the story's complexity necessitates research, which is not stated here.

The scrum master should emphasize the core principles of agile, which are centered around collaboration, delivering value incrementally, and fostering a shared mindset among the team. In an agile environment, success is not only about following processes but about the team working together towards a common goal, adapting to change, and continuously delivering value to customers. These principles are the foundation of agile methodologies and essential for teams that are new to agile to understand.

When overwhelmed by support tickets, the agile approach is toprioritize systemic problem-solving over reactive work. According to thePMI Agile Practice Guide (Section 5.5: Quality and Continuous Improvement)andMike Griffiths' PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution), agile teams should identifyroot causesrather than just addressing symptoms. Byanalyzing the backlog, the team can spot patterns and addresssystemic issues, reducing incoming ticket volume in the long run.
* Option Cis correct: addressing the root cause improves sustainability and overall efficiency.
* Option Aleads to burnout and is unsustainable.
* Option Bignores prioritization or value.
* Option Dis not a strategic response-it increases cost without solving the core issue.

In agile, especially under conditions of uncertainty or anticipated changes, teams should focus on collaborative product development, including ongoing backlog refinement and continuous product reviews.
This approach is endorsed by the PMI Agile Practice Guide (Section 5.1 Product Backlog and Refinement) and Section 7.2 (Engaging Stakeholders), which emphasize frequent interaction with the product owner and iterative feedback loops to adapt quickly.
Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the practice of refining the backlog regularly and conducting frequent reviews to stay aligned with stakeholder expectations.
* Option B is correct: continuous collaboration with the product owner supports flexible, value-driven delivery.
* Option A is only a partial measure.
* Option C promotes a waterfall mindset.
* Option D ignores the nature of changing requirements.