Pass the PMI Agile DASSM Questions and answers with ExamsMirror

Reducing work-in-progress (WIP)is intended to increase focus, reduce lead time, and create a greater incentive to prioritize. It helps teams deliver value more quickly and efficiently by concentrating on fewer items at a time, minimizing context-switching, and reducing the chances of burnout.Option A isnota benefit of reducing WIP, as reducing WIP discourages multi-tasking between many high-priority items. In fact, reducing WIP aims to prevent multi-tasking, which is often counterproductive.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) curriculum materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

The main role of the team lead (which can be referred to as a Scrum Master, Team Coach, or Team Lead in Disciplined Agile) is to ensure that the team is building the product in the right way. This involves facilitating the team's process, removing impediments, and coaching them to adopt and optimize Agile practices, ensuring quality and efficiency in delivery. The team lead does not dictate what product to build (which is the role of the Product Owner), nor is their primary role to build the product themselves or coordinate building efforts in a command-and-control manner. Instead, they focus on enabling and empowering the team to deliver high-quality work in alignment with Agile principles.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) curriculum materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

In Disciplined Agile, the role of a DevOps Engineer is not necessarily filled by an operations person assigned to an Agile or Lean team. The DevOps role can be filled by individuals from either the development or operations side, or even someone with cross-functional expertise. The focus of the DevOps role is to foster collaboration between development and operations to enable continuous integration, delivery, and deployment. It is not limited to being an "operations person," but rather emphasizes the integration and collaboration needed to improve the flow from development to operations.

A team should consider entering the transition phase when the product meets all stakeholder expectations. In Disciplined Agile, the transition phase involves finalizing the product or solution for release. This phase is initiated when the product is deemed ready and all necessary criteria, including stakeholder expectations, have been fulfilled. Options A (new MBI developed), C (operational teams ready), and D (MVP ready) may be relevant in other contexts but do not specifically trigger the transition phase.

The principle of "Delight customers" in the Disciplined Agile framework encourages teams to exceed customer expectations rather than just meet them. This approach aims to provide exceptional value and experiences that surprise and please customers, thereby fostering loyalty and positive word-of-mouth. Simply meeting expectations is not sufficient to truly "delight" customers; therefore, the statement that delighting customers means just about meeting their expectations is false.

In the context of Disciplined Agile (DA), an Epic is a large user story that represents a significant piece of work that usually requires substantial effort and may span multiple iterations or sprints to complete. Epics are often too large to be completed in a single iteration and are typically broken down into smaller, more manageable user stories. Option A (a collection of smaller user stories) is partially correct because epics are often decomposed into smaller user stories, but option B provides a more precise definition as it emphasizes the size and effort required for completion. Options C and D are not correct in the DA context; they describe different types of analysis tools or techniques.

The process goal of "Explore Scope" in the Disciplined Agile framework focuses on understanding the purpose, domain, and intended usage of a product. This involves clarifying what needs to be delivered, gathering requirements, and determining the boundaries of what is in and out of scope for the product development. When a team is exploring the product's purpose, domain, and usage, they are actively engaging in the process of defining and refining the scope of the work to be done, making Option C the correct answer. Options A, B, and D relate to other aspects of agile project management, but do not specifically address the exploration of scope.

True: A value stream does indeed begin and end with a customer. In Disciplined Agile, a value stream represents the sequence of activities an organization undertakes to deliver a product or service that is of value to a customer. It starts with a customer need or demand and ends with the delivery of value to that customer. The focus on value streams helps organizations optimize the flow of value, reduce waste, and enhance customer satisfaction by aligning all activities around delivering what the customer truly needs.

Agile teams, as per the Disciplined Agile (DA) framework, can deliver non-software projects. The DA toolkit is designed to be adaptable and applies agile and lean principles to a wide range of business domains beyond software development. This flexibility allows agile teams to use iterative and incremental approaches to manage various types of projects, such as marketing campaigns, event planning, and other organizational initiatives. Thus, it aligns with the PMI's stance that agility can benefit all types of projects, not just software-focused ones.

The architecture owner in Disciplined Agile has several key responsibilities: working with the product owner to define the technical roadmap (A), mentoring and coaching the team on technical practices (B), working to improve the supportability of the product (C), and evolving the design and architecture for the product (E). However, evaluating team members' performance and administering rewards (D) is not within the scope of the architecture owner’s responsibilities. This task typically falls under the purview of people managers or human resources.