Remove minimum-viable-architecture
article thumbnail

Article: A Minimum Viable Product Needs a Minimum Viable Architecture

InfoQ Articles

Creating a Minimum Viable Architecture as part of an MVP helps teams to evaluate the technical viability and to provide a stable foundation for the product that can be adapted as the product evolves. By Kurt Bittner, Pierre Pureur.

119
119
article thumbnail

Article: Minimum Viable Architecture in Practice: Creating a Home Insurance Chatbot

InfoQ Articles

Even a simple application, like the one described in this article, needs a minimum viable product (MVP) and a minimum viable architecture (MVA). This is the second article in a series on MVA. By Kurt Bittner, Pierre Pureur.

135
135
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Article: How Much Architecture Is “Enough?”: Balancing the MVP and MVA Helps You Make Better Decisions

InfoQ Articles

The Minimum Viable Architecture (MVA) is the architectural complement to a Minimum Viable Product (MVP). As new features are delivered to customers, corresponding incremental improvements need to be made in the architecture. The MVA and MVP must evolve together for a product to be successful.

94
article thumbnail

Article: Enhancing Your "Definition of Done" Can Improve Your Minimum Viable Architecture

InfoQ Articles

While normally focused on functional aspects of quality, teams can strengthen the quality and sustainability of their products if they expand their DoD to include architectural considerations. A Definition of Done describes the criteria that determines whether a software product is releasable. By Pierre Pureur, Kurt Bittner

Agile 52
article thumbnail

Article: Chipping Away at the Monolith: Applying MVPs and MVAs to Legacy Applications

InfoQ Articles

Legacy applications actually benefit the most from concepts like a Minimum Viable Product (MVP) and its related Minimum Viable Architecture (MVA).

article thumbnail

Article: Location, Location, Location: MVA Considerations for Distributed Processing and Data

InfoQ Articles

Even when designing a Minimum Viable Architecture (MVA), developers must consider resource location, especially when mobile apps are part of a distributed system. Distributing the data and processing can introduce new challenges if location is not part of the decision making criteria. By Kurt Bittner, Pierre Pureur.

53
article thumbnail

Starting a New Project as a Business Analyst

Analysts Corner

Understand the information architecture. You may also create a user story map to identify the minimum viable product. Understand existing solutions, and identify pain points. Get more information about the business domain, the clients, the end users, and the competition. You might need to interview different stakeholders.