Analysis

Sure Step in action: a blurry Degree of Fit?

by Vjekoslav Babic on August 27, 2010

image 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?

[click to continue reading…]

{ 1 comment }

4 strategies for a favorable Degree of Fit

by Vjekoslav Babic on August 25, 2010

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.

[click to continue reading…]

{ 1 comment }

What does a Dynamics consultant do: Part two

by Vjekoslav Babic on December 4, 2008

image Yesterday, in my What does a Microsoft Dynamics consultant do? post I started explaining the job of an application consultant. As promised, today I’ll explain what duties an application consultant has in each of Sure Step phases.

[click to continue reading…]

{ 0 comments }

What’s New In Sure Step: Functional Requirements Document

by Vjekoslav Babic on October 30, 2008

One of many improvements the latest version of Microsoft Dynamics Sure Step methodology has brought along is the revised purpose of the Functional Requirements Document (FRD). This document has long served as cornerstone of every Analysis process of every implementation project: it was the main deliverable of the Analysis phase and it both documented customer’s requirements and explained how they will be met with Microsoft Dynamics NAV solution.

[click to continue reading…]

{ 1 comment }

Featuritis Cure

by Vjekoslav Babic on October 24, 2008

Don’t you just love when users come up with new feature ideas at a microprocessor clock rate. Even before you finish developing one, five new requests pop up. This is a disease, and it’s called featuritis!

[click to continue reading…]

{ 1 comment }

Diagnostic Phase – a signpost for implementation

September 19, 2008

Each phase of Microsoft Dynamics Sure Step methodology is equally important in an implementation project. You could argue that analysis is the most important, or that design is the most important, or that operation is less important. I’ll paraphrase Scott Adams here and ask: how one phase can be more important if each of them [...]

[click to continue reading…]

A case for Sure Step: how Sure Step brings project success

September 11, 2008

Methodology is a tough topic. There are good methodologies, there are bad methodologies, there are good methodologies gone bad. Methodology is not a silver bullet, it won’t just make any problems disappear, and is hardly ever the single source of success or failure. But a methodology can be a major contributor to success. I could [...]

[click to continue reading…]

Standard enemy

May 15, 2008

The biggest jeopardies often lurk where we least expect them. When implementing an ERP system such as Microsoft Dynamics NAV, what should be one of our best allies, turns out to be our mortal enemy. It has a simple name: The Standard. Standard processes, standard functionality, standard documents, standard system. All these gizmos can turn [...]

[click to continue reading…]