How to prevent failure: project education

  • Post comments:6 Comments
  • Reading time:4 mins read

According to Standish Group, top causes of failed IT project are these:

  • lack of end-user engagement,
  • unclear specification,
  • changes in scope,
  • lack of management support,
  • lack of planning,
  • unrealistic and unclear goals.

I haven’t seen too many failed Microsoft Dynamics NAV implementation projects, but those that I did see fail, have failed precisely for a selection of these reasons.

Take a closer look at the list above. Doesn’t it seem that the blame lays mostly on the customer? But is it really customer’s fault?

(more…)

Continue ReadingHow to prevent failure: project education

Do you trust your vendor: 9 good reasons to reveal your project budget up front

  • Post comments:4 Comments
  • Reading time:6 mins read

imageLast week I participated in a discussion about budgets and whether you should ask your potential customers their budget. It made me think: how often do customers reveal their project budgets before the consultants bid?

From my personal experience—not too often. What a waste! Of time, money, and opportunity.

(more…)

Continue ReadingDo you trust your vendor: 9 good reasons to reveal your project budget up front

Look me in the eye!

  • Post comments:2 Comments
  • Reading time:2 mins read

(A short rant about eye-contact-based specifications.)

image In short, there is no such things as an eye-contact-based specification. And for a reason.

While kicking-off of a project, we had a discussion with the customer about the change management approach, and specification detail. (more…)

Continue ReadingLook me in the eye!