A Minimum Viable Product (MVP) is a product with just enough features to satisfy early customers and?
Answer : A
A Minimum Viable Product (MVP) is a product with just enough features to satisfy early customers and provide feedback for future product development. The MVP approach allows organizations to test their product hypothesis with minimal effort and investment, gather valuable user feedback, and make informed decisions about further development. By delivering a basic version of the product quickly, teams can learn from real-world use, validate assumptions, and iterate on the product to better meet customer needs in subsequent versions.
PMI Disciplined Agile (DA) Toolkit, which discusses the concept of an MVP as a tool for early market entry, user feedback, and iterative development.
PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which outlines the role of an MVP in enabling rapid feedback loops and continuous improvement.
What goal diagrams should a team select first?
Answer : B
In Disciplined Agile, teams are encouraged to select goals that are most relevant to their context and life cycle. This approach ensures that the team focuses on achieving outcomes that align with their specific needs, challenges, and project phase. Goal diagrams in DA help teams visualize and prioritize their objectives, and by choosing goals most pertinent to their current context, teams can address the most critical aspects first and adjust their practices effectively.
PMI Disciplined Agile (DA) Toolkit, which discusses the use of goal diagrams and emphasizes the importance of selecting goals based on the team's context and project life cycle.
PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which provides guidance on goal-setting and prioritization in Disciplined Agile.
What docs a well-written user story describe?
Answer : C
A well-written user story in agile practices, including Disciplined Agile, describes the customer's perspective. User stories are short, simple descriptions of a feature or requirement from the point of view of the end user or customer. They are intended to capture the 'who, what, and why' of a requirement, focusing on the value it delivers to the customer. This perspective ensures that the development team understands the real-world needs and motivations behind the features they are building, allowing them to create solutions that truly meet user needs.
PMI Disciplined Agile (DA) Toolkit, which outlines the structure and purpose of user stories, highlighting the importance of describing features from the customer's perspective.
PMI Agile Practice Guide, which discusses the use of user stories to capture customer requirements and deliver value.
Why is the retrospective an important agile ceremony?
Answer : A
In Agile, and specifically within the Disciplined Agile framework, the retrospective is a crucial ceremony where the team reflects on their past iteration to identify areas of improvement. The main purpose is to foster continuous improvement by focusing on how the team can better work together moving forward. It encourages open communication, self-reflection, and team accountability, aligning with the agile principles of continuous learning and adaptation.
The other options are incorrect because:
B . Organizing the product backlog is typically done during backlog refinement sessions, not retrospectives.
C . Prohibiting stakeholders from making requests is not the purpose of a retrospective; stakeholder feedback is valuable and is usually gathered during review sessions.
D . Providing the product owner with insights into team dynamics may occur, but it is not the primary goal of the retrospective.
Therefore, the correct answer is A. It allows the team time to focus on how they can better work together moving forward, as it aligns with the continuous improvement objective central to Agile and Disciplined Agile practices.
Which method extends the Kaizen loop strategy to help teams identify techniques that are likely to work in their context?
Answer : B
The method that extends the Kaizen loop strategy to help teams identify techniques likely to work in their context is Guided continuous improvement. In the Disciplined Agile (DA) toolkit, guided continuous improvement refers to using a structured approach to learning and adaptation, where teams are provided with guidance and options based on proven practices. This helps teams apply Kaizen principles effectively in their unique environments by selecting and tailoring techniques that are most likely to yield positive results.
A . Explicit workflow policies refer to defining specific rules about how work is managed but do not inherently guide continuous improvement.
C . Communities of practice involve groups that share knowledge, but they do not extend the Kaizen loop strategy directly.
D . Cross-team learning helps in sharing knowledge between teams but is not the method extending the Kaizen loop strategy.
Thus, the correct answer is B. Guided continuous improvement as it directly aligns with the aim of adapting the Kaizen strategy to specific contexts.
Select two tactical scaling factors that must be considered when analyzing the team's context. (Choose two)
Answer : C, D
When analyzing a team's context for tactical scaling in Disciplined Agile, two key factors that must be considered are Domain Complexity and Team Size:
C . Domain Complexity: Refers to the complexity of the problem domain the team is working within. More complex domains require different approaches and potentially more sophisticated techniques to manage uncertainty, dependencies, and risks.
D . Team Size: The size of the team affects how the team communicates, collaborates, and organizes itself. Larger teams may require additional coordination, communication practices, and role definitions to be effective.
The other options are less relevant for tactical scaling:
A . Demographics, B. Best Practices, E. Budget, and F. Dynamics are not directly identified as key tactical scaling factors in the Disciplined Agile context.
Which of the following is a primary role on a Disciplined Agile Delivery team?
Answer : D
On a Disciplined Agile Delivery (DAD) team, the Architecture Owner is a primary role. The Architecture Owner is responsible for guiding the team in making sound architectural decisions and ensuring that the architecture evolves appropriately to support the team's work. This role involves collaborating with the team to address architectural concerns, mitigate technical risks, and ensure alignment with the overall technical vision. The Architecture Owner also helps the team navigate complex technical decisions and is a key player in maintaining the integrity of the system architecture.
PMI Disciplined Agile (DA) Toolkit, which describes the roles in a DA team and specifies the Architecture Owner as a primary role responsible for architectural concerns.
PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which outlines the roles and responsibilities of the Architecture Owner.