PMI DASSM Dumps

According to the Disciplined Agile (DA) manifesto, valuing transparency over false predictability means that it is better to be open and honest about uncertainties and unknowns rather than pretending to have precise control or predictability over future outcomes. This approach builds trust and enables more adaptive and responsive planning. Option A (pointless trying to be predictable) is an oversimplification, Option C (stakeholders don’t need to know about the goals) is incorrect, and Option D, while partially true, does not fully capture the intention of the manifesto statement.

Top of Form

Bottom of Form

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.

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.

The primary role of the Product Owner in Disciplined Agile is to ensure that the team builds the right product. This includes defining and prioritizing the product backlog, making decisions on behalf of stakeholders, and ensuring that the team understands the product vision and customer needs. Options A (coordinate the product), B (organize the product team), and C (inspect the product) are aspects of the Product Owner's responsibilities, but they do not capture the overarching goal of delivering the right product to meet customer needs.

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

According to Disciplined Agile (DA) principles, the maximum frequency of delivering a valuable solution is "several times a day." This reflects a highly agile and responsive way of working, where teams aim to continuously integrate, test, and deliver small increments of value as quickly as possible. Options B, C, and D suggest less frequent delivery, which would not align with DA’s emphasis on maximizing the flow of value delivery to customers.

The process goal of "Explore Scope" in the Disciplined Agile framework focuses on understanding the purpose, domain, and intended usage of a product. This involves clarifying what needs to be delivered, gathering requirements, and determining the boundaries of what is in and out of scope for the product development. When a team is exploring the product's purpose, domain, and usage, they are actively engaging in the process of defining and refining the scope of the work to be done, making Option C the correct answer. Options A, B, and D relate to other aspects of agile project management, but do not specifically address the exploration of scope.

The Retrospective is an important agile ceremony because it provides a dedicated time for the team to reflect on their performance and processes, discuss what went well, what didn’t, and how they can improve moving forward. This continuous improvement mindset is central to agile methodologies, including Disciplined Agile (DA). It helps build a culture of transparency, trust, and learning. Option B is incorrect because the Product Owner is not the focus of the Retrospective. Options C and D do not describe the purpose of a Retrospective in agile practices.

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

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.

In Disciplined Agile, the responsibility for determining the "Way of Working" (WoW) falls primarily on the team members. Disciplined Agile promotes a self-organizing team structure, where team members collaboratively decide on the practices and processes they will use, tailored to their unique context. While roles such as the Product Owner or Team Lead may provide input or guidance, the decision is ultimately a team-driven process. This approach empowers teams to choose the most effective ways of working to meet their goals. Thus, "B. Team members" is the correct answer.

The purpose of an iteration retrospective in Disciplined Agile (DA) is to reflect on the recent iteration and identify areas of improvement, successes, and challenges. The retrospective allows the team to transfer knowledge, insights, and process improvements to subsequent iterations, fostering continuous improvement. This helps the team become more effective and efficient over time.

Option B relates to a daily stand-up, Option C involves iteration planning, and Option D pertains to an iteration review or demo, not a retrospective.

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

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, monitoring, and control. This approach also makes it easier to align with governance requirements and tomake 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.

Disciplined Agile (DA) is best described as aprocess-decision toolkit. Unlike a prescriptive methodology or framework, DA provides a flexible toolkit that helps teams and organizations make informed decisions about their way of working based on their unique context. It offers guidance on various agile, lean, and traditional practices, and helps teams choose the most effective strategies for their situation. DA focuses on pragmatism and context-driven choice, encouraging teams to adopt and adapt practices that suit their specific needs rather than following a one-size-fits-all approach.

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

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.

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

False: In a complex adaptive system, it is generally better to havepatterns of good practicesrather than one best practice. This is because complex systems are characterized by dynamic and unpredictable behavior, where a single best practice may not be applicable or effective in all situations. Instead, using a variety of good practices allows teams to adapt to changing conditions and choose the most appropriate approach for their specific context. Disciplined Agile promotes a flexible, context-driven approach to process decisions rather than a rigid adherence to one best practice.

The process goal "Improve Quality" is most likely to offer potential techniques for addressing technical debt. Disciplined Agile encourages teams to continuously improve the quality of their deliverables, and one of the key aspects of improving quality is to manage and reduce technicaldebt. Techniques under this process goal include refactoring, applying test automation, and implementing continuous integration practices, all of which help address existing technical debt in a structured manner.

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.

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

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.

The Kaizen feedback loop, which is an important concept in Lean and Agile practices, can be summarized as "Plan, Do, Study, Act" (PDSA). This cycle is fundamental to continuous improvement (Kaizen) and is used to iteratively improve processes and products. "Plan" involves identifying a goal or a change to implement; "Do" means implementing the change; "Study" refers to analyzing the results and understanding the impact of the change; and "Act" is about making necessary adjustments or standardizing the change if it is successful. Options A, B, and C do not accurately reflect the PDSA cycle as recognized in Disciplined Agile and Lean methodologies.

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.

In Disciplined Agile (DA), teams should first select the goal diagrams that are most relevant to their specific context and chosen lifecycle. DA provides guidance on choosing strategies and practices that are best suited to the team's unique situation, objectives, and constraints. While it's important to consider goals in which the team lacks experience (A) or that are selected by stakeholders (B), the most effective approach is to focus on those goals that align with the team's current context and lifecycle. Choosing goals that are the easiest to complete (C) might not necessarily contribute to the overall effectiveness or agility of the team.

Top of Form

Bottom of Form

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

DevOpsis a key competency in Disciplined Agile, aiming to create a smooth flow of work from development through to operations. This involves practices such as continuous integration, continuous delivery, and automated deployment, which help to reduce cycle time, improve feedback loops, and ensure the product is always in a deployable state. The focus is on integrating development and operations to deliver value to customers more rapidly and reliably.

Options B (using developers for operations), C (automating testing), and D (involving operational teams in development) are components of DevOps practices, but the primary goal is to establish a seamless workflow.

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 Improvementis essential when the team seeks assistance in identifying feasible improvement opportunities and avoiding risks associated with poor decisions. In Disciplined Agile, continuous improvement is a core principle, but it is recognized that teams may sometimes require external guidance to navigate the wide array of potential changes. This external guidance can help the team focus on the most impactful improvements, avoid common pitfalls,and incrementally enhance their ways of working. Guided continuous improvement helps ensure that the team's efforts are directed towards effective and sustainable changes.

Attributes of a leader in Disciplined Agile include taking risks, inspiring trust, and focusing on goals. Leaders in an agile environment should be willing to take calculated risks to innovate and improve, build trust within their teams and with stakeholders, and maintain a focus on achieving goals and delivering value. Options B (Goes with the flow) and D (Assigns tasks) are less aligned with agile leadership, which emphasizes empowerment over task assignment and adaptability rather than passively following along.

It istruethat any change or improvement in the process is likely to plateau unless efforts are put into constantly reviewing and revising it. Continuous improvement is a core principle of Agile and Disciplined Agile, where teams are encouraged to regularly inspect and adapt their processes to ensure ongoing progress. Without regular reflection and adjustments, improvements can stagnate, and the team may miss opportunities for further optimization and innovation.

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

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.

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.

The architecture owner in Disciplined Agile has several key responsibilities: working with the product owner to define the technical roadmap (A), mentoring and coaching the team on technical practices (B), working to improve the supportability of the product (C), and evolving the design and architecture for the product (E). However, evaluating team members' performance and administering rewards (D) is not within the scope of the architecture owner’s responsibilities. This task typically falls under the purview of people managers or human resources.

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

If the frequency of changes to requirements is very high (almost daily), the Continuous Delivery Agile lifecycle model makes the most sense. This model is designed to handle frequent changes by integrating and delivering work continuously, ensuring that new requirements are incorporated quickly and effectively. Options A (Scrum) and D (Agile) provide iterative approaches, but they may not handle daily changes as efficiently as a continuous delivery model. Option B (Lean) focuses on optimizing flow and reducing waste but does not specifically address handling frequent requirement changes.

The main role of the team lead in Disciplined Agile is toensure 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.

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.

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 main role of the team lead (which can be referred to as a Scrum Master, Team Coach, or Team Lead in Disciplined Agile) is to ensure that the team is building the product in the right way. This involves facilitating the team's process, removing impediments, and coaching them to adopt and optimize Agile practices, ensuring quality and efficiency in delivery. The team lead does not dictate what product to build (which is the role of the Product Owner), nor is their primary role to build the product themselves or coordinate building efforts in a command-and-control manner. Instead, they focus on enabling and empowering the team to deliver high-quality work in alignment with Agile principles.

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.

Disciplined Agile (DA) encourages embracingdiversitybecause diverse teams bring a wide range of perspectives, experiences, and ideas, which can foster innovation and creativity. Diverse teams are better equipped to solve complex problems, adapt to changing environments, and meet varied customer needs. While diversity can sometimes lead to more challenging discussions, it ultimately contributes to higher-quality outcomes.

Options A (reaching consensus faster) and B (mandates) are not primary reasons within the DA framework. Option D (allowing everyone to do what they want) does not reflect a structured Agile approach.

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

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.

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

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.

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 Team Lead, in Disciplined Agile, is responsible for ensuring that the daily coordination meeting (often known as the daily stand-up) happens. While team members participate in the meeting and are responsible for their coordination, the Team Lead facilitates the process and ensures that it takes place consistently. This role helps maintain the cadence and discipline of the daily coordination meeting.

Transparency is a core practice in Disciplined Agile to ensure that all stakeholders, including team members and customers, have a clear understanding of the project's progress and any challenges faced. The reasons for practicing transparency include ensuring everyone knows what is happening (A), improving team morale (B), and meeting customer expectations (D). Delaying bad news to customers contradicts the principle of transparency. Hence, "C. It delays breaking bad news to customers" is not a reason that Disciplined Agile teams practice transparency.

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.

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 FLOW view in Disciplined Agile does not mean that there are no starts and stops in any DA project. Rather, it emphasizes optimizing the flow of work through the system by minimizing delays, reducing bottlenecks, and removing unnecessary handoffs. However, starts and stops may still exist due to various factors such as dependencies, changing priorities, or external constraints.

User stories are a key component in Agile practices, including the Disciplined Agile (DA) framework. They are typically described by the acronym INVEST, which stands for:

Independent: User stories should be self-contained, so they do not overlap with others.

Negotiable: User stories are not contracts; they should leave room for discussion and refinement.

Valuable: Each user story must deliver value to the end user or customer.

Estimable: A good user story can be estimated in terms of the effort required to complete it.

Small: User stories should be small enough to be completed within a single iteration.

Testable: A user story must be testable, meaning it should be possible to determine whether the user story has been completed successfully.

Based on the INVEST criteria, "Achievable" is not a recognized feature of a user story. While achieving a user story is an implicit goal, it is not explicitly mentioned in the standard definition or characteristics used in Agile frameworks such as Disciplined Agile. The features that are essential to a user story are "Negotiable," "Estimable," and "Testable," as they ensure the story is clearly defined, measurable, and valuable to the user.

References:

Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise, Scott Ambler & Mark Lines.

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

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.

The least suitable way to adopt Disciplined Agile Delivery (DAD) is touse any of the prescribed methods and follow to the letter. DAD emphasizes flexibility and the need to adapt practices to the specific context of the team or organization. Blindly following a method without considering the unique needs, challenges, and goals of the team contradicts the adaptive and context-sensitive nature of Disciplined Agile. Options B, C, and D (taking advice from "Choose Your WoW", starting with DAD, or working with an experienced coach) are all suitable ways to adopt DAD, as they involve guidance, adaptation, and learning.

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.