Delivering early value with MVA
Early validation, feedback, and learning cycles are critical practices in agile software delivery. Developing an MVP helps enterprises test new innovations in production and receive customer feedback early enough to reduce risk before committing to large investments.
Architects play a critical role in defining the technical scope of MVP as well as designing the Minimum Viable Architecture (MVA). As a rule of thumb, high business value features are delivered first to ensure the business gets maximum value upfront. When designing the MVP scope, features are carefully chosen based on a combination of risk and value, as shown in the following diagram:
Figure 6.14 – Risk- and value-based prioritization for MVP
The preceding diagram is adapted from Ken W. Collier's view on the prioritization approach for business features. However, this approach is not particularly viable for architecture unless the business solution...
