Pass the PMI PMI Agile DASSM Questions and answers with CertsForce

The statement "The implementation of this blade will be standard across domains" isfalseabout the Business Operations process blade. In Disciplined Agile (DA), the Business Operations process blade involves strategies for providing services to the business and ensuring operational effectiveness, but its implementation will vary depending on the specific context, domain, and organizational needs. DA emphasizes tailoring practices to fit the unique circumstances of the organization, so a one-size-fits-all or standard implementation is not appropriate.

Options A (collaboration with Sales and Marketing), B (providing services to the business), and D (focusing on delighting customers) are true aspects of the Business Operations process blade.

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: 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 primary benefit of DevOps, within the context of Disciplined Agile, isreduced cost of deployments. DevOps is a set of practices that aims to shorten the systems development life cycle and provide continuous delivery with high software quality. In DA, DevOps practices facilitate seamless integration and continuous delivery of code changes, enabling more frequent and reliable releases to production.

By automating and streamlining deployment processes, DevOps reduces the manual effort, time, and errors associated with deployments, which, in turn, lowers the overall cost. This aligns with the Disciplined Agile principle of "optimize flow across the entire value stream," which emphasizes efficient and cost-effective delivery of value.

Additionally, reducing the cost of deployments leads to other secondary benefits such as improved quality (due to more frequent testing and feedback loops) and greater agility (by enabling quicker response to changing market or customer needs). Therefore, while other options may seem beneficial, the most direct and primary benefit associated with DevOps is indeed the reduced cost of deployments.

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 Disciplined Agile (DA), the "Specialist" is considered a supporting role. Specialists possess expertise in specific areas (e.g., security, database management) and are brought in as needed to support the primary delivery team. The supporting roles are not part of the core team but contribute specialized skills and knowledge when required.

Options A (Stakeholder), B (Team Lead), and D (Architecture Owner) are not supporting roles. Stakeholders represent end-users or business interests, while Team Leads and Architecture Owners are considered primary roles within a DA team.

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

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.

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.

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.

According to the I.N.V.E.S.T. mnemonic, a good user story should be:

Independent:Can be developed and delivered without dependencies on other stories.

Negotiable:Flexible in details and open to discussion.

Valuable:Must deliver value to the customer or end-user.

Estimable:Can be estimated to gauge effort required.

Small:Sized appropriately to be completed within an iteration.

Testable:Should have clear criteria to determine whether the story is complete.

"Valuable" is a key characteristic that ensures the user story contributes to the product's value. Options A (Incremental), C (Tangible), and D (Satisfactory) are not part of the I.N.V.E.S.T. mnemonic.

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.