I woke up this morning and checked my to-do list for today. Business, business, business, and some more business. And yet it seems that my to-do list never goes blank, a couple of customers or projects are always in the backlog. I don’t know why exactly, but after opening the browser I typed the address of my blog—something I didn’t do for a long time—and I was stunned.
Almost three months since my last post. The oldest post on my blog’s home page is four months old and counting. I could remember times when a post couldn’t survive four days on my home page. My blog wasn’t dormant, it seemed downright dead.
“Software projects are no different from other projects”.
This statement is being repeated over and over at project management courses and seminars, even endorsed in books.
It’s true that software (and ERP implementation, as a subset of software) projects have many traits in common with projects in other disciplines. But ignoring their specifics is almost as wrong as saying that software projects are completely different than other projects.
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?