The Problem with Late Software
March 14, 2008 · Filed Under BI, Project Management
With the delay of the highly anticipated database, Microsoft SQL Server 2008, the problem of late software releases is again receiving attention. An article over on TDWI highlights four problems a delayed software release can cause:
- Delayed implementation
- Delayed training
- Loss of project budget
- Loss of momentum
I would also add the following:
- Rushed testing, resulting in potentially unforeseen problems during the go live.
- The time and budget originally allocated for enhancements is reduced, affecting long term satisfaction with the solution.
- The snowball effect: follow on projects are delayed.
- Disappointment among business users. Their hard earned trust in the IT department is eroded.
After reading through the article, I realized that these challenges are not specific to BI projects, or even projects based on off-the-shelf software. Any project with a wide audience of end users, executive level visibility and high expectations will be severely affected by pushing out a release date. This is a risk that must be considered and mitigated from the very beginning of any IT project.
Related Posts:
Are Analytics the future of BI?
Comments
Leave a Reply