Free Practice Questions for PMI DASSM Exam

TheProduct backlogis the artifact that collects all the work flowing to the team. It contains a prioritized list of user stories, tasks, enhancements, bug fixes, and other work items that represent the overall scope of the product development effort. The Product Owner manages the backlog, ensuring it is continuously refined and updated to reflect changing priorities and requirements. The iteration backlog (option B) is a subset of the product backlog items that the team commits to delivering in a single iteration, while the business backlog and release roadmap are not typically used to collect all work items for a team.

In the Disciplined Agile framework, the principle of "Context Counts" emphasizes the importance of tailoring practices to fit the specific situation or context of the team. In this scenario,the team decided to skip the daily standup meetings because they were co-located, and the meetings were not adding value. This is an example of making a context-specific decision based on the team's unique circumstances, which aligns with the DA principle of "Context Counts." Options A (Being awesome), B (Enterprise awareness), and D (Choice is good) do not accurately capture the rationale behind the decision to modify the practice based on context.

In Disciplined Agile, the "Construction" phase is where a consumable solution is developed incrementally and collaboratively. This phase is focused on creating working software or products in small, manageable increments, incorporating feedback, and ensuring that the solution evolves to meet customer needs. The Construction phase emphasizes collaboration, incremental development, and continuous integration to build a high-quality product iteratively.

Options A (Execution) and D (Transition) do not accurately describe the phase focused on collaborative and incremental solution development. Option B (Inception) refers to the initial phase where the scope, vision, and feasibility of the project are established.

References:

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

PMI’s Disciplined Agile Senior Scrum Master (DASSM) materials.

DevOps in the Disciplined Agile framework refers to a set of practices and tools aimed at creating a seamless integration of development and operations to enable continuous delivery and integration. Option (B), "Creating a smooth flow of work from development to operations," correctly captures the essence of DevOps. This practice involves automating workflows, improving collaboration between development and operations teams, and ensuring that software changes can be deployed to production reliably and frequently.

Options A, C, and D do not fully encompass the concept of DevOps in the Disciplined Agile context. While automating testing (A) and involving operational teams in development (C) are parts of DevOps, they are not the complete definition. Using development team members to solve operational problems (D) is not the primary focus of DevOps; instead, the aim is to create a collaborative environment where both development and operations teams work together effectively.

Thus, the correct answer is (B) as it represents the overarching goal of DevOps in a DA context, which is to facilitate a smooth, efficient flow from development to operations, enabling rapid and reliable software delivery.

A long-lived (stable) team is one that remains intact over multiple projects or iterations, allowing team members to develop strong relationships, trust, and a deep understanding of each other's skills and working styles. This stability leads to two key benefits:

Highly Collaborative:Stable teams develop effective communication and collaboration patterns, which enhance their ability to work together efficiently. They understand each other's strengths and weaknesses and can leverage this knowledge to optimize teamwork and problem-solving.

Trustworthy:Long-lived teams build trust over time, which is essential for open communication, risk-taking, and innovation. Trust enables team members to feel safe sharing their ideas and concerns, which leads to higher engagement, morale, and productivity.

Options A (Projectized) and B (Specifically resourced) are incorrect as they do not directly represent the benefits of having a stable team. Option E (Ability to multi-task) is less relevant, as Agile promotes focused work rather than multi-tasking.

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.

Disciplined Agile (DA) milestones are based on Lean governance principles. Lean governance emphasizes lightweight control mechanisms and focuses on achieving desired outcomes rather than enforcing compliance through heavy documentation or bureaucratic processes. DA milestones are established to ensure that value is being delivered efficiently and effectively throughout the lifecycle, with decisions made based on evidence and validated learning rather than detailed documentation (A) or strict adherence to lifecycle stages (D). While continuous integration (C) can support Lean governance by providing frequent, actionable insights into product development, it is not the foundation upon which DA milestones are based.

The three categories of process blades in Disciplined Agile (DA) are:

Disciplined DevOps:Focuses on integrating development and operations to streamline workflows, reduce bottlenecks, and ensure continuous delivery and deployment.

Disciplined Agile IT:Encompasses practices that support IT functions, such as Enterprise Architecture, Data Management, IT Governance, and IT Operations.

Disciplined Project Management Office (PMO):Provides strategic alignment, governance, and guidance to ensure that projects and initiatives align with organizational goals and deliver value.

Disciplined Agile Delivery (C) is a process blade itself, not a category, and Disciplined Kanban (D) is not a recognized process blade in DA.

The principle "Be awesome" in Disciplined Agile emphasizes creating an environment where people are motivated, work well together, and support each other in achieving common goals. When a team lead works hard to foster collaboration and unity within the team, they are applying the "Be awesome" principle by creating a positive, effective, and high-performing team dynamic. Options B (Choice is good), C (Context counts), D (Optimize around products/services), and E (Delight customers) do not specifically relate to the emphasis on fostering teamwork and an awesome team environment.

Top of Form

Bottom of Form

The principle ofpragmatismin Disciplined Agile does not mean that the team will always do what the customer wants. Instead, it means that the team will make practical decisions based on the specific context, constraints, and overall business goals. The team may sometimes need to challenge or refine customer requirements to ensure that the solutions provided are feasible, valuable, and sustainable.

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.

The responsibility for choosing the team's lifecycle in Disciplined Agile (DA)depends on the context. DA promotes a context-driven approach where decisions are made based on the specific needs, objectives, and constraints of the team and the organization. In some cases, the team itself may choose the lifecycle that best fits its way of working. In other scenarios, the decision could be influenced by an Agile coach, team manager, or organizational guidelines. Therefore, it is not a one-size-fits-all answer, and the context determines who is best suited to make this decision.