A common cause of cost overruns in IT projects is unrealistically estimating that everyone involved will actually spend eight hours a day working on it. In other cases, managers don’t budget enough time for people to learn new software or business processes–like when a person with no accounting background develops an application for accounting. Then there’s documentation, paperwork, and e-mail.
Factors outside the control of IT–vendors or client departments–can also force a change in specs after the project is underway.
We’re looking for cost-overrun stories for an article that will appear in CIO Republic. If we use your story, you’ll win a prize.
You can share your story in this discussion or by e-mailing me.
Thanks,
Suzanne Thornberry
suzanne.thornberry@techrepublic.com
Web Editor
CIO Republic