MVP FTW

“Another MVP project.. YAY!”

How often do you get push back from internal stakeholders because they hear it will be a MVP solution?

For those wondering what a MVP is?  It does not mean Most Valuable Product.

MVP == Minimum Viable Product.

So why do some projects work on delivering an MVP solution?
Could be many reasons, some include;
-         Time and resource constraints
-         Need to make market announcement deadlines
-         Product or system being replaced is due for expiry/renewal

As the name implies a minimum viable product delivers a somewhat basic solution that on its own is enough for teams to be able to perform their day-to-day work duties.

As a result post-go-live teams may move forward using temporary workarounds.
Examples include;
-         swivel chairing between systems/applications
-         manual data entry
-         manual reporting

So why the pushback?

In my experience, the main reason is because the initial project sell or communication, promises a more ideal end-state delivery of X system or Y process.  As projects continue, with introduced risks, issues, blockers, resourcing etc, a compromise is made – an agreement to deliver a MVP.
-  Now, please note that sometimes an MVP is always stated from the outset.

Some teams who have received MVP go-live projects from their past experience sometimes know that post-go-live, the same effort, to continue developing features and enhancements falls by the way side.

Why?

Because the project team has moved onto other priorities or projects and maybe the BAU/operations team looking after said enhancements is not yet setup to handle the work promised.

So what role should BAs play here?

BAs are often front and centre for relaying information between the project teams and our stakeholders. As soon as we know that a MVP is being delivered, the point needs to be repeated often, and expected outcomes clearly relayed and understood.

A good way to set the right expectation is during continuing workshops, test sessions, demos, brown bags, and end-user training sessions.

The better the communication, the better the solution is received on go-live.

There is nothing wrong with a MVP.
In fact it’s a great way to build and deliver solutions, but if the end customer or internal stakeholder is expecting something ‘more’, and they were not completely privy to what they will get, then do not expect to be praised or even forgiven for a self-inflicted tarnished reputation.

Have a great day.

#communications#businessanalysis#experience#team