The correct answer is C - Work with the customer to understand which user stories will deliver the best business value, re-prioritize the backlog, and share it with the customer to provide release plans.
Agile allows for adaptive planning and continuous prioritization but also provides transparency and planning via product roadmaps and release planning. Collaborating with the customer to align on value and priorities fosters trust and offers predictability through rolling wave planning.
PMI Agile Practice Guide:
"Agile release planning provides a high-level roadmap of deliverables based on value. It enables stakeholder alignment while remaining flexible to changing priorities." (PMI Agile Practice Guide, Section 5.3 - Adaptive Planning and Release Planning) Mike Griffiths:
"Agile doesn't reject roadmaps-it refines them iteratively. Teams work with stakeholders to determine business value and build release forecasts that evolve with each iteration." (PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Incorrect options:
* A is rigid and misrepresents agile's balance between planning and adaptability.
* B inappropriately shifts responsibility to the customer.
* D is valid but lacks the engagement and re-prioritization aspect.

The correct answer is A - Include it in the product backlog and use a new indicator to annotate that it is technical debt. Agile teams track technical debt transparently by adding it to the product backlog. Marking it with a clear label helps the team and product owner consider it during prioritization and planning.
From the PMI Agile Practice Guide:
"Technical debt should be made visible and added to the product backlog. Teams may use tags or indicators to distinguish it and make informed prioritization decisions." (PMI Agile Practice Guide, Section 5.5 - Technical Debt) Mike Griffiths emphasizes:
"Technical debt must be tracked in the backlog to avoid long-term consequences. Tagging it ensures stakeholders are aware and can prioritize its resolution appropriately." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* B assumes all technical debt is low priority, which may not be true.
* C is incorrect; agile explicitly recommends tracking tech debt.
* D introduces inconsistency and reduces visibility.
####################################

When a security issue is revealed mid-sprint, the project manager should consult with both the product owner and the project team. The product owner is responsible for prioritizing the backlog and ensuring that the most valuable features are worked on, while the team will help assess the technical implications of addressing the security issue.
The product owner needs to understand the impact of the security issue on the product ' s value and determine if it needs to be prioritized over other work in the sprint.
* The project team should help evaluate the effort required to address the issue and ensure that the solution is feasible within the sprint's capacity.
* By collaborating with both the product owner and the team, the project manager can make an informed decision on whether to adjust the sprint plan, reprioritize the backlog, or take necessary actions to address the vulnerability. This ensures that the security issue is resolved without jeopardizing the overall sprint goals.

In agile, work is considered "done" only when it meets the agreed-upon Definition of Done (DoD), which includes all aspects like coding, review, testing, and documentation. If there ' s disagreement about completion, the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance) recommends revisiting and aligning the DoD between the team and product owner.
Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) explains that without a clear and shared Definition of Done, misunderstandings about completion status can occur, especially with quality-related tasks like testing.
* Option A is correct because aligning on the DoD resolves current and future misunderstandings.
* Option B introduces unnecessary escalation.
* Option C postpones resolution and does not solve the core issue.
* Option D incorrectly assumes testing isn't part of the story's completion criteria.

The correct answer is B - Prioritizing stories.
The MoSCoW method is a prioritization technique used in Agile to categorize requirements and backlog items based on their business value. It helps stakeholders and teams agree on what is essential to deliver versus what is desirable or optional.
MoSCoW stands for:
* M - Must have
* S - Should have
* C - Could have
* W - Won't have (this time)
From the PMI Agile Practice Guide:
"The MoSCoW prioritization method helps stakeholders classify backlog items based on their criticality and desired delivery timing. This enables better alignment with business objectives." (PMI Agile Practice Guide, Section 5.2 - Prioritization) Mike Griffiths explains:
"MoSCoW is a simple but effective method for clarifying which features are essential and which can be deferred. It enhances transparency during prioritization discussions." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Value-Driven Delivery) Why the other options are incorrect:
* A - Estimating story size involves techniques like planning poker or T-shirt sizing.
* C - Product validation is done via demos, acceptance criteria, and stakeholder feedback.
* D - Progress tracking uses tools like burndown charts or cumulative flow diagrams.