In our previous Episode, we show how critical is to #ThinkBig but #BuildSmall in the #QuoteToCash #Transformation, why Requirements should be prioritized, the importance to start with a High-Level Design and the rational of an initial configuration based on few Products, few Customer Agreements and only one Country; as an introduction into this #Episode8, dedicated to show why a #MinimumViableProduct (#MVP) will impact on a success and low-cost implementation.

2nd Attention focus:

§ Is a #MVP the same as a #ProofOfConcept (#PoC) or a #Prototype?

§ Why does an #MVP sometimes take too much time and could be so expensive?

§ Should you test your #DataQuality and #MigrationStrategy on the #MVP?

§ Should you Go-Live with your #MVP or just do a Non-Productive Go-Live?

§ Should you run a #MVP from Scratch or based on a Preconfigured instance of the targeted #QuoteToCash solution?

Thoughts to brainstorm:

§ A #MVP is similar to a #PoC, however a #PoC usually is run by the solution vendor or a System Integrator (SI), based on: some or limited requirements collected by their Presales Team, not always based on real customer data, and only in few cases, based in a High-Level Design. The key objective of a #PoC is to help the customer to decide if the solution could work but not help to see holistically and in real how the business will run on the solution, like happen in a #MVP.

§ A #Prototype could be like a #MVP, however the key difference is that normally is not based on a High-Level Design. Evangelists of Prototyping normally promote to “not lose time” on a design, and just start configuring requirements.

§ Major issues of a #PoC or a #Prototype are that working without a “minimum viable end-to-end scope” and High-Level Design as a Roadmap, Scope and Time usually have deviations, and for that, normally are more expensive than a #MVP.

§ Because in a #MVP your are configuring end-to-end a piece of the business (few Products, few Customers and 1 country), it’s 100% possible to test the Model with Real Data, what will show, by the way, if their quality could be a “headache” at the moment of the implementation.

§ Should you Go-Live or Not with your #MVP? Our recommendation is that, after a successful Non-Productive test with real data, you should Go-Live. About convivence with your Legacy systems and Model of Operation…we will talk in another Episode.

§ And to close the loop, a #MVP run on a Preconfigured instance of the targeted solution, will avoid deviations that normally happen starting from Scratch.

In summary, a #MVP helps companies Transforming their #QuoteToCash to see:

§ End-to-End how a key piece of their #Business will flow on the new #EnterpriseArchitecture.

§ Because is based on a High-Level Architecture and Real Data, enforces a clear focus and, prevents deviations and surprises at the moment of the Go-Live.

§ When the #MVP is based on #GMBs #BISTRO, an #SAPBRIM Preconfigured instance, of most powerful #QuoteToCash solution, you will #MitigateRisks of deviations, wrong decisions and big bang implementations, during your #Transformation journey.

Learn more about #GMB, one of the most recognized “curators” of #SAPBRIM solution, that also holds one of the longest track records of working on #critical and #escalated projects, that no one else has been able to tackle, at: https://www.gmbtechnology.com/