The final step in the "Choose your WoW" (Way of Working) process is Guided Continuous Improvement . This step emphasizes the need for teams to continually assess and refine their way of working based on outcomes, feedback, and learning. The focus is on applying a structured approach to improvement, where teams iteratively experiment with new practices and techniques and adapt based on what works best in their context.

Options B (Make some choices), C (Connect the dots), and D (Select the best-fit life-cycle) are earlier steps in the process, which involve defining the team's initial way of working.

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.

One of the significant changes in finance processes within Agile teams is that teams are typically given a definite budget to manage. In an Agile environment, teams are empowered to make decisions and manage their finances within the constraints of their allocated budget. This approach ensures better control over expenditures and accountability. Option A (less oversight), C (structured around functions), and D (not needing to monitor cash flows) do not accurately describe changes in financial management in agile teams.

Top of Form

Bottom of Form

In Disciplined Agile, teams avoid spending a considerable amount of time at the beginning to lock down the architecture and design of the product. Instead, DA promotes an iterative and incremental approach, where architecture and design evolve as the team gains more understanding of the project requirements and constraints. This adaptive approach reduces the risks associated with upfront design and supports flexibility and responsiveness to change. Therefore, the correct answer is "False" because DA does not advocate for a long, upfront architecture and design phase.

Top of Form

Bottom of Form

In the context of Disciplined Agile Delivery (DAD), the three common phases across project life cycles are Inception, Construction, and Transition. "Inception" involves initial planning and setup; "Construction" is where the product or solution is developed iteratively; and "Transition" focuses on deploying the solution to the stakeholders or end users. Options A (Inspiration) and D (Modulation) are not standard phases in the DA or agile frameworks.

The main role of the team lead in Disciplined Agile is to ensure that the team builds the product right . This involves guiding the team to follow the appropriate practices, ensuring high-quality standards, and removing any impediments that could affect the development process. The team lead facilitates the team’s work, helps them adhere to their chosen way of working, and ensures that the product meets the necessary quality standards and fulfills customer requirements. While other roles, such as product owner or architect, might focus more on defining the right product or coordinating efforts, the team lead's primary responsibility is to ensure proper execution and adherence to quality practices.

The "Exploratory" lifecycle in Disciplined Agile (DA) is most suitable for a lean startup model that focuses on quickly validating ideas and narrowing down candidate projects to pursue. The Exploratory lifecycle is designed for situations where the primary goal is to learn and validate assumptions rapidly through experimentation and feedback. This aligns with the lean startup approach of testing hypotheses, iterating quickly, and adapting based on validated learning. Options A (Continuous delivery Agile), B (Agile), D (Lean), E (Continuous Delivery Lean), and F (Program) do not focus specifically on the rapid learning and experimentation phase that characterizes the lean startup model.

An iteration backlog is created at the beginning of each sprint (or iteration) during the iteration planning meeting. The iteration backlog consists of a set of user stories or tasks that the team commits to completing during that specific iteration. Option A (beginning of each project) is incorrect because the iteration backlog is not created once for an entire project but is defined at the start of each sprint. Option B (defining the MBI) and Option C (planning a Kanban board) do not specifically align with the concept of an iteration backlog in agile.