Which of the following roles would fall under that of a "specialist" on a Disciplined Agile Delivery Team?
Answer(s): A
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?
Answer(s): D
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.
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?
Answer(s): C
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?
Answer(s): B
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.
What are the three phases common across project life cycles? (Choose three)
Answer(s): C,D,E
In Disciplined Agile (DA), the three common phases across project life cycles are Inception, Construction, and Transition. These phases reflect the iterative and incremental approach of agile methodologies tailored to suit varying contexts.Inception: This phase is about getting things started properly. It includes initial planning activities such as defining the vision, developing a preliminary project plan, identifying stakeholders, securing funding, and setting up the initial environment.Construction: This phase focuses on developing a consumable solution in a series of iterations. The team builds, enhances, and evolves the solution to ensure that it meets stakeholders' needs while remaining aligned with the overarching vision and goals. Transition: The transition phase ensures that the solution is ready for delivery to the end-users or stakeholders. This includes final validation and verification activities, user training, deployment, and addressing any remaining issues.These phases are common in the DA life cycles, reflecting the disciplined approach to managing complexity in various types of projects, from straightforward to highly complex, while supporting adaptability and continuous improvement.
PMI, "Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)," which outlines the DA life cycles, including Inception, Construction, and Transition phases. PMI's Disciplined Agile Toolkit, which describes these phases in detail and their relevance across different types of project life cycles.
Post your Comments and Discuss PMI DASM exam dumps with other Community members:
Amazon ECS
Application Load Balancer
AWS Global Accelerator
Network Load Balancer
EC2
Auto Scaling group
CloudFront
ALB
AWS PrivateLink
CRR
SSE-S3
Athena
S3
SSE-KMS
RDS Custom for Oracle
s3:GetObject
Amazon OpenSearch Service
CloudWatch Logs
Kinesis Data Firehose
Kinesis
S3 bucket
SQS
AWS Lambda
AWS Secrets Manager
AWS Systems Manager OpsCenter
secretsmanager:GetSecretValue
seq
for h in {1..254}
for h in $(seq 1 254); do
Kinesis Data Streams
Amazon Redshift
secrets:GetSecretValue
aws:PrincipalOrgID
"aws:PrincipalOrgID": "o-1234567890"
Azure Bot Service
Microsoft.Network/applicationSecurityGroups
Microsoft.Network/bastions
Microsoft.Network
COPY INTO
SELECT
COPY INTO @stage/path/file.csv FROM (SELECT col1, col2 FROM my_table WHERE date >= '2024-01-01') FILE_FORMAT=(TYPE=CSV);
Users
External collaboration settings
zone
subinterfaces
test
test security-policy-match
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the DASM content, but please register or login to continue.