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

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.

A Minimum Viable Product (MVP) and a Minimum Business Increment (MBI) serve different purposes in the Disciplined Agile framework. An MVP (Option C) represents the smallest version of a product that can be released to customers to provide feedback and validate assumptions, whereas an MBI (Option D) is a small, deployable unit of value that builds upon an existing product and is designed to deliver business value incrementally. Option D is correct because an MBI is generally built incrementally on top of an existing product to enhance or add new capabilities. The other options do not correctly describe the relationship or distinction between MVP and MBI in the DA framework.

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.