CASM Certified Agile Service ManagerV2.1 Questions and Answers

Becoming more Agile requires fostering collaboration, flexibility, and customer focus. Let’s evaluate the options:

A. Incorrect. While IT plays a crucial role in Agile transformation, solely focusing on software development doesn't address Agile principles like collaboration, iterative value delivery, and responsiveness to change.

B. Incorrect. Strict control over changes contradicts Agile principles, which encourage adaptability and welcoming change throughout development.

C. Correct. Collaboration is a core value in Agile, emphasizing interactions among teams, customers, and stakeholders to deliver value effectively.

D. Incorrect. While collaboration is correct, pairing it with a narrow IT focus (option A) doesn’t reflect a holistic Agile transformation.

References:

Agile Manifesto (Individual and interactions over processes and tools).

Principles of Agile Transformation: Collaboration and adaptability are key.

The Practice Backlog serves as the single source of truth for requirements within a service management practice, similar to how a Product Backlog functions in Scrum.

A. Incorrect. This describes a Sprint Backlog, not the Practice Backlog.

B. Correct. The Practice Backlog acts as the comprehensive repository for requirements specific to a practice.

C. Incorrect. While the Practice Backlog informs the roadmap, it is not a detailed project plan.

D. Incorrect. Only B accurately reflects the nature of a Practice Backlog.

References:

ITIL 4 and Agile Service Management: Practice Backlog as a requirements repository.

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.

References:

Scrum Guide 2020: The role of the Product Owner

Designing an Agile process begins with understanding customer needs and value to ensure that processes align with delivering that value efficiently.

A. Incorrect. While understanding the vision and goal is important, focusing on customer value takes precedence in Agile.

B. Correct. Agile emphasizes delivering value to customers, making this the critical starting point for process design.

C. Incorrect. Engaging stakeholders is essential but follows after understanding customer needs.

D. Incorrect. Understanding architecture comes later in the design process, after defining customer-centric objectives.

References:

Agile Manifesto: Customer collaboration over contract negotiation.

ITIL 4: Service design principles.

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.

References:

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

A Microprocess Architecture is a structured framework of interrelated microprocesses designed to improve the efficiency and effectiveness of service management processes.

A. Correct. This definition captures the purpose and functionality of a microprocess architecture in service management.

B. Incorrect. While integration is part of a microprocess architecture, the emphasis is on interrelation and service management effectiveness.

C. Incorrect. Although it mentions structure and value, it does not emphasize the interconnected nature of the microprocesses.

D. Incorrect. Microprocess architectures are not exclusive to Scrum but are broader in scope.

References:

ITIL 4: Microprocess modularity and architecture principles.

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.

References:

Scrum Guide 2020: Sprints and Timeboxing

The Agile Service Manager primarily serves the team by removing impediments that block progress and ensuring smooth delivery. Let’s assess the options:

A. Incorrect. While customer focus is important, this responsibility lies with the Product Owner or similar roles, not primarily the Agile Service Manager.

B. Incorrect. Writing user stories is a responsibility of the Product Owner or team members, not the Agile Service Manager.

C. Correct. The Agile Service Manager supports the team by identifying and eliminating obstacles to ensure their progress and efficiency.

D. Incorrect. While some aspects are relevant, only C accurately reflects the primary role of an Agile Service Manager.

References:

Scrum Guide 2020: Role of the Scrum Master in removing impediments.

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.

References:

Agile Glossary: Definition of Epics.