While I’m no project/portfolio management expert, I do know a thing or two about common issues that people tend to encounter in this industry, particularly when rolling out a Project Server implementation. One relatively big issue is organizational resistance. You make this big investment in Project Professional and Project Server, because you know it’s what’s best for your business, and then, once you roll it out across the company, you hear little complaints coming in…”I don’t want to fill out timesheets,” “my Excel spreadsheet is working fine for me, I don’t want to learn a new tool,” and so on. No surprises there…the learning curve is steep for the tool itself, and for the formal process you’re trying to implement. We know that, you knew it when you rolled it out, no big shocker. So given all that, what can you do to ease the transition and help avoid the inevitable pushback from the people you’re asking to use this new solution?
Again I have to emphasize that I’m no expert, so I’m sure many of you out there have more informed suggestions that I hope you’ll share in comments on this blog post. I can, however, offer these suggestions, gleaned from a decade of documenting project and portfolio management software solutions:
These are just a few suggestions for ways you can prepare your organization for what’s to come. I’d love to hear other suggestions, or pointers to resources you find helpful in preparing organizations for new Project Server rollouts. What are your thoughts?
But I think the usability of Actual Work input grid of PWA 2007 is clearly worse than that of PWA 2002.
This kind of functionality 'downgrade' is one of the biggest triggers of organizational resistance.
I don't want to blame my colleages when they resist and complain about the upgrade of Project Server.
Microsoft engineers should be humble enough to accept that their latest version is NOT always the best product.
STAGE the benefits -- PS2007 is complex enough, make sure you roll out features at a rate that matches your orgnanizations agility, evolution, and abilty to change. Resource utilization and portfolio management can be overkill for less developed practice areas.