PMI Updated DASSM Exam Questions and Answers by amar

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.

In the Disciplined Agile (DA) framework, the architecture of a product is typically proven during the Elaboration phase. This phase focuses on validating the architecture of the solution, mitigating technical risks, and establishing a firm foundation for the project's future iterations. During Elaboration, teams work on refining the architecture, ensuring that it can support future development and will meet the project's quality requirements. The construction phase builds upon this established architecture, and by the Inception phase, the initial vision and feasibility are already defined but not yet validated. Therefore, "A. Elaboration" is the correct answer as it is the phase where architecture is thoroughly proven and refined.

In Disciplined Agile (DA), iteration planning is typically conducted at the beginning of each iteration. The team pulls prioritized work items (user stories, features, etc.) from the product backlog that they can commit to completing in the upcoming iteration. This approach ensures that the team is always working on the most valuable tasks and is aligned with the principles of Agile, which emphasize iterative and incremental progress. The planning at the start of each iterationallows the team to refine the scope, estimate the effort required, and make necessary adjustments based on their capacity and previous iteration learnings.

Options B, C, and D are not correct in the context of DA practices. While iteration reviews and retrospectives contribute to continuous improvement, the formal planning of iterations is conducted at the beginning of each iteration.

References:

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

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

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.