PeopleCert CASM Practice Exam Questions & Answers

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.

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.

Agile Process Improvement: Microprocess design principles.

ITIL 4: Process modularity and adaptability.

Scrum is built around timeboxed iterations called Sprints, where teams work in a fixed period (typically 1-4 weeks) to deliver a potentially shippable product increment.

A . Incorrect. While Scrum incorporates some Lean principles, its foundation is timeboxing, not Lean.

B . Incorrect. Scrum and DevOps are complementary but distinct. Scrum is not based on DevOps principles.

C . Correct. Timeboxing is a core aspect of Scrum, ensuring focused delivery within a defined timeframe.

D . Incorrect. Scrum rejects sequential (Waterfall-like) processes in favor of iterative and incremental work.

Scrum Guide 2020: Sprints and Timeboxing

An Agile Service Management Team typically requires a Leader who guides the team in applying Agile practices, ensuring collaboration, and delivering value. Let's evaluate the roles:

A . Correct. A leader is necessary to inspire, guide, and ensure the team adheres to Agile principles. This role may overlap with an Agile Service Manager or Scrum Master.

B . Incorrect. While developers may be part of service delivery teams, they are not mandatory for every Agile Service Management team, which focuses more on service processes.

C . Incorrect. Designers may contribute to specific tasks, but they are not core members of Agile Service Management teams.

D . Incorrect. While the customer provides input, they are not part of the team but rather a stakeholder.

ITIL 4 Service Value Chain: Roles and responsibilities in Agile Service Management.

The Sprint Backlog provides the team with a clear understanding of what needs to be done and the freedom to self-manage to achieve the Sprint Goal.

A . Correct. The Sprint Backlog includes a plan for how the team will meet the Sprint requirements.

B . Incorrect. While the Sprint Backlog lists work items, this alone doesn't cover its full purpose.

C . Correct. Agile teams are self-managing, and the Sprint Backlog empowers them to organize their work autonomously.

D . Correct. Both A and C accurately describe the purpose of the Sprint Backlog.

Scrum Guide 2020: Purpose and contents of the Sprint Backlog.

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.

Lean Startup by Eric Ries: MVP concept.

Agile principles: Iterative delivery and customer feedback.

Lean is a production philosophy derived from Toyota's manufacturing system, which focuses on delivering customer value by reducing waste, improving flow, and continuously enhancing processes.

A . Incorrect. Lean is not a standard for delivering software. It is a broader philosophy that can be applied across industries.

B . Correct. Lean's primary objective is to optimize customer value by eliminating inefficiencies and improving workflow.

C . Incorrect. While Lean uses pull systems to manage workflow, this is a method within Lean and not its overall definition.

D . Incorrect. DevOps values align with Lean principles but do not define Lean itself.

Lean Thinking by James Womack and Daniel Jones

SAFe Framework: Applying Lean Principles