A Minimum Viable Process (MVP) is the smallest functional version of a process that delivers enough value for initial use while allowing for iterative refinement.
A . Incorrect. "Minimum Value Process" is not a recognized term in Agile.
B . Correct. The MVP concept aligns with Agile principles, focusing on delivering value early while enabling incremental improvements.
C . Incorrect. A Beta Release applies to software products rather than processes.
D . Incorrect. A Proof of Concept demonstrates feasibility but does not necessarily deliver usable value.
Reference:
Lean Startup by Eric Ries: MVP concept.
Agile principles: Iterative delivery and customer feedback.

An Epic is a larger work item that is broken down into smaller, related user stories. It is not directly tied to Sprint requirements.
A . Incorrect. An Epic is not a single user story; it encompasses multiple related user stories.
B . Correct. Epics represent a grouping of related user stories that contribute to a larger feature or objective.
C . Incorrect. Epics are not necessarily scoped to a single Sprint; they may span multiple Sprints.
D . Incorrect. While related stories are correct, the reference to Sprint requirements is inaccurate.
Reference:
Agile Glossary: Definition of Epics.

Microprocesses are small, independent activities within a broader process, focused on efficiency and adaptability. Let's evaluate the options:
A . Incorrect. While small, frequent releases are characteristic of Agile principles, this is not a specific characteristic of microprocesses. Microprocesses focus on modularity and adaptability rather than release strategies.
B . Correct. Outputs from microprocesses can feed into multiple practices, demonstrating their flexibility and reusability.
C . Correct. Each microprocess adds incremental value, aligning with Agile's iterative approach.
D . Correct. Microprocesses are often tailored to support specific processes or practices.
Reference:
Agile Process Improvement: Microprocess design principles.
ITIL 4: Process modularity and adaptability.

In Scrum, the Product Owner has the authority to manage the Product Backlog, including accepting or rejecting changes to the Sprint Backlog.
A . Incorrect. The team is responsible for delivering the work but does not control changes to the Sprint Backlog.
B . Incorrect. The Agile Service Manager is not a role in Scrum and does not make decisions about the Sprint Backlog.
C . Incorrect. The Agile Practice Owner is not a Scrum role.
D . Correct. The Product Owner ensures the Sprint Backlog aligns with the Sprint Goal and business priorities.
Reference:
Scrum Guide 2020: The role of the Product Owner