DASSM Disciplined Agile Senior Scrum Master (DASSM) Exam Questions and Answers

True : A value stream does indeed begin and end with a customer. In Disciplined Agile, a value stream represents the sequence of activities an organization undertakes to deliver a product or service that is of value to a customer. It starts with a customer need or demand and ends with the delivery of value to that customer. The focus on value streams helps organizations optimize the flow of value, reduce waste, and enhance customer satisfaction by aligning all activities around delivering what the customer truly needs.

In the Disciplined Agile framework, the principle of "Context Counts" emphasizes the importance of tailoring practices to fit the specific situation or context of the team. In this scenario, the team decided to skip the daily standup meetings because they were co-located, and the meetings were not adding value. This is an example of making a context-specific decision based on the team's unique circumstances, which aligns with the DA principle of "Context Counts." Options A (Being awesome), B (Enterprise awareness), and D (Choice is good) do not accurately capture the rationale behind the decision to modify the practice based on context.

According to Disciplined Agile and broader agile principles, complex adaptive systems, such as software development environments, cannot be fully understood by analyzing individual parts in isolation. The nature of complex adaptive systems is that they involve multiple interacting components, and their behaviors emerge from these interactions. Therefore, understanding the whole system requires examining the relationships, feedback loops, and patterns that arise within the entire context, not just the individual parts. This concept is grounded in systems thinking, a key component in agile methodologies, which encourages viewing the system holistically.

Enforcing adherence to organizational standards is an important aspect of Lean governance in the Disciplined Agile framework. Lean governance involves ensuring that teams follow defined policies, procedures, and standards to align with the organization's goals while allowing for flexibility and responsiveness. It balances the need for governance with the principles of Lean, ensuring that teams work within the boundaries of organizational standards while continuously improving their processes.

Minimum Business Increments (MBIs) and Minimum Viable Products (MVPs) have different intentions. An MVP is designed to test a new product idea quickly and cost-effectively, with minimal functionality, to learn from customer feedback. An MBI, on the other hand, represents the smallest piece of business functionality that can deliver value to customers and stakeholders while aligning with strategic goals. While both aim to deliver value quickly, the MBI focuses on delivering tangible business value, whereas the MVP is more about validating product-market fit.

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, PDSA is 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

If a team completes the work in their iteration backlog earlier than expected, the best course of action is to work with the product owner to pull more work from the product backlog into their iteration backlog. This approach keeps the team productive and focused on delivering value, rather than waiting or working on non-critical tasks. Option A suggests working on non-critical tasks, which does not maximize value delivery. Option B (waiting for other groups) is not a productive use of time. Option D (reporting differences in completion time) is helpful for future planning but does not address the immediate need to keep the team engaged.

When introducing new features to a large, existing product, the product team should employ the Minimum Business Increment (MBI) technique. In the Disciplined Agile (DA) framework, an MBI is a small, releasable component that delivers recognizable business value to a customer or user. Unlike a Minimum Viable Product (MVP), which is often used for new products or market exploration, an MBI is suitable for incrementally enhancing existing products by delivering value in manageable pieces. This approach allows teams to release new features more frequently and receive feedback more rapidly, helping them to prioritize future work based on actual customer and business needs. Continuous Integration (A) is a practice of merging code frequently to prevent integration issues, while Pull System (B) is related to Lean practices of managing work in progress. MVP (D) is generally used for launching new products rather than adding to an existing one.

The Product Backlog is the artifact that collects all the work flowing to the team in Agile practices, including Disciplined Agile (DA). It is an ordered list of everything that might be needed in the product, serving as the single source of work undertaken by the team. This backlog includes user stories, features, enhancements, bug fixes, and technical tasks. It is prioritized by the Product Owner to ensure that the team works on the most valuable items first.

Options B (Business backlog) is not a standard Agile artifact. Option C (Iteration backlog) is a subset of the Product Backlog, containing items chosen for the current iteration. Option D (Release roadmap) is a higher-level plan for future releases, not a collection of all work items.

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 primary risk addressed by the stakeholder vision milestone is that your primary stakeholders agree to your strategy . This milestone ensures alignment and consensus among key stakeholders regarding the project's overall vision, goals, and strategic approach. Achieving this agreement is critical to securing buy-in, support, and commitment from stakeholders, which helps to mitigate the risk of misalignment and conflicting expectations as the project progresses. Other risks, like architectural strategy viability, business case viability, or a realistic release plan, are addressed by other specific milestones or checkpoints in the Disciplined Agile framework.

The team lead is not responsible for securing funding for the team. In a Disciplined Agile framework, funding responsibilities typically fall under the purview of management or a sponsor. The team lead focuses on enabling the team, removing impediments, facilitating collaboration, and coaching the team toward effective delivery practices.

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 process goal most likely to offer potential techniques to address concerns that the development team does not understand the overall business process is Explore Scope . In Disciplined Agile, "Explore Scope" focuses on defining and understanding the scope of the project, including the business processes that are relevant to the product being developed. It involves techniques such as creating process maps, using business process modeling, or conducting domain workshops to help the team understand the overall business context and requirements. This ensures that the development team has a comprehensive understanding of the customer requirements and the broader business environment in which the product will be used.

Disciplined Agile (DA) is an agnostic hybrid approach that draws upon various ideas, principles, and practices from multiple agile and lean methodologies, including Scrum, Kanban, Extreme Programming (XP), Lean, and others. It does not adhere strictly to one methodology but instead provides a toolkit that allows teams to tailor their ways of working based on their specific context, objectives, and constraints. Options B (Agile), C (Iterative), and D (Lean) are more specific frameworks or approaches, whereas Disciplined Agile explicitly combines multiple methodologies in an agnostic manner.

The Marketing process blade in Disciplined Agile is responsible for crafting an appealing roadmap of the organization's offerings in close conjunction with Product Management. Product Management helps define the product vision, strategy, and features, while Marketing ensures that these offerings are effectively communicated to the target audience. Options A (Portfolio management), C (Finance), D (Business Operations), and E (Control) do not primarily focus on this collaboration.

Top of Form

Bottom of Form

Lean governance practices, as described in the PMI Disciplined Agile (DA) framework, focus on enabling teams to deliver value in a lean, efficient manner. This involves creating business value regularly (Option A), empowering the team (Option C), providing appropriate Return on Investment (RoI) (Option D), and presenting accurate and timely information (Option E). However, "Directing the team with clear tasks" (Option B) contradicts the lean governance principles, which emphasize empowering teams to make decisions and self-organize rather than being directed. Therefore, directing the team with clear tasks is not a lean governance practice.

When analyzing a team’s context for tactical scaling, Disciplined Agile (DA) considers factors such as "Team Size" and "Dynamics." "Team Size" affects communication, coordination, and overall team performance, while "Dynamics" refers to how well the team members work together, the existing relationships, and the level of trust and collaboration within the team. Options A (Demographics) and B (Best Practices) are not primary tactical scaling factors. Option C (Budget) is an important project consideration but not specifically a tactical scaling factor within the DA framework.

Top of Form

Bottom of Form

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.

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

A Minimum Viable Product (MVP) is a product with the minimum set of features needed to satisfy early customers and gather feedback for future development. The primary purpose of an MVP is to validate product assumptions, understand user needs, and guide subsequent iterations based on real user feedback. This iterative approach helps in aligning the product with customer expectations and reducing the risk of failure.

Options A (last iteration of development), B (not yet ready to be sold), and C (used for demonstration only) do not accurately reflect the primary purpose of an MVP in Disciplined Agile.

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.

Push is when work is given to people . In a "push" system, tasks or work items are assigned to individuals or teams regardless of their current capacity or workload. This can lead to overburdening, inefficiencies, and bottlenecks. In contrast, a "pull" system allows team members to take on new work only when they have the capacity to do so, promoting smoother flow and reducing waste. Agile methodologies generally favor a pull approach to optimize flow and enhance team autonomy and efficiency.

It is true that, in the initial stages, a team's way of working (WoW) may be determined more by enterprise guidelines or the recommendations of a coach. This is acceptable in Disciplined Agile, especially when teams are new to agile practices and need direction. Over time, however, teams are expected to evolve and refine their WoW based on their unique context, learning from experience, and continuous improvement.

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 PMI Disciplined Agile framework presents various process choices in a goal diagram to allow teams to select the most appropriate practices for their context. However, not all choices are suitable for every situation. The goal diagram illustrates multiple options to provide flexibility, but teams need to assess their specific circumstances, constraints, and goals to determine which process choices are viable. Therefore, it is true that not all process choices may be viable in a given situation.

In a program team within the Disciplined Agile (DA) framework, each sub-team does not need to have the same Way of Working (WoW). DA promotes flexibility and recognizes that different teams may choose different WoWs that best fit their specific context, goals, and constraints. This approach allows each sub-team to optimize its process for maximum effectiveness, even if that means adopting different methodologies or practices.

For a long-term project with potential for significant budgeting and tracking overhead, the Scrum Master should set up a long-standing team. According to the Disciplined Agile framework, long-standing teams are stable teams that remain intact across multiple projects or over a long duration. These teams are cross-functional, meaning they have all the necessary skills to deliver value and are more likely to develop high levels of collaboration and productivity over time. While cross-functional teams (B) are a necessary characteristic, "long-standing team" (A) is the best answer for a long-term project with significant overhead, as it implies continuity and sustained team dynamics. A project team (C) is typically formed for a short-term, specific project and disbanded afterward. A shared services team (D) provides specialized skills and services to various teams and is not typically suited for the dedicated effort required by long-term projects.

While "Delight customers" is an important goal in agile and Disciplined Agile (DA) practices, it is not listed as one of the key principles to keep in mind when choosing and evolving a team’s Way of Working (WoW). The key principles are "Pragmatism" (A), "Choice is good" (C), and "Context counts" (D). These principles emphasize practical decision-making, recognizing that different situations require different approaches (choice is good), and tailoring the WoW to the specific context.

Disciplined Agile Delivery (DAD) defines a delivery life cycle consisting of three phases: Inception, Construction, and Transition. Inception focuses on initial project planning, stakeholder alignment, and getting the team ready to work. Construction is the phase where the team builds the solution in iterations, delivering incremental value. Transition involves preparing the solution for release, including final testing, deployment, and user training. The other options (A, B, C) do not accurately reflect the terminology and phases used in the DAD life cycle.

A complex adaptive system (CAS) is characterized by the property that understanding the individual components does not lead to a perfect understanding of the entire system's behavior. This is because CAS are dynamic networks of interactions where the behavior of the whole system emerges from the interactions among its parts. Option A describes a process but does not capture the essence of complexity. Option C suggests a deterministic algorithm, which is not accurate for describing CAS. Option D touches on evolving ways of working, but it does not correctly define the nature of CAS in the context of complexity theory.

In Disciplined Agile, the role of a DevOps Engineer is not necessarily filled by an operations person assigned to an Agile or Lean team. The DevOps role can be filled by individuals from either the development or operations side, or even someone with cross-functional expertise. The focus of the DevOps role is to foster collaboration between development and operations to enable continuous integration, delivery, and deployment. It is not limited to being an "operations person," but rather emphasizes the integration and collaboration needed to improve the flow from development to operations.

Guided continuous improvement extends the Kaizen loop strategy by providing structured, context-specific guidance to teams on how to identify and implement techniques likely to be effective for their unique circumstances. This method emphasizes learning from experience, adjusting practices based on outcomes, and aligning improvements with the organization's goals, enhancing the team's ability to adapt and improve continuously.

Options A (Cross-team learning), C (Explicit workflow policies), and D (Communities of Practice) are valuable for learning and improvement but do not specifically focus on providing guided, context-sensitive strategies for improvement.

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.

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.

In the Disciplined Agile (DA) framework, the Iteration Demo is the ceremony where the team presents the work completed during the iteration to stakeholders and other team members. This is the primary opportunity to obtain feedback on the increment of product or work that was developed. The feedback gathered during this demo is crucial for making any necessary adjustments in subsequent iterations. Other ceremonies like Daily Stand-up (B), Iteration Planning (C), or Retrospective (D) have different focuses. For example, Retrospective (D) is used for process improvement feedback, not product feedback.

During the Inception stage of a Disciplined Agile project, the team typically focuses on defining the project's vision, goals, and scope, as well as identifying high-level architecture and a test strategy. The deployment strategy, which details how the product will be released to the users, is generally determined later in the project when more is known about the product's architecture and functionality. Therefore, "B. Deployment strategy" is the correct answer, as it may not be decided during the Inception stage.

Top of Form

Bottom of Form

The three categories of process blades in Disciplined Agile (DA) are:

Disciplined DevOps: Focuses on integrating development and operations to streamline workflows, reduce bottlenecks, and ensure continuous delivery and deployment.

Disciplined Agile IT: Encompasses practices that support IT functions, such as Enterprise Architecture, Data Management, IT Governance, and IT Operations.

Disciplined Project Management Office (PMO): Provides strategic alignment, governance, and guidance to ensure that projects and initiatives align with organizational goals and deliver value.

Disciplined Agile Delivery (C) is a process blade itself, not a category, and Disciplined Kanban (D) is not a recognized process blade in DA.

The primary advantage of breaking a project into phases is that it enables teams to focus on critical themes and ease of governance. Phases provide a structure to manage complex projects by focusing on specific objectives or deliverables at each stage, facilitating better planning, monit oring, and control. This approach also makes it easier to align with governance requirements and to make course corrections based on learnings from earlier phases. Options A, B, and C do not capture the strategic and governance benefits provided by phased approaches.

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.

"Ensure production readiness" is one of the process goals in the transition stage of the Disciplined Agile (DA) framework. During the transition phase, the team focuses on finalizing the product and preparing it for release, which includes activities like final testing, user training, and deployment planning to ensure the solution is ready for production use. Options A (Produce a potentially consumable solution) and B (Develop common vision) are more aligned with earlier phases, such as Inception or Construction. Option D (Address risk) is a goal throughout the lifecycle but is not specific to the transition phase.

The "Plan the Release" process goal in Disciplined Agile is most likely to offer potential techniques for providing a cost estimate for the project while recognizing that requirements will evolve over time. This goal involves determining the scope of the release, estimating the effort and cost, and planning for future iterations. It accounts for the fact that Agile teams work in environments of uncertainty and helps them create realistic plans that can adapt as requirements change. Options A (Project Management), C (Explore Scope), and D (Address Changing Stakeholder Needs) are relevant for Agile projects, but "Plan the Release" specifically focuses on creating estimates and planning in an Agile context.

The eight principles of Disciplined Agile are:

Delight Customers : Focus on providing exceptional value to customers.

Be Awesome : Foster an environment where team members feel motivated and supported.

Pragmatism : Make practical decisions based on context, rather than blindly following a methodology.

Context Counts : Recognize that every team and organization operates in a unique context.

Choice is Good : Encourage flexibility by providing multiple options to solve problems.

Optimize Flow : Improve efficiency and effectiveness by focusing on smooth workflow.

Enterprise Awareness : Ensure alignment with organizational goals and strategies.

Organize Around Products/Services : Form teams based on delivering complete products or services, rather than around specialized functions.

These principles promote a flexible, customer-centric, and context-sensitive approach to Agile delivery.

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 correct answer is C. Accelerate value delivery . In the Disciplined Agile (DA) framework, the process goal "Accelerate value delivery" typically requires significant tailoring to suit the specific needs, context, and constraints of the team and the organization.

What is "Accelerate Value Delivery"?

The process goal "Accelerate value delivery" focuses on optimizing the flow of work and reducing delays in delivering valuable outcomes to customers. This goal encompasses various practices and techniques such as reducing batch sizes, implementing continuous integration and delivery, enhancing team collaboration, removing bottlenecks, and improving overall efficiency in delivering products or services.

Achieving this goal requires careful consideration of the team's context, technology stack, existing workflows, and the organization's unique challenges and constraints. As a result, "Accelerate value delivery" is highly tailored to ensure that the selected practices are effective in a specific environment.

Why "Accelerate Value Delivery" Requires a Lot of Tailoring:

Tailoring is necessary because different teams and organizations have varying capabilities, maturity levels, cultural norms, and existing processes. For example, one team might need to focus on improving their DevOps practices, while another may need to address process inefficiencies or enhance cross-functional collaboration.

In Disciplined Agile, there is no one-size-fits-all approach to accelerating value delivery. Teams are encouraged to choose from a range of strategies and techniques that best suit their particular circumstances. This flexibility means that teams must continually assess and adapt their approaches to achieve optimal results, which requires significant customization and tailoring.

Why the Other Options Are Not Correct:

A. Form team: While forming a team may require some tailoring based on the project's needs and team composition, it is generally a more straightforward process with less variation in how it is executed compared to accelerating value delivery.

B. Prove architecture early: This process goal typically involves establishing the technical foundation of the solution early in the project. While it may require some adaptation based on the project's architecture, it does not involve the same level of ongoing tailoring as optimizing the flow of value delivery.

D. Improve quality: Although improving quality involves adopting practices that suit the team's context, it does not typically require as much tailoring as "Accelerate value delivery." Quality improvement is often about adhering to established standards and best practices, which can be more consistent across different teams and projects.

Therefore, C. Accelerate value delivery is the correct answer because it inherently involves a high degree of customization to adapt the approach to the unique context and constraints of the team and organization, consistent with Disciplined Agile's emphasis on context-driven agility.

In the PMI Disciplined Agile framework, the timely delivery of the product as committed is ultimately the responsibility of the entire team. While the Product Owner (Option A) provides direction and prioritization of work, and the Team Lead (Option B) facilitates the process, it is the collective responsibility of the Team Members (Option C) to deliver the product incrementally and meet commitments. Agile teams operate under the principle of shared responsibility and accountability for outcomes, meaning every team member contributes to the delivery process. Other roles, such as Gold User (Option D) and Architecture Owner (Option E), have specific responsibilities but are not accountable for the delivery timeline.

A value stream map is a lean tool that visually maps out the steps in a process from start to finish to identify areas of waste, delays, or inefficiencies in delivering value to the customer. In Disciplined Agile (DA), value stream mapping helps the team identify problem areas where waste occurs, such as bottlenecks, excessive handoffs, or unnecessary steps that do not add value to the customer. By recognizing these problem areas, the team can focus on improving or eliminating them to optimize the value delivery process. Options A, C, and D provide specific strategies for improving processes but do not encompass the broad benefit of identifying problem areas in realizing value.

In Disciplined Agile, shared services teams are not always based on specialization. While shared services teams often consist of specialists (e.g., security experts, database administrators), they can also be cross-functional teams that provide support across different disciplines. The key is that these teams provide services to multiple delivery teams, regardless of whether they are composed entirely of specialists.

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 Disciplined Agile, it is the team members who decide how much work is moved from the product backlog to the iteration backlog. This decision is based on the team's capacity, velocity, and understanding of the complexity and size of the work items. While the Product Owner (B) prioritizes the product backlog, it is up to the team to determine how much of that work can be realistically completed within an iteration. Stakeholders (C), the team manager (D), or the project manager (E) do not make this decision.

In the context of the construction phase of a project, "Prove Architecture Early" is a relevant process goal. During this phase, it is critical to validate the chosen architecture to ensure that it will support the desired functionality and meet quality requirements. This goal focuses on reducing technical risks by building architectural spikes or prototypes to validate key architectural decisions. This helps the team confirm that the architecture is sound before investing heavily in development. Other options like "Explore Scope," "Develop Test Strategy," and "Form Team" are activities relevant to earlier phases (such as inception).

The "Architecture Owner" in Disciplined Agile is responsible for addressing and mitigating key technical risks within a project. This role ensures that the architecture of the solution aligns with the strategic and tactical goals of the organization, guides the team in making architecture-related decisions, and helps in managing technical debt.

Options B (removing impediments) and C (working cross-functionally to deliver the solution) are responsibilities of the Team Lead or Scrum Master. Option D (determining priorities for the solution) is typically the role of the Product Owner.

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.

For an Agile or Lean project team, the aim of the Construction phase is to develop a consumable solution in a collaborative and incremental manner. This phase focuses on delivering working increments of the product that can be consumed by end users or stakeholders. The approach is highly iterative and involves continuous feedback, allowing the team to make frequent adjustments to align with customer needs and expectations. Options B, C, and D do not fully capture the essence of delivering a solution that is ready to be consumed and used by customers.

The best way to eliminate waste in Disciplined Agile is to "eliminate delays in workflow and feedback." Lean principles focus on removing any non-value-added activities (waste) to improve efficiency. By minimizing delays, teams can ensure a smoother flow of work and faster feedback loops, which helps to identify and resolve issues quickly and reduces the time taken to deliver value to customers. While making sure each step is done as quickly as possible (A) or correctly (D) and ensuring people know their job (B) are important, they are not the primary method of eliminating waste according to Lean principles.

The primary advantage of using design thinking, according to DA guidelines, is that it promotes customer empathy and appropriate solutions. Design thinking focuses on understanding the user's needs and creating solutions that are tailored to those needs. Options A, C, and D are not accurate descriptions of design thinking's primary benefit; rather, they reflect misconceptions or partial truths.

The desire of senior management to evolve an organization to be more responsive to changes in the marketplace or environment is best captured by the concept of Business Agility . Business agility refers to the ability of an organization to adapt quickly and effectively to market changes, customer demands, and emerging opportunities, all while maintaining a focus on delivering value. Disciplined Agile promotes business agility by providing a toolkit that helps organizations navigate their unique challenges and choose the best practices to enhance responsiveness and adaptability across all levels of the organization.

In Disciplined Agile, the amount of work to be completed during an iteration is defined by the team members themselves, based on their understanding of their current capacity and velocity. The team collaboratively estimates what they can achieve and commits to completing that work. Option A (the Product Owner) is responsible for prioritizing the backlog but does not dictate the amount of work. Option B (the team lead) facilitates the process but does not decide the work. Option D (the quality tester) is involved in testing completed work but does not determine the iteration's workload.

Top of Form

Bottom of Form

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.

The principle of "Delight customers" in the Disciplined Agile framework encourages teams to exceed customer expectations rather than just meet them. This approach aims to provide exceptional value and experiences that surprise and please customers, thereby fostering loyalty and positive word-of-mouth. Simply meeting expectations is not sufficient to truly "delight" customers; therefore, the statement that delighting customers means just about meeting their expectations is false.

One of the promises of Disciplined Agile (DA) is to ensure psychological safety, which means creating an environment where team members feel safe to express their ideas, take risks, and admit mistakes without fear of criticism or retaliation. Psychological safety allows teams to collaborate more effectively, innovate, and learn from their experiences. Option A (providing a hygienic work environment) refers to physical safety, while Options C (never criticizing) and D (providing counseling) do not accurately capture the essence of psychological safety as promoted in DA.