In Disciplined Agile, the team members are responsible for defining the amount of work to be completed during an iteration based on their understanding of the team's current capacity. This is aligned with Agile principles that promote self-organizing teams and emphasize the importance of team members making commitments based on their realistic assessment of what they can achieve. This collaborative decision-making process helps to ensure that the team is neither over-committing nor under-utilizing its capacity, leading to sustainable delivery and higher quality outcomes.

PMI Agile Practice Guide, which supports the principle of team autonomy in deciding how much work they can complete in an iteration.

PMI Disciplined Agile (DA) Toolkit, which promotes self-organization and team-based decision-making regarding workload capacity.

In Lean and Agile terminology, Push refers to work being given to people regardless of their current capacity. This approach contrasts with a 'pull' system, where work is pulled by the team when they have the capacity to handle it. 'Push' systems often lead to overloading team members, increased bottlenecks, and inefficiencies.

A . Delayed until later does not capture the concept of 'Push.'

C . Expedited to meet a deadline is about urgency, not pushing work.

D . Outsourced to a vendor refers to the delegation of work outside the team and is unrelated to the 'Push' concept.

Thus, the correct answer is B. Given to people.

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.

The Disciplined Agile (DA) principle of being pragmatic is characterized by the focus on 'being as effective as you can and continuously improving.' According to PMI's Disciplined Agile Toolkit, being pragmatic means applying an agile mindset that is not constrained by a rigid set of rules or practices. Instead, it emphasizes being practical and outcome-focused, aiming for the best results in each unique context while continually seeking opportunities for improvement.

Disciplined Agile promotes pragmatic decision-making by suggesting that teams should balance their approach by being both goal-driven and situation-aware. This means that instead of strictly adhering to a single agile framework or methodology, teams should assess their situation, leverage their experience, and apply the most suitable tools and techniques available. Furthermore, continuous improvement (Kaizen) is a fundamental aspect, meaning teams should regularly reflect on their practices and make iterative enhancements to achieve effectiveness.

This principle also aligns with DA's guidance to 'Optimize Flow' and 'Be Awesome,' as it encourages teams to deliver value while recognizing that every situation might require different tools, techniques, and practices. Thus, 'D. Being as effective as you can and continuously improving' best captures the essence of DA's pragmatic approach.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which details the core principles of Disciplined Agile, including being pragmatic by focusing on effectiveness and continuous improvement.

PMI Disciplined Agile (DA) Toolkit, which explains how being pragmatic involves choosing the best approach for your specific context rather than adhering to a strict methodology.

Disciplined Agile (DA) provides a solid foundation for business agility through multiple mechanisms, including:

B . Defining a framework for agility at scale: DA offers a comprehensive toolkit that supports scaling agile practices across an organization, integrating principles from various agile methodologies to ensure coherence and alignment.

D . Providing guidance to streamline processes in a context-sensitive manner: DA emphasizes tailoring processes to the specific context of the organization, project, or team, rather than applying a one-size-fits-all approach. This flexibility allows organizations to adapt more effectively to change and improve their agility.

A . Enforcing adherence to organizational standards contradicts the DA principle of pragmatism and flexibility.

C . Creating awesome teams that foster joy is beneficial but is not specifically cited as foundational for business agility.

E . Describing trade-offs is part of DA's decision-making framework but not directly a way of providing a foundation for business agility.

Thus, the correct answers are B. Defines a framework for agility at scale and D. Provides guidance to streamline processes in a context-sensitive manner.