AMinimum 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.

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.

In Disciplined Agile (DA), theTeam Memberrole is primarily responsible for building the product correctly.
Team Members are the individuals who directly create the product by writing code, testing, designing, and performing other tasks necessary to deliver a working solution. The Architecture Owner may guide architectural decisions, and the Team Lead may facilitate processes, but it is the Team Members who actively build the product and ensure it meets the required standards and specifications.

In Disciplined Agile, theConstructionphase of the project life cycle is responsible for developing a consumable solution in a collaborative and incremental manner. During this phase, the team iteratively builds the solution, working closely with stakeholders to ensure that the product or service being developed meets their needs and expectations. The Construction phase emphasizes agility, collaboration, and incremental development, where the solution evolves through repeated iterations, incorporating feedback and improvements at each step. This approach helps to minimize risks, adapt to changes, and deliver value more frequently.

In Disciplined Agile, theArchitecture Owneris responsible formitigating key technical risks. This role focuses on overseeing the architectural integrity of the solution being developed, ensuring that the team makes sound technical decisions that align with the desired architecture and quality attributes of the project. The Architecture Owner helps in identifying and addressing potential technical risks early in the project life cycle, collaborating with the team to adapt the architecture as necessary to mitigate these risks.
This individual works closely with the team to guide architectural considerations, ensures compliance with the chosen architectural strategies, and maintains the overall technical direction of the project. Although they are involved in other cross-functional activities, their primary responsibility is to foresee and address technical challenges that could jeopardize the success of the project.