PMI DASM Practice Test - Questions Answers, Page 5

In Disciplined Agile (DA), the Team Lead (often equivalent to the Scrum Master role in Scrum) is primarily responsible for ensuring that the team adheres to the agreed-upon practices and builds the product correctly. This involves facilitating the team's processes, coaching team members on agile practices, and helping them remove impediments. The Team Lead is responsible for guiding the team in following the chosen way of working (WoW) and ensuring that the team's processes are efficient, effective, and continuously improving. Therefore, the primary focus is on ensuring that the product is built correctly according to the standards and requirements agreed upon by the team.

PMI Disciplined Agile (DA) Toolkit, which defines the role of the Team Lead as the person who ensures that the team follows effective practices and builds the product correctly.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which provides insights into the responsibilities of the Team Lead role in DA.

In agile practices, particularly in the context of user stories, the features are typically defined by the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable. 'Achievable' is not a standard feature of a user story. Instead, user stories should be Negotiable (they are not fixed, and details can be discussed), Estimable (it should be possible to estimate the effort required), and Testable (it should be possible to verify whether the story has been implemented correctly). Therefore, 'Achievable' is not one of the features of a user story.

PMI Disciplined Agile (DA) Toolkit, which discusses the criteria for writing effective user stories using the INVEST model.

PMI Agile Practice Guide, which outlines the characteristics of user stories and the INVEST criteria.

A value stream map is a Lean tool that helps teams visualize the flow of work and identify waste throughout the process of delivering a product or service. The primary purpose of a value stream map is to help the team identify problem areas or bottlenecks in the path to realizing value. By understanding where delays, excess inventory, or unnecessary steps occur, teams can target these areas for improvement, thereby minimizing waste and optimizing the flow of value to customers.

B . Focusing on the construction phase is not specific to minimizing waste across the entire value stream.

C . Reducing delays in the workflow process is an outcome of identifying problem areas but not the direct function of value stream mapping.

D . Applying the five Whys root cause method is a separate Lean technique that can complement value stream mapping but is not its main purpose.

The role of the Product Owner in Agile and Disciplined Agile frameworks is to ensure the team is building the right product that aligns with stakeholder needs and provides maximum value to the customer. The Product Owner achieves this by managing and prioritizing the product backlog, defining user stories, clarifying requirements, and making decisions on behalf of the stakeholders.

A . Coordinate the product is not a primary function of the Product Owner.

B . Inspect the product may be a part of their responsibilities, but the focus is on guiding the product's development.

D . Organize the product team is more aligned with the Scrum Master's role.

In Team Estimation, also known as relative estimation or silent grouping, the team first estimates the relative sizes of all user stories by comparing them against each other. The stories are arranged in order of size (smallest to largest) without initially assigning specific numbers. After ordering, numerical values (such as story points) are then assigned to each story based on their relative size. This method leverages group consensus and comparative analysis to provide more accurate estimates.

B . Ranking teams in order of importance is not part of the Team Estimation process.

C . Defining 'Definition of Done' criteria is a separate exercise, not related to estimating story size.

D . Estimating necessary roles is not a part of Team Estimation.

According to the INVEST mnemonic, a good user story should be Valuable. This means that the user story must deliver value to the customer or stakeholder. Each user story should have a clear purpose, ensuring that the effort invested in its development contributes to the overall product value. Other criteria of the INVEST mnemonic include Independent, Negotiable, Estimable, Small, and Testable, but 'Valuable' is key to justifying the user story's inclusion in the product backlog.

PMI Disciplined Agile (DA) Toolkit, which outlines the INVEST criteria for user stories and emphasizes the need for stories to deliver value.

PMI Agile Practice Guide, which describes the characteristics of well-formed user stories using the INVEST mnemonic.

A complex adaptive system is characterized by the idea that understanding the individual components does not necessarily provide a clear understanding of the system's overall behavior. These systems are composed of interacting agents that adapt and learn from their experiences, leading to emergent behavior that cannot be easily predicted from the properties of the individual components. This concept is critical in Agile and Disciplined Agile practices, where teams and organizations are viewed as complex adaptive systems that evolve and adapt over time in response to their environment.

PMI Disciplined Agile (DA) Toolkit, which discusses the concept of complex adaptive systems in the context of agile teams and organizational dynamics.

PMI Agile Practice Guide, which explains how Agile frameworks view teams and organizations as complex adaptive systems to embrace change and continuous improvement.

A long-standing team is best suited for a long-term project with the potential for significant budgeting and tracking overhead. In Disciplined Agile (DA), a long-standing team is a stable, cross-functional team that remains intact over time and works on various projects or continuous delivery of value. This type of team reduces overhead associated with forming and disbanding teams and allows for more consistent tracking, budgeting, and management of resources. Additionally, long-standing teams develop stronger team dynamics and improve performance over time due to their stability.

B . A project team is typically temporary and disbanded once the project ends.

C . A cross-functional team is a characteristic of many Agile teams but does not specifically address the need for long-term stability.

D . A shared services team supports other teams by providing specialized skills but is not focused on long-term projects with budgeting needs.

The three phases of Disciplined Agile Delivery (DAD)'s delivery life cycle are:

Inception: This phase focuses on getting the project off the ground. It includes identifying stakeholders, understanding the vision, defining the initial scope, and planning for the necessary resources and timeline.

Construction: This phase involves building the solution incrementally and iteratively, with continuous delivery of working software and regular stakeholder feedback.

Transition: This phase prepares the solution for release into production or the marketplace. It includes final validation, user training, deployment planning, and release management.

Other options are incorrect:

A . Commencement, Creation, Evolution are not standard DAD phases.

B . Initiation, Foundation, Conversion do not match DAD terminology.

C . Introduction, Substance, Alteration are not relevant to DAD.

Therefore, the correct answer is D. Inception, Construction, Transitions.