The Retrospective is an important agile ceremony because it provides a dedicated time for the team to reflect on their performance and processes, discuss what went well, what didn’t, and how they can improve moving forward. This continuous improvement mindset is central to agile methodologies, including Disciplined Agile (DA). It helps build a culture of transparency, trust, and learning. Option B is incorrect because the Product Owner is not the focus of the Retrospective. Options C and D do not describe the purpose of a Retrospective in agile practices.

The main role of the team lead (which can be referred to as a Scrum Master, Team Coach, or Team Lead in Disciplined Agile) is to ensure that the team is building the product in the right way. This involves facilitating the team's process, removing impediments, and coaching them to adopt and optimize Agile practices, ensuring quality and efficiency in delivery. The team lead does not dictate what product to build (which is the role of the Product Owner), nor is their primary role to build the product themselves or coordinate building efforts in a command-and-control manner. Instead, they focus on enabling and empowering the team to deliver high-quality work in alignment with Agile principles.

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.

Among the primary roles on Disciplined Agile (DA) teams, the Team Lead (also referred to as a Scrum Master or Agile Coach in other frameworks) needs to be a process expert . The Team Lead is responsible for guiding the team in following Agile practices, helping them optimize their way of working (WoW), removing impediments, and facilitating continuous improvement. They ensure that the team adheres to the chosen practices and adapts them as necessary to fit their context.

Options A (Team member), B (Architecture owner), and C (Product owner) are important roles but are not primarily focused on being process experts.

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.

Agile teams, as per the Disciplined Agile (DA) framework, can deliver non-software projects. The DA toolkit is designed to be adaptable and applies agile and lean principles to a wide range of business domains beyond software development. This flexibility allows agile teams to use iterative and incremental approaches to manage various types of projects, such as marketing campaigns, event planning, and other organizational initiatives. Thus, it aligns with the PMI's stance that agility can benefit all types of projects, not just software-focused ones.

In Disciplined Agile, shared services teams are not always based on specialization. While shared services teams often consist of specialists (e.g., security experts, database administrators), they can also be cross-functional teams that provide support across different disciplines. The key is that these teams provide services to multiple delivery teams, regardless of whether they are composed entirely of specialists.

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.

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.

In the context of the Disciplined Agile (DA) framework, if a team is about to begin work on a project where releases are expected only every six months or so, and the team does not have an agile mindset or desire to release often, the "Traditional" lifecycle is most appropriate. The Traditional lifecycle, also known as a predictive or waterfall lifecycle, is suitable for teams or projects that require extensive planning and where changes are infrequent or less welcome. This approach matches well with a mindset that is not inclined towards frequent releases or iterative development, allowing for longer, planned intervals between releases, which aligns with the six-month release cadence described in the scenario.

An advantage of a project team as opposed to long-standing product teams is a greater focus on delivery and short-term goals . Project teams are typically formed to achieve specific, time-bound objectives, and their primary focus is on delivering the project outcomes within the set timeframe. This can lead to an intense focus on immediate deliverables and short-term results.

Options A (motivation to learn and evolve the WoW) and D (bringing work to the team) are more applicable to long-standing teams, while Option C (long-term focus) is not typically an advantage of project-based teams.

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.

In Disciplined Agile, the role of a DevOps Engineer is not necessarily filled by an operations person assigned to an Agile or Lean team. The DevOps role can be filled by individuals from either the development or operations side, or even someone with cross-functional expertise. The focus of the DevOps role is to foster collaboration between development and operations to enable continuous integration, delivery, and deployment. It is not limited to being an "operations person," but rather emphasizes the integration and collaboration needed to improve the flow from development to operations.

Transparency is a core practice in Disciplined Agile to ensure that all stakeholders, including team members and customers, have a clear understanding of the project's progress and any challenges faced. The reasons for practicing transparency include ensuring everyone knows what is happening (A), improving team morale (B), and meeting customer expectations (D). Delaying bad news to customers contradicts the principle of transparency. Hence, "C. It delays breaking bad news to customers" is not a reason that Disciplined Agile teams practice transparency.