Skip to main content

MVP is Not Just for Startups



One of the key goals for startups is to release their products quickly, which has lead to a minimum viable product (MVP) approach.  Speed to market is so important that it's better to release a product before all the desired features are present so you can capture market share and use customer feedback to help you prioritize the introduction of new features.

The challenge of the MVP approach is to determine what "viable" means.  If you launch without sufficient features, your product may fail to attract any customers, or disappoint your first customers. But if you wait, competitors are likely to step in with their own offerings.

The MVP concept is not only applicable to startups and commercial companies that are selling products, but also to internal software projects for companies, government agencies, and non-profits.  Too often I have seen scope creep add to the feature list of a software product and delay launch dates for weeks or months.

Using MVP principles, your project team can stay on schedule to ship a product by postponing features to after launch as long as they are not critical.  This approach is consistent with Agile software development methodology which calls for a backlog of features and tasks, and a grooming process that refines the backlog for each iteration (sprint) that is conducted.

Shipping a product quickly has many benefits.  It starts the user feedback process in a more powerful way than during development or testing.  It conserves the energy of executive sponsors, and allows you to create wins that boost confidence in the development team.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do