After three iterations, it is identified that a project's underlying security structure architecture is unstable. While there is a technical solution, all work to date is flawed. This will impact seve

Question

Options

• AAsk the development team to address the issue since it is in their domain.
• BReview the project's risk matrix, and follow the steps outlined in the risk mitigation plan.
• CMeet with the team and stakeholders to address rework and rewrite stories as needed.
• DCancel the current sprint, and meet with stakeholders to reassess the project's validity.

• A
  3% (1)
• B
  9% (3)
• C
  82% (27)
• D
  6% (2)

Explanation

A foundational architectural defect that invalidates all prior work and threatens future business services is a high-stakes issue that requires collective decision-making. The product owner must bring together the team and stakeholders to transparently assess the scope of rework, reprioritize the backlog, and rewrite affected stories. This collaborative approach maintains trust and ensures all impacted parties contribute to the solution. Option A (delegate to dev team alone) excludes stakeholders who are directly affected. Option B (follow the existing risk plan) is likely insufficient for a newly discovered, systemic architectural failure. Option D (cancel sprint) is premature - the severity must first be understood collaboratively before such drastic action is taken.

No community discussion yet for this question.