Pass the PMI Agile DASSM Questions and answers with ExamsMirror

A major challenge that agile teams face withProcurement processesis that these processes are oftennot agile enough. Traditional procurement practices can be bureaucratic, slow, and rigid,making it difficult for Agile teams to respond quickly to changes, integrate new vendors, or adjust to new requirements. Agile teams need flexible procurement processes that allow for iterative and incremental development, quick onboarding of vendors, and adaptive contracting mechanisms.

Options B (vendor compliance), C (preference for in-house teams), and D (no contracting) are not typically the primary challenges Agile teams face with procurement.

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 Disciplined Agile (DA) framework, the role of "Team Member" is primarily responsible for building the product right. Team members, who possess the necessary skills and expertise, work collaboratively to develop, test, and deliver the solution according to the agreed-upon requirements and standards. While the Team Lead (B) facilitates the process and the Product Owner (C) ensures the right product is being built by prioritizing features and managing the backlog, it is the Team Members who actually perform the development work. The Architecture Owner (D) ensures the architectural integrity of the solution but is not solely responsible for building the product itself.

Top of Form

Bottom of Form

Disciplined Agile (DA) emphasizes the use ofautomated measuresto enable data-driven decision-making in projects. This is aligned with the Disciplined Agile Manifesto and principles, which focus on pragmatism, the use of relevant metrics, and fostering continuous improvement within teams.

In Disciplined Agile, metrics are viewed as tools that provide objective insights into project health and progress. The use of automated measures helps to minimize human error and bias, and enhances the reliability of the data being collected. Automated metrics can include lead time, cycle time, throughput, defect rates, and other quantitative data points that can be generated from automated tools (such as Jira, Azure DevOps, etc.). These metrics allow teams to make informed decisions swiftly and adjust their practices and processes based on actual data.

The DA mindset also promotes outcome-oriented metrics rather than activity-oriented ones. This means teams focus on the end results and the value being delivered, rather than just measuring tasks completed or the amount of work done. By favoring automated and objective measures, DA ensures that teams base their decisions on accurate and timely information rather than subjective opinions or potentially misleading scalar measures.

This is also supported by the DA principle that encourages “Optimize Flow Across the Entire Value Stream” – which relies on data-driven decision-making to effectively manage and optimize processes. Overall, automated measures align with DA's goal of achieving agile goals in a pragmatic, context-sensitive manner.

The "Definition of Done" (DoD) is a checklist that specifies the criteria that must be met for a user story or product increment to be considered complete by the team. It provides a shared understanding among team members and stakeholders of what it means for work to be finished. The DoD ensures that all user stories meet a minimum quality standard and are ready for production or release. It is not related to when the team is done with the iteration (B) or with estimating user stories (C).

Even when a project follows a Scrum or Agile lifecycle, it still needs the Inception, Construction, or Transition phases as described in Disciplined Agile (DA). These phases provide a structured approach to project delivery. The "Inception" phase involves initial planning and alignment, "Construction" focuses on iterative development, and "Transition" ensures the final product is ready for release. While Scrum and Agile frameworks focus on iterative and incremental development, DA uses these phases to ensure a comprehensive approach to project management.

The process blade most likely to offer potential techniques for setting up mechanisms for teams to share their learnings with other teams isContinuous Improvement. In Disciplined Agile, the Continuous Improvement blade encompasses activities and practices that foster a culture of learning, adaptation, and improvement. This includes mechanisms for sharing lessons learned, best practices, and knowledge across teams to enhance organizational agility and effectiveness. Techniques under this blade may involve communities of practice, internal knowledge-sharing sessions, retrospectives, and other collaborative activities that support learning and improvement at scale.

A long-lived (stable) team is one that remains intact over multiple projects or iterations, allowing team members to develop strong relationships, trust, and a deep understanding of each other's skills and working styles. This stability leads to two key benefits:

Highly Collaborative:Stable teams develop effective communication and collaboration patterns, which enhance their ability to work together efficiently. They understand each other's strengths and weaknesses and can leverage this knowledge to optimize teamwork and problem-solving.

Trustworthy:Long-lived teams build trust over time, which is essential for open communication, risk-taking, and innovation. Trust enables team members to feel safe sharing their ideas and concerns, which leads to higher engagement, morale, and productivity.

Options A (Projectized) and B (Specifically resourced) are incorrect as they do not directly represent the benefits of having a stable team. Option E (Ability to multi-task) is less relevant, as Agile promotes focused work rather than multi-tasking.

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 Continuous Delivery Lean life cycle is suitable when there is an experienced team working on a product or service where the requirements change frequently, potentially daily. This life cycle supports frequent deployments and quick feedback loops, making it ideal for environments where requirements are dynamic and evolve rapidly. Options A, D, and E do not align with the conditions that necessitate a Continuous Delivery Lean approach, as they involve either less experienced teams or slower-evolving requirements.

In the Disciplined Agile (DA) framework, the architecture of a product is typically proven during the Elaboration phase. This phase focuses on validating the architecture of the solution, mitigating technical risks, and establishing a firm foundation for the project's future iterations. During Elaboration, teams work on refining the architecture, ensuring that it can support future development and will meet the project's quality requirements. The construction phase builds upon this established architecture, and by the Inception phase, the initial vision and feasibility are already defined but not yet validated. Therefore, "A. Elaboration" is the correct answer as it is the phase where architecture is thoroughly proven and refined.

The Disciplined Agile (DA) principle of being pragmatic is characterized by focusing on being as effective as possible and continuously improving. DA encourages teams to choose the best tools, practices, and strategies that suit their specific context, rather than rigidly adhering to a particular methodology or framework. This principle emphasizes a pragmatic, situational approach, where the goal is to achieve optimal results while continuously refining and improving processes. Options A, B, and C relate to aspects of flexibility and adaptation, but they do not fully capture the broader commitment to effectiveness and continuous improvement that defines pragmatism in DA.