Defining a Strategic MVP: Your Roadmap to Success

If you have been around software development for a while, you know that feature creep can kill any project dead in its tracks. Defining a Minimum Viable Product (MVP) can keep feature creep in check enough to launch a project that can then be iterated upon in future releases. Fewer, or simplified features won’t necessarily lead to a successful MVP. Cutting features without considering their strategic significance can lead to project failure.

We will discuss how to use a strategic lense to frame an MVP discussion that successfully identifies what should be included in an MVP and what should be moved to future releases.

Audience
Experience Level
Beginner
Schedule Info
Date / Time
Room
Balcony B
Session Track
Supporting Documents