If projects were completely predictable, there would be no need for risk management. Everything could be planned and executed according to plan. However, we know better. Unexpected things happen, disrupt the original plans and cause time and cost overruns. In IT projects, these overruns are far too common to be ignored.
{ 1 comment }
Implementation is like marriage. For better or worse, you choose a piece of software, take it under your roof and commit to it for a long term, so help you God.
And as in marriage, if you want to live happily ever after with your new software, the my way or the highway attitude doesn’t help much—you must be open to compromise.
Last Monday, I argued for avoiding customizations if at all possible, an argument I stand by firmly. It’s like forcing your wife to color her hair pink. I don’t know about your wife, but mine doesn’t color her hair pink. If you like it pink, it’s probably something to think about before turning your yes in.
But NAV is NAV, isn’t it? It has what it has, and if I need it different, I have to customize it, right?
Wrong. You can compromise.
{ 21 comments }
Last 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.
{ 4 comments }
