The correct answer is B - How much money the organization will earn or save by having the MMF.
Minimally Marketable Features (MMFs) are the smallest set of functionality that deliver value and can be released to generate revenue or realize benefits. Prioritization of MMFs is typically done based on expected business value-such as cost savings, revenue potential, or customer satisfaction.
From the PMI Agile Practice Guide:
"MMFs help teams focus on delivering value early and frequently. They are prioritized based on expected value to the customer or organization, return on investment (ROI), and business impact." (PMI Agile Practice Guide, Section 3.4 - Delivering Value Frequently) Mike Griffiths also emphasizes:
"MMFs should be prioritized based on business value-how much benefit they bring to the customer or organization. Value-based prioritization ensures the right features are built first." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Value-Driven Delivery) Why the other options are incorrect:
* A refers to risk but doesn't address business value.
* C addresses stakeholder involvement, not delivery prioritization.
* D refers to development time, which is considered but secondary to value.

The correct answer is D - Brainstorm with the team to identify a solution.
Agile promotes collective ownership and team-based decision-making. When a critical issue such as architectural scalability arises, the team should be involved in brainstorming alternatives, weighing trade-offs, and deciding how best to move forward collaboratively.
From the PMI Agile Practice Guide:
"Agile encourages collaborative problem-solving and cross-functional ownership. Teams should collectively analyze challenges and determine the most appropriate course of action." (PMI Agile Practice Guide, Section 4.3 - Collaborative Decision-Making) Mike Griffiths also affirms:
"When teams face significant technical or architectural risks, they should come together to explore options and make decisions based on consensus, feasibility, and value." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 - Problem Detection and Resolution) Why the other options are inappropriate:
* A is authoritarian and ignores team input.
* B risks performance degradation without team consensus.
* C may be part of the process, but only after the team has evaluated options.
###########
##################################################

The correct answer is D - Present the idea at the next ceremony attended by stakeholders to obtain their input.
Agile emphasizes transparency and collaboration with stakeholders. Since the organization values security highly, decisions that impact quality or policy must be discussed openly with stakeholders who have the authority to weigh cost-benefit trade-offs.
From the PMI Agile Practice Guide:
"Agile teams embrace customer collaboration and transparency. When decisions have business or organizational implications-such as security or compliance-stakeholders must be involved in evaluating trade-offs." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths states:
"When teams face decisions that could impact non-functional requirements like security, these should be escalated transparently to stakeholders for evaluation." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A and C could result in bias or lack of organizational alignment.
* B is too late and internal-only for a business-critical concern.

Step 1: Identifying Remaining MVP Story Points
From the backlog, the MVP-related stories that are not started include:
* Accessibility - color blind (4 story points)
* Increase security (21 story points)
* Add AI chatbot (5 story points)
Total remaining MVP story points = 4 + 21 + 5 = 30
Step 2: Projected Sprint Completion
* MVP Completion: The risk register mentions a burn reduction for sprints 4-6 due to holiday schedules.
* If the burn rate is consistent after sprint 6, the MVP will be completed by sprint 9.
* The entire backlog is projected to complete by sprint 16 assuming no further deviations.

When significant architectural flaws are discovered, agile teams inspect and adapt. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives and Adaptation), the product owner and team should collaboratively reassess priorities and rewrite backlog items to reflect the rework needed. This is aligned with agile's incremental delivery and continuous adaptation.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) stresses that rework should be handled through backlog refinement and collaborative planning-not panic or reactive decisions.
* Option C is correct: reassessing the backlog with stakeholders aligns with agile practices.
* Option A abdicates product responsibility.
* Option B is too rigid for agile, unless the risk matrix is already very mature and agile-focused.
* Option D cancels value delivery and is unnecessarily drastic.