InfoQ Homepage MVP Content on InfoQ
Articles
RSS Feed-
Architectural Trade-Offs: the Art of Minimizing Unhappiness
To architect is to be a frustrated perfectionist; a good architecture minimizes this unhappiness by making trade-offs that can be lived with. The main skill in architecting is making trade-offs. These trade-offs reflect the most important and difficult decisions a team will make about its architecture.
-
How Much Architecture Is “Enough?”: Balancing the MVP and MVA Helps You Make Better Decisions
The Minimum Viable Architecture (MVA) is the architectural complement to a Minimum Viable Product (MVP). The MVA and MVP must evolve together for a product to be successful. As new features are delivered to customers, corresponding incremental improvements need to be made in the architecture. Also, the architecture should not get too far ahead of what is needed for the product.
-
Enhancing Your "Definition of Done" Can Improve Your Minimum Viable Architecture
A Definition of Done describes the criteria that determines whether a software product is releasable. 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.
-
IDEA: a Framework for Nurturing a Culture of Continuous Experimentation
For a team to be agile, they need a culture that allows them to learn, unlearn, and relearn. This article explains how teams can foster such a culture, navigate through the complexities of modern development environments and harness agility to deliver software quickly that fits the needs of users and business sponsors. It describes a framework to explore, plan, implement and evaluate ideas.
-
Agility and Architecture: Balancing Minimum Viable Product and Minimum Viable Architecture
Software architecture and agility are often portrayed as incompatible. In reality, they are mutually reinforcing - a sound architecture helps teams build better solutions in a series of short intervals, and gradually evolving a system’s architecture helps by validating and improving it over time.
-
Rules of Thumb & Traps When Approaching Tech Stack Decisions
At the MVP stage - do only the stuff you would do in a hackathon. Scalability and processes will become important once we have predictable revenue streams. Where are you generating your unique value proposition? Outsource all aspects of the tech solution which are not in a relationship with your competitive advantage. Follow a general tech directive but balance it with the team's autonomy.
-
How to Introduce Innovation into the DNA of 21st Century Companies
An innovation mindset is about the tiny little improvements any employee can do; hundreds of simple, low-cost- no-effort activities are in plain sight just waiting for somebody to deploy them. This article provides guidelines that can support you in changing the attitude of employees in your organization providing trust, time, space, teams, a second operating system, MVPs, and co-creation.
-
Building a Scale-Ready MVP
In these times of turmoil, information technology is a strategic asset to weather the difficult times ahead. Companies launch projects to build digital products and seize new opportunities, but even with strong pressure to release as fast as possible, beware of the pitfalls of an unsustainable MVP. Building an MVP that is scale-ready takes careful consideration and disciplined practices.
-
Q&A on the Book The Pragmatist's Guide to Corporate Lean Strategy
The book The Pragmatist's Guide to Corporate Lean Strategy explores how to practically adopt lean enterprise and lean startup concepts to turn your company into a lean agile enterprise promoting business agility. It provides examples from companies that have applied these concepts, describes the strategy, best practices, anti-patterns, and gives insights into lean and agile transformations.
-
Using Structured Conversations to Discover Your MVP
In an increasingly more complex world, finding the smallest possible chunk to deliver to get feedback is essential. This is the idea behind the term MVP. This article describes a model where business and technology together explore the product needs along seven product dimensions, which is a great way of finding small slices of work to develop.