PMI Updated DASSM Exam Questions and Answers by jac

TheProduct Backlogis the artifact that collects all the work flowing to the team in Agile practices, including Disciplined Agile (DA). It is an ordered list of everything that might be needed in the product, serving as the single source of work undertaken by the team. This backlog includes user stories, features, enhancements, bug fixes, and technical tasks. It is prioritized by the Product Owner to ensure that the team works on the most valuable items first.

Options B (Business backlog) is not a standard Agile artifact. Option C (Iteration backlog) is a subset of the Product Backlog, containing items chosen for the current iteration. Option D (Release roadmap) is a higher-level plan for future releases, not a collection of all work items.

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.

According to Disciplined Agile and broader agile principles, complex adaptive systems, such as software development environments, cannot be fully understood by analyzing individual parts in isolation. The nature of complex adaptive systems is that they involve multiple interacting components, and their behaviors emerge from these interactions. Therefore, understanding the whole system requires examining the relationships, feedback loops, and patterns that arise within the entire context, not just the individual parts. This concept is grounded in systems thinking, a key component in agile methodologies, which encourages viewing the system holistically.

"Organization distribution" is not a tactical scaling factor for a team in the context of Disciplined Agile (DA). Tactical scaling factors focus on specific elements that impact the immediate team context, such as Team Size (A), Geographic Distribution (B), and Team Maturity (C). "Organization distribution" refers more broadly to the structure or distribution of the organization as a whole, rather than directly impacting the team's day-to-day operations or scaling concerns.

Top of Form

Bottom of Form

False: Fulfilling the requirements does not necessarily mean that the customer is delighted. In Disciplined Agile and other Agile frameworks, delighting customers goes beyond merely meeting the stated requirements. It involves exceeding customer expectations, delivering unexpected value, and providing a positive user experience. A product or service may fulfill the technical or functional requirements but fail to delight if it does not provide an exceptional user experience, is not easy to use, or does not address the underlying needs or desires of the customer comprehensively. The goal is to deliver true value, which often means going beyond the baseline requirements.