Free Access PMI DASSM New Release

In the "Team Estimation" technique, you know you are finished estimating user stories whenthere are no more user stories left to estimate, and no team member wishes to move a card. This method relies on a collaborative, consensus-based approach where team members discuss and move cards (representing user stories) until everyone agrees on their relative sizes or effort. Onceall user stories are estimated and no further adjustments are proposed, the estimation process is considered complete. Time spent or product owner involvement is secondary to achieving team consensus on the estimates.

A team should consider entering the transition phase when the product meets all stakeholder expectations. In Disciplined Agile, the transition phase involves finalizing the product or solution for release. This phase is initiated when the product is deemed ready and all necessary criteria, including stakeholder expectations, have been fulfilled. Options A (new MBI developed), C (operational teams ready), and D (MVP ready) may be relevant in other contexts but do not specifically trigger the transition phase.

A value stream map is a lean tool that visually maps out the steps in a process from start to finish to identify areas of waste, delays, or inefficiencies in delivering value to the customer. In Disciplined Agile (DA), value stream mapping helps the team identify problem areas where waste occurs, such as bottlenecks, excessive handoffs, or unnecessary steps that do not add value to the customer. By recognizing these problem areas, the team can focus on improving or eliminating them to optimize the value delivery process. Options A, C, and D provide specific strategies for improving processes but do not encompass the broad benefit of identifying problem areas in realizing value.

In the Disciplined Agile (DA) framework, the role of "Team Member" is primarily responsible for building the product right. Team members, who possess the necessary skills and expertise, work collaboratively to develop, test, and deliver the solution according to the agreed-upon requirements and standards. While the Team Lead (B) facilitates the process and the Product Owner (C) ensures the right product is being built by prioritizing features and managing the backlog, it is the Team Members who actually perform the development work. The Architecture Owner (D) ensures the architectural integrity of the solution but is not solely responsible for building the product itself.

Top of Form

Bottom of Form