Pass the PMI PMI Agile DASSM Questions and answers with CertsForce

Disciplined Agile projects do not aim to maximize work-in-progress (WIP). Instead, they aim to minimize WIP to increase efficiency and reduce waste. By limiting WIP, teams can focus on completing tasks faster and delivering value more frequently. This approach is aligned with lean principles, which discourage multitasking and encourage teams to complete work items before starting new ones. Therefore, the statement that disciplined agile projects try to maximize WIP is false. The goal is to optimize the flow of work, not overload the team with too many concurrent tasks.

Top of Form

Bottom of Form

When changing legacy code, the recommended approach in Disciplined Agile is to "Add a test first, then change it." This practice is aligned with Test-Driven Development (TDD) and ensures that any modifications made to the legacy code do not introduce new defects. By writing tests before making changes, you establish a safety net that confirms the existing functionality remains intact, and the new changes work as expected. Rewriting the code (B), delegating the task (C), or changing the code before adding tests (D) can increase risk and are not recommended practices.

The responsibility for choosing the team's lifecycle in Disciplined Agile (DA)depends on the context. DA promotes a context-driven approach where decisions are made based on the specific needs, objectives, and constraints of the team and the organization. In some cases, the team itself may choose the lifecycle that best fits its way of working. In other scenarios, the decision could be influenced by an Agile coach, team manager, or organizational guidelines. Therefore, it is not a one-size-fits-all answer, and the context determines who is best suited to make this decision.

An advantage of aproject teamas opposed to long-standing product teams is agreater focus on delivery and short-term goals. Project teams are typically formed to achieve specific, time-bound objectives, and their primary focus is on delivering the project outcomes within the set timeframe. This can lead to an intense focus on immediate deliverables and short-term results.

Options A (motivation to learn and evolve the WoW) and D (bringing work to the team) are more applicable to long-standing teams, while Option C (long-term focus) is not typically an advantage of project-based 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.

A team should consider entering the transition phase when the product meets all stakeholder expectations. In Disciplined Agile, the transition phase involves finalizing the product or solution for release. This phase is initiated when the product is deemed ready and all necessary criteria, including stakeholder expectations, have been fulfilled. Options A (new MBI developed), C (operational teams ready), and D (MVP ready) may be relevant in other contexts but do not specifically trigger the transition phase.

Avalue streamin Disciplined Agile and Lean thinking is defined as the sequence of steps that an organization undertakes to deliver a product or service to customers. This encompasses all activities, from identifying customer needs to delivering the final product or service, and includes both value-adding and non-value-adding activities. The goal of managing a value stream is to optimize the flow of value to the customer by identifying and eliminating waste, improving efficiency, and enhancing overall effectiveness.

Using a Pull system means that work is pulled by the team members only when they are ready to start the next piece of work. It does not mean that all team members are pulled in to do the work. Instead, the team pulls in work based on capacity and readiness, ensuring a manageable workflow and limiting Work In Progress (WIP). Options B, C, and D describe principles that align with a pull system, but A does not.

Using Lean thinking, we should be managingthe value stream. Lean thinking focuses on optimizing the entire flow of value from the initial customer request to the delivery of the final product or service. Managing the value stream involves identifying and eliminating waste, reducing delays, and ensuring smooth flow across all steps in the process to deliver maximum value to the customer. Lean emphasizes managing the process flow rather than micromanaging individual steps or people, allowing for continuous improvement and more efficient operations.

Plan Do Study Act (PDSA) is a four-step iterative process used for continuous improvement. It helps teams to better understand the effectiveness of their actions and identify opportunities for improvement. The cycle involves planning an action (Plan), executing it (Do), studying the results (Study), and acting on what is learned (Act). While reflecting on whether the team is working on the correct things (B) or improving plans (C) are parts of continuous improvement, PDSAis primarily aimed at understanding and improving the results of actions. Option D (providing justification when something goes wrong) is not the purpose of PDSA.

Disciplined Agile (DA) is described as a process-decision toolkit that provides tailored guidance to help teams and organizations optimize their way of working in a context-sensitive manner. Unlike a rigid methodology, DA offers flexibility by allowing teams to choose from a variety of agile, lean, and traditional practices that best fit their situation. DA emphasizes that there is no "one-size-fits-all" approach; rather, it empowers teams to make informed decisions based on their specific needs and circumstances. Option A focuses on project alignment, which is only one aspect of DA. Options C and D do not accurately reflect the comprehensive, adaptive nature of DA as a toolkit designed for broad applicability.

Top of Form

Bottom of Form