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

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Dynamics 365 for Government Contractors (GovCon) Frequently Asked Questions (FAQ)

One of InfoStrat's most popular solutions is Dynamics 365 for Government Contractors (GovCon).



Here are some answers to frequently asked question on this solution:
Can I add new fields to the solution?  -- Yes, the solution is fully customizable and you can add your own new fields to any form, view or report.Does Dynamics 365 for GovCon work on mobile devices?  -- Yes, Microsoft offers mobile apps for all the most popular platforms including iPhone, iPad, and Android phone and tablets.Does Dynamics 365 connect with bid data systems such as Deltek and Onvia?  -- Some information services, such as Onvia, offer integration with Dynamics 365.  Others require third party solutions such as the InfoStrat integration with Deltek GovWin IQ.What do customers typically customize for their unique requirements? -- Not all contractors follow the same steps in the capture process.  Most clients will tailor the business process to add or remove steps in order to match their sales methodology.  Of…

Understanding Dynamics 365 and Office 365 Admin Roles

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 AdministratorDynamics 365 System AdministratorDynamics 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 deployment.  The Global Administrator is the only …