DASSM Exam Dumps - Disciplined Agile Senior Scrum Master (DASSM) Exam

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.

Governance in a Disciplined Agile (DA) project involves ensuring that the organization's standards, practices, and compliance requirements are being met while allowing teams to operate within a defined framework. It includes activities such as creating forums for sharing knowledge (A), making decisions about funding (B), administering rewards and recognition (C), ensuring compliance with a regulatory standard (E), and having a defined process for decision-making (F).

However, governance does not mean giving the team complete freedom to make decisions (D). In DA, while teams are encouraged to be self-organizing and empowered, they must still operate within the constraints of organizational governance policies and practices. Governance ensures there is a balance between team autonomy and alignment with organizational goals and standards. Therefore, "complete freedom to the team to make decisions" is not aligned with the DA approach to governance.

This aligns with the principles found in the PMI Disciplined Agile framework, which emphasizes both flexibility and control. In DA, governance is about guiding and monitoring the team’s activities to align with the organizational context, rather than granting unrestricted autonomy.

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

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.

Disciplined Agile projects do not aim to maximize work-in-progress (WIP). Instead, they aim to minimize WIP to increase efficiency and reduce waste. By limiting WIP, teams can focus on completing tasks faster and delivering value more frequently. This approach is aligned with lean principles, which discourage multitasking and encourage teams to complete work items before starting new ones. Therefore, the statement that disciplined agile projects try to maximize WIP is false. The goal is to optimize the flow of work, not overload the team with too many concurrent tasks.

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.

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 is false to say that Disciplined Agile (DA) roles cover all possible roles in an organization. DA defines a set of primary roles (such as Team Lead, Product Owner, and Architecture Owner) and supporting roles for agile delivery teams. However, it does not prescribe all roles that might exist in an organization, such as executive leadership or specialized departments outside the agile delivery context.