Pass the PMI Agile DASSM Questions and answers with ExamsMirror

For an Agile or Lean project team, the aim of theConstruction phaseis to develop aconsumable solutionin a collaborative and incremental manner. This phase focuses on delivering working increments of the product that can be consumed by end users or stakeholders. The approach is highly iterative and involves continuous feedback, allowing the team to make frequent adjustments to align with customer needs and expectations. Options B, C, and D do not fully capture the essence of delivering a solution that is ready to be consumed and used by customers.

False: On an Agile team, the team members do not accept or reject their own work at the iteration demo. Instead, the Product Owner, along with stakeholders, is responsible for accepting or rejecting the work presented. The iteration demo (or sprint review) is an opportunity for the team to showcase their completed work to stakeholders and gather feedback. The decision to accept the work is based on whether it meets the Definition of Done, fulfills the acceptance criteria, and aligns with stakeholder expectations.

The primary function of the "Business Operations" process blade in Disciplined Agile is to provide ongoing support and services to customers and ensure that products function smoothly post-deployment. This involves managing customer relationships, handling support requests, andmaintaining operational stability. Options such as "B. To monitor the competitive landscape" and "D. To ensure cash flow in the organization" do not align with the core function of Business Operations. "C. To monitor and guide teams to remove barriers" is more aligned with the roles of leadership and governance. Hence, "A. To provide services to customers and support your products" is the correct answer.

An important part of improving the Way of Working (WoW) for a team is to continuously evolve and adapt processes, tools, and practices to better fit the team's needs and context. "Stick to a method once you discover it" contradicts the Disciplined Agile principle of continuous improvement. Instead, teams are encouraged to always try to get better (C), do the best they can (A), and start where they are (D) while continuously exploring new and more effective ways of working. Thus, Option B is not an important part of improving the WoW.

Estimating in hours instead of pointsmay not help in improving predictabilitybecause time-based estimates can often be inaccurate and can vary widely based on individual productivity and context. Using story points allows teams to focus on relative size and complexity, making it easier to compare work items and plan iterations more predictably.

Options B (reducing technical debt), C (reducing feedback cycles), D (respecting WIP limits), and E (adopting a test-first approach) all contribute to improving predictability by promoting consistent, high-quality delivery.

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 the context of the Disciplined Agile (DA) framework, if a team is about to begin work on a project where releases are expected only every six months or so, and the team does not have an agile mindset or desire to release often, the "Traditional" lifecycle is most appropriate. The Traditional lifecycle, also known as a predictive or waterfall lifecycle, is suitable for teams or projects that require extensive planning and where changes are infrequent or less welcome. This approach matches well with a mindset that is not inclined towards frequent releases or iterative development, allowing for longer, planned intervals between releases, which aligns with the six-month release cadence described in the scenario.

Disciplined Agile (DA) milestones are based on Lean governance principles. Lean governance emphasizes lightweight control mechanisms and focuses on achieving desired outcomes rather than enforcing compliance through heavy documentation or bureaucratic processes. DA milestones are established to ensure that value is being delivered efficiently and effectively throughout the lifecycle, with decisions made based on evidence and validated learning rather than detailed documentation (A) or strict adherence to lifecycle stages (D). While continuous integration (C) can support Lean governance by providing frequent, actionable insights into product development, it is not the foundation upon which DA milestones are based.

The principle "Organize around products/services" meansbuilding dedicated cross-functional teams focused on customer offerings. This approach ensures that teams are aligned directly with the delivery of customer value, with all the necessary skills to deliver a complete product or service. This organization enhances focus, collaboration, and efficiency, driving greater value delivery to customers.

Option A (asking customers to pick from available products) does not reflect this principle, and Option C (project teams being best equipped) does not align with the DA emphasis on long-standing, product-focused teams over temporary project teams.

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 primary advantage of using design thinking, according to DA guidelines, is that it promotes customer empathy and appropriate solutions. Design thinking focuses on understanding the user's needs and creating solutions that are tailored to those needs. Options A, C, and D are not accurate descriptions of design thinking's primary benefit; rather, they reflect misconceptions or partial truths.

The Exploratory Life Cycle is adopted when there is a need to bring a new product or service to market, and the customer requirements are uncertain. This life cycle is characterized by a high degree of exploration and experimentation, where the team continuously learns and adapts based on customer feedback and market conditions. Options A and B are incorrect because they refer to evolving an existing product or service rather than bringing a new one to market. Option E is also incorrect because it assumes the requirements are well understood, which would not necessitate an exploratory approach.