PMI Updated DASSM Exam Questions and Answers by laiba

In Disciplined Agile, "Team Estimation" is a collaborative process where the team members estimate the effort or size of user stories. The process typically involves first determining the relative size or complexity of each story by comparing them against one another. After this comparative sizing, numerical values (such as story points) are assigned based on the team's estimation scale. This method promotes group discussion, consensus, and a shared understanding of the work involved in each story, enhancing estimation accuracy and team alignment.

Options B, C, and D do not accurately describe the "Team Estimation" process as practiced in Disciplined Agile. Team Estimation focuses on assessing the relative size of work items rather than prioritization (Option B), defining criteria (Option C), or role assignment (Option D).

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.

Business Agility is the ability of an organization to adapt quickly and effectively to market and environmental changes, responding with innovative solutions and maintaining competitiveness. This concept involves a broader strategic capability beyond just implementing agile processes; it requires an organization-wide mindset of flexibility, responsiveness, and continuous improvement. Options A, B, and D reflect narrower or less comprehensive aspects that do not fully encompass the broader concept of Business Agility.

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.

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.