Sometimes the Degree of Fit might seem like comparing apples and oranges. With 90 extremely detailed fits, and 10 high-level gaps, the degree of fit seems high, but it isn’t. 90 extremely detailed gaps, and 10 high-level fits, make the degree of fit seem low. In either case the degree of fit is unreliable and it doesn’t tell you anything at all.
For a degree of fit to be reliable, all the requirements should be specified roughly on the same level of detailedness. If they aren’t, you might have an extremely risky project before you, and you just don’t see it. Or you might have a slam dunk, and you stand scared to death by the non-existent risks you see all over.
In situations such as these you have to level the requirements to get a more meaningful figure, otherwise your Fit Gap Analysis doesn’t serve its purpose.
But how exactly do you tell apples from oranges in a requirements list?
Continue reading Sure Step in action: a blurry Degree of Fit?
If your Degree of Fit is just not there, or the balance between it and the budgetary estimate is not favorable, the risk that project will exceed the budget or not meet the requirements is high, but you might still decide to go on. In fact, most consultants often do, choosing to fight the odds. According to field reports, this approach often fails.
There are four things you can do to ensure the customer satisfaction while keeping the project in budget and still reducing the risks by increasing the degree of fit.
Let’s see what they are.
Continue reading 4 strategies for a favorable Degree of Fit
The Sure Step season seems to have started in its fullest for me – it is the second time this year already that I’m delivering the Sure Step course, this time in Copenhagen, Denmark, and I must say that I truly enjoy it.
Anyway, while discussing the Fit Gap and Solution Blueprint decision accelerator, an important component of the Diagnostic phase, a student asked me an interesting question: why do we need to give effort estimates to meet the requirements at this stage?
And indeed – isn’t it far too early to give or commit to any effort estimates at this early stage, isn’t there a huge risk that the customer might understand these estimates as final project estimates? What’s the true meaning of effort estimates during Fit Gap analysis in diagnostic phase?
Continue reading Fit Gap and Solution Blueprint Estimates
“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” That’s the very first principle of the Agile Manifesto.
The problem with ERP is that the first deliveries are all but early: they typically occur only after about twenty months.
Twenty months is a heck of a long time. And value achieved after a twenty-month implementation is often far below expectations.
Continue reading 1st rule of agile ERP: deploy vanilla ERP
The degree of fit is an important indicator of your project’s alignment with the standard functionality.
After you determine the degree of fit, and understand what it means for the project, do you just passively accept the findings, or do you do something to make them more favorable?
Continue reading The value of Degree of Fit: understanding risks