Most projects fail due to a manager's ambition or pressure to complete on time. This leads to significant errors.
Here are two examples from the opposite sides of the spectrum
- I have been witness to a very large and very risky project, which was initiated with nearly no regard for the risks involved. The project was completed successfully but only with the titanic effort and dedication of the project team.
- Only 2 weeks later, I was a witness to a project which had major issues with coordination, communication and breached deadlines, but still it went ahead. Sadly, the project finished with a major issue, mostly because of project staff fatigue which led to human error.
You should ALWAYS be prepared with an answer to the following question:
- What is the 'deal breaker' of the implementation? Under which conditions should we abort and re plan?
- Risk to business continuity
- Risk of impact to core business operation
- Risk of major personnel harm
Talkback and comments are most welcome
Security risks and measures in software development
4 Controls to Avoid Risks of Fully Trusting a System
Information Risks when Branching Software Versions