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

Disciplined Agile (DA) milestones are based on Lean governance principles. Lean governance emphasizes lightweight control mechanisms and focuses on achieving desired outcomes rather than enforcing compliance through heavy documentation or bureaucratic processes. DA milestones are established to ensure that value is being delivered efficiently and effectively throughout the lifecycle, with decisions made based on evidence and validated learning rather than detailed documentation (A) or strict adherence to lifecycle stages (D). While continuous integration (C) can support Lean governance by providing frequent, actionable insights into product development, it is not the foundation upon which DA milestones are based.

False: On an Agile team, the team members do not accept or reject their own work at the iteration demo. Instead, the Product Owner, along with stakeholders, is responsible for accepting or rejecting the work presented. The iteration demo (or sprint review) is an opportunity for the team to showcase their completed work to stakeholders and gather feedback. The decision to accept the work is based on whether it meets the Definition of Done, fulfills the acceptance criteria, and aligns with stakeholder expectations.

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 process goalCoordinate Activitiesis most likely to offer potential techniques for aligning and working more effectively with people in the marketing department. In Disciplined Agile, "Coordinate Activities" focuses on how teams can effectively collaborate both internally and externally with other departments or stakeholders. This goal includes strategies for synchronizing work, managing dependencies, and establishing communication channels, which are essential for ensuring alignment with the marketing department and facilitating cross-functional collaboration. Other options such as "Address Risk" or "Explore Scope" do not directly relate to inter-departmental coordination, while "Sales and Marketing" is not a specific process goal within the Disciplined Agile framework.

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.

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.

The primary role of the Product Owner in Disciplined Agile is to "build the right product." This means the Product Owner is responsible for defining and prioritizing the product backlog, ensuring that the development team works on features that deliver the most value to the stakeholders and align with the business objectives. The Product Owner acts as the voice of the customer, making critical decisions about the product's direction, features, and functionality. The other options (B, C, and D) may involve activities related to product development, but they do not encompass the core responsibility of building the right product.

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, any step in the value stream that does not directly contribute to creating the product or delivering value to the customer is considered waste. This aligns with the Lean principle of identifying and eliminating waste to improve efficiency and effectiveness. Therefore, if a step is not necessary for creating the product, it is classified as waste.

The primary purpose of creating a Minimum Viable Product (MVP) is toestablish the validity of a hypothesisby testing a prototype with real customers. In Disciplined Agile, an MVP is a minimal version of a product designed to test assumptions and learn about market needs with the least amount of effort and resources. By putting a prototype in front of customers, teams can validate or invalidate their hypotheses, gather user feedback, and make informed decisions on future development. This aligns with the lean and agile principle of delivering value quickly and efficiently while minimizing waste. Other options, like committing to continuous improvement or creating a marketable product, are secondary to the core purpose of hypothesis validation through MVPs.

"Enterprise awareness" in the Disciplined Agile framework means understanding and considering the needs and goals of the broader organization while making decisions at the team level. It does not mean standardizing processes across all teams; rather, it encourages teams to align with organizational objectives and practices in a way that fits their unique context. Therefore, the statement is false. Standardizing processes would contradict DA’s core principle that "Context Counts," which supports flexible and situationally appropriate process choices.

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.

Reducing work-in-progress (WIP)is intended to increase focus, reduce lead time, and create a greater incentive to prioritize. It helps teams deliver value more quickly and efficiently by concentrating on fewer items at a time, minimizing context-switching, and reducing the chances of burnout.Option A isnota benefit of reducing WIP, as reducing WIP discourages multi-tasking between many high-priority items. In fact, reducing WIP aims to prevent multi-tasking, which is often counterproductive.

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.

Pushis when work isgiven 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.

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 isC. 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 deliveryis 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.

Estimating in hours instead of pointsmay not help in improving predictabilitybecause time-based estimates can often be inaccurate and can vary widely based on individual productivity and context. Using story points allows teams to focus on relative size and complexity, making it easier to compare work items and plan iterations more predictably.

Options B (reducing technical debt), C (reducing feedback cycles), D (respecting WIP limits), and E (adopting a test-first approach) all contribute to improving predictability by promoting consistent, high-quality 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.

Among the four views that describe Disciplined Agile (DA),Practicesare best represented asgoal diagrams. DA goal diagrams visually depict the process goals and decision points that teams can navigate to choose the best way of working (WoW) in their specific context. These diagrams provide guidance on options, techniques, and strategies for achieving different agile and lean practices.

Options B (Lifecycle models), C (Principles and guidelines), D (Roles and responsibilities), E (Team structures), and F (Workflows) describe other aspects of DA but do not specifically represent 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 Minimum Business Increment (MBI) is a tool used in Disciplined Agile to sequence work in a way that delivers value quickly. An MBI represents the smallest piece of functionality that delivers business value to customers or stakeholders, and it is fully usable upon release. By focusing on MBIs, teams can prioritize work that maximizes the delivery of value, ensures faster feedback, and enables quicker realization of benefits.

Options A (Planning Poker) and C (Minimum Viable Product, MVP) are related to estimation and product development strategies, while Option C (WIP limits) focuses on managing workflow efficiency rather than directly sequencing work for quick value delivery.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

The "Marketing" process blade in the Disciplined Agile framework provides strategies to ensure successful interactions with the external world about your organization, products, and offerings. Marketing focuses on understanding customer needs, communicating the value proposition of products and services, and engaging effectively with potential and current customers to build brand awareness and drive sales. Other options like Portfolio Management (A), Product Management (B), Sales (C), and Business Operations (D) have different focuses and do not specifically cover the broad external communication strategy and positioning that Marketing does.

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

In the context of roles in Disciplined Agile (DA), it is true that a person may take on more than one role within a team. DA promotes flexibility and adaptability in team roles, allowing team members to wear multiple hats depending on their skills and the team's needs. Option A (highly specialized team members) contradicts DA’s principle of cross-functional teams. Option C incorrectly assigns the facilitator role to the Product Owner, and Option D does not accurately describe the Team Lead's responsibilities in DA.

Disciplined Agile provides a solid foundation for business agility by (A) creating awesome teams that foster joy and (D) describing the trade-offs associated with a range of options. Creating awesome teams involves building a positive and productive team environment where team members are engaged, motivated, and empowered. Describing trade-offs allows teams to make informed decisions by understanding the implications of different practices and approaches. While "enforcing adherence to organizational standards" (C) and "defining a framework for agility at scale" (B) are part of Disciplined Agile, they are not specifically highlighted as primary ways DA fosters business agility.

The statement isfalse. In Disciplined Agile (DA), organizations are considered complex adaptive systems, meaning they require adaptive, decentralized, and bottom-up governance approaches rather than rigid, top-down control. Teams are encouraged to be self-organizing and empowered to make decisions that align with their context and the organization's goals. Top-down governance can be too rigid and may stifle innovation, agility, and responsiveness.

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, limiting work-in-progress (WIP) is crucial to optimizing flow within a team. By reducing the number of tasks being worked on at any given time, teams are better able to focus on completing a smaller set of high-priority items, which reduces context switching and increases efficiency. This focus leads to faster delivery of high-quality work. Options like "A. Pursue multiple goals at a time" and "C. Preventing priority changes" are contrary to the benefits of limiting WIP, and "D. Respect the timebox" is less relevant in the context of optimizing flow. Thus, "B. Create focus" is the correct answer.

The primary function of the "Business Operations" process blade in Disciplined Agile is to provide ongoing support and services to customers and ensure that products function smoothly post-deployment. This involves managing customer relationships, handling support requests, andmaintaining operational stability. Options such as "B. To monitor the competitive landscape" and "D. To ensure cash flow in the organization" do not align with the core function of Business Operations. "C. To monitor and guide teams to remove barriers" is more aligned with the roles of leadership and governance. Hence, "A. To provide services to customers and support your products" is the correct answer.

The primary risk addressed by thestakeholder vision milestoneisthat 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.

Guided continuous improvement is not limited to using a prescriptive framework or model. In Disciplined Agile (DA), guided continuous improvement can be achieved by using principles, guidelines, and practices that are adaptable to various contexts. It emphasizes learning and improving based on feedback, rather than following a strictly defined process.

The Disciplined Agile (DA) principle of "Accelerate value delivery" reflects the importance of minimizing the cost of delay. Cost of delay measures the impact of time on the value delivery, emphasizing the need to deliver valuable work quickly to maximize its benefits. While Option D (Optimize flow) is related to managing work effectively, it does not specifically highlight the urgency of reducing the cost of delay. Options A (Keep workloads within capacity) and C (Collaborate proactively) are important DA principles but do not directly address this concept.

The final step in the "Choose your WoW" (Way of Working) process isGuided 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.

False: Fulfilling the requirements does not necessarily mean that the customer is delighted. In Disciplined Agile and other Agile frameworks, delighting customers goes beyond merely meeting the stated requirements. It involves exceeding customer expectations, delivering unexpected value, and providing a positive user experience. A product or service may fulfill the technical or functional requirements but fail to delight if it does not provide an exceptional user experience, is not easy to use, or does not address the underlying needs or desires of the customer comprehensively. The goal is to deliver true value, which often means going beyond the baseline requirements.

Theteam leadisnot responsible for securing fundingfor 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.

Guided continuous improvementextends 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.

It istruethat, 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.

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.

For an Agile or Lean project team, the aim of theConstruction phaseis to develop aconsumable solutionin 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 decision to keep a single Scrum team of 12 members, despite the increase in size, reflects the Disciplined Agile principle ofbeing pragmatic. This principle involves making context-sensitive decisions that balance competing priorities. In this case, although Scrum recommends smaller team sizes (ideally 10 or fewer), the team prioritized cohesiveness and delivery over strict adherence to the guideline. By being pragmatic, they chose an approach that best suits their current context and promotes better collaboration and productivity, even if it meant working with a slightly larger team. This decision also demonstrates a balance between adhering to best practices and adapting to the unique needs and dynamics of the team.

In the Disciplined Agile (DA) approach, the role of a team lead, such as a Scrum Master or Agile Coach, includes supporting team members and helping them overcome obstacles. Option B reflects this mindset: having a conversation with the team member to understand the root causes of their struggle and collaboratively seeking solutions. This approach aligns with agile principles of servant leadership, empathy, and collaboration. It encourages open communication, trust-building, and personal development, which are core to maintaining a high-performing and motivated team.

Providing time management training (Option A), holding a one-on-one meeting focused on failures (Option C), or redistributing work without addressing underlying issues (Option D) are less aligned with the values of Disciplined Agile, as they do not directly address the specific impediments faced by the team member or promote a supportive and growth-oriented team culture.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI

The Disciplined Agile principles that best address the need to consider the bigger picture areEnterprise AwarenessandContext Counts.

Enterprise Awarenessensures that teams understand how their work fits within the broader organizational context, including alignment with corporate objectives, policies, and other teams. This principle encourages teams to think beyond their immediate tasks and consider the overall goals and constraints of the organization.

Context Countsemphasizes that the approach to work should be tailored to the specific situation and environment. It promotes the idea that different contexts require different strategies, and there is no one-size-fits-all approach. Both principles encourage a holistic view that considers the larger organizational and environmental factors influencing team decisions.

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).

In a Disciplined Agile team, the role of the team lead is not typically to make decisions on product priorities or the product roadmap. These responsibilities usually belong to the Product Owner, who represents the customer and stakeholders, prioritizes the backlog, and defines the product vision. The team lead's responsibilities include guiding the team through improvement actions (A), facilitating collaboration (B), and helping the team evolve their Way of Working (WoW) (D). Hence, "C. Providing timely decisions on priority and product roadmap" is not a role for the team lead.

The Exploratory Life Cycle is adopted when there is a need to bring a new product or service to market, and the customer requirements are uncertain. This life cycle is characterized by a high degree of exploration and experimentation, where the team continuously learns and adapts based on customer feedback and market conditions. Options A and B are incorrect because they refer to evolving an existing product or service rather than bringing a new one to market. Option E is also incorrect because it assumes the requirements are well understood, which would not necessitate an exploratory approach.

In Disciplined Agile, the "Construction" phase is where a consumable solution is developed incrementally and collaboratively. This phase is focused on creating working software or products in small, manageable increments, incorporating feedback, and ensuring that the solution evolves to meet customer needs. The Construction phase emphasizes collaboration, incremental development, and continuous integration to build a high-quality product iteratively.

Options A (Execution) and D (Transition) do not accurately describe the phase focused on collaborative and incremental solution development. Option B (Inception) refers to the initial phase where the scope, vision, and feasibility of the project are established.

References:

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

PMI’s Disciplined Agile Senior Scrum Master (DASSM) materials.

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.

It is false to say that all the process goal diagrams need to be explored while determining the initial Way of Working (WoW). In Disciplined Agile (DA), teams are encouraged to focus on the most relevant process goals based on their specific context, objectives, and constraints. Exploring every possible process goal would be impractical and unnecessary; instead, the team should prioritize and tailor their WoW to address the most critical factors for their situation.

Top of Form

Bottom of Form

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 process goal most likely to offer potential techniques to address concerns that the development team does not understand the overall business process isExplore 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.

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.

True: On an Agile team, the Product Owner is the go-to person for business domain information. The Product Owner is responsible for defining the product vision, managing the product backlog, and acting as the primary liaison between the development team and stakeholders. They provide clarity on business requirements, priorities, and customer needs, ensuring that the team understands what is needed to deliver value. The Product Owner's deep knowledge of the business domain makes them the authoritative source for business-related questions and guidance.

We can identify our challenges "by visualizing our workflow to identify what blocks it." Visualizing the workflow, such as through a Kanban board or value stream map, helps teams see where bottlenecks, delays, or inefficiencies occur. This visualization makes it easier to pinpoint problems and areas for improvement. While holding retrospectives (B), finding where frustrations arise (C), and trying good practices to identify failures (D) are all valuable techniques, visualizing workflow is a foundational Lean practice for identifying and addressing challenges in real time.

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.

For an Agile or Lean project team, the aim of the Inception phase is to "perform sufficient work to initiate the endeavor and obtain agreement as to the overall vision with their stakeholders."The Inception phase involves developing a shared understanding of the project's vision, objectives, and scope, ensuring that all stakeholders are aligned and have agreed on the goals. While options A, B, and C involve planning, modeling, or building, the primary goal of the Inception phase is to set a clear direction and establish alignment among stakeholders.

It is false to say that if you are following Scrum, you cannot use Disciplined Agile (DA). DA is a toolkit that allows teams to adopt and tailor practices from multiple frameworks, including Scrum. DA is designed to complement existing agile frameworks by providing additional flexibility and guidance to improve team processes and outcomes. Therefore, Scrum and DA can be used together effectively.

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.