Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. PMI
  5. DASM

Free PMI DASM Exam Braindumps (page: 2)

95.3% Passing Rate DOWNLOAD PDF EXAM
50 Questions & Answers
Page 2 of 14

Which of the following roles would fall under that of a "specialist" on a Disciplined Agile Delivery Team?

  1. Business Analyst
  2. Product Owner
  3. Project Manager
  4. Stakeholder

Answer(s): A

Explanation:

In the context of the Disciplined Agile (DA) framework, a "specialist" on a Disciplined Agile Delivery Team is someone with a specific, specialized skill set or domain expertise that contributes to the overall development and delivery process.
While the DA framework promotes cross-functional team members, it acknowledges that certain roles require specialized knowledge. A Business Analyst (BA) is considered a specialist role because they bring specific expertise in requirements gathering, process analysis, stakeholder communication, and translating business needs into actionable tasks for the development team. According to PMI's Disciplined Agile guidelines, BAs provide value by ensuring that the requirements are well-understood and clearly defined, which is crucial in aligning the team's efforts with stakeholder needs. On the other hand, the roles of Product Owner (B) and Project Manager (C) are more related to leadership, decision-making, and coordination, rather than specialized technical or analytical expertise. Stakeholders (D) are external to the delivery team and are not considered specialists within the team itself.



What is the Disciplined Agile principle of being pragmatic characterized by?

  1. Adapting lean methodologies when necessary
  2. Tailoring the organizational structure to the context
  3. Identifying when to be agile
  4. Being as effective as you can and continuously improving

Answer(s): D

Explanation:

The Disciplined Agile (DA) principle of being pragmatic is characterized by the focus on "being as effective as you can and continuously improving." According to PMI's Disciplined Agile Toolkit, being pragmatic means applying an agile mindset that is not constrained by a rigid set of rules or practices. Instead, it emphasizes being practical and outcome-focused, aiming for the best results in each unique context while continually seeking opportunities for improvement. Disciplined Agile promotes pragmatic decision-making by suggesting that teams should balance their approach by being both goal-driven and situation-aware. This means that instead of strictly adhering to a single agile framework or methodology, teams should assess their situation, leverage their experience, and apply the most suitable tools and techniques available. Furthermore, continuous improvement (Kaizen) is a fundamental aspect, meaning teams should regularly reflect on their practices and make iterative enhancements to achieve effectiveness. This principle also aligns with DA's guidance to "Optimize Flow" and "Be Awesome," as it encourages teams to deliver value while recognizing that every situation might require different tools, techniques, and practices. Thus, "D. Being as effective as you can and continuously improving" best captures the essence of DA's pragmatic approach.


Reference:

PMI, "Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)," which details the core principles of Disciplined Agile, including being pragmatic by focusing on effectiveness and continuous improvement.
PMI Disciplined Agile (DA) Toolkit, which explains how being pragmatic involves choosing the best approach for your specific context rather than adhering to a strict methodology.



A team is about to begin work on a project that will lace rapidly changing requirements with releases only every six months or so. The team does not have an agile mindset and does not want to release often.
Which lifecycle should the scrum master select?

  1. Program
  2. Lean
  3. Traditional
  4. Agile

Answer(s): C

Explanation:

In the context of the Disciplined Agile framework, when a team is dealing with rapidly changing requirements but is resistant to frequent releases and does not have an Agile mindset, the Traditional lifecycle is appropriate. This lifecycle aligns with teams that prefer a more plan-driven, less iterative approach, which typically includes longer release cycles and detailed upfront planning. The Traditional lifecycle in Disciplined Agile follows a waterfall-like approach, which is suitable when the team is not yet prepared to adopt Agile principles such as frequent delivery and adaptive planning.
The other options do not match this scenario:
A . Program lifecycle is used for coordinating multiple teams on larger programs, which is not relevant to a single team with the specified conditions. B . Lean focuses on optimizing flow and delivering value quickly, which contrasts with the team's preference for infrequent releases.
D . Agile lifecycle involves iterative development and frequent releases, which the team is resistant to.
Therefore, C. Traditional is the correct answer as it fits the team's preference for less frequent releases and their lack of an Agile mindset.



What is the purpose of an iteration retrospective?

  1. To showcase what the team accomplished in an iteration.
  2. To transfer knowledge and improvements to the next iteration.
  3. To prioritize stories and concrete tasks for the next iteration.
  4. To identity progress and to note encountered impediments.

Answer(s): B

Explanation:

The purpose of an iteration retrospective in the Disciplined Agile framework is to reflect on the team's process and performance during the previous iteration to identify what went well and what can be improved. The primary goal is to continuously improve by transferring the lessons learned, knowledge, and potential improvements to the next iteration. This aligns with Disciplined Agile's emphasis on continuous improvement and learning, which is critical to the team's effectiveness and efficiency.
The other options are not the primary focus of an iteration retrospective:
A . To showcase what the team accomplished in an iteration is the purpose of an iteration review or demo, not a retrospective.
C . To prioritize stories and concrete tasks for the next iteration is typically part of iteration planning. D . To identify progress and to note encountered impediments is also part of other ceremonies like daily standups but not the main focus of a retrospective. Thus, the correct answer is B. To transfer knowledge and improvements to the next iteration, aligning with the Disciplined Agile framework's purpose for iteration retrospectives.






Post your Comments and Discuss PMI DASM exam prep with other Community members:

DASM Exam Discussions & Posts