Michael Krigsman makes a living from the subject of of IT project failure. There are a number of issues he discusses on project failures:
There was report in the South African Sunday Independent on 18 April 2010 which highlighted a number of the issues Michael has covered. The report concerned the bungling of the multi-billion rand contract awarded by the South African Department of Home Affairs to black-empowered IT company Gijima AST. (Note: The Sunday Independent only gives access to articles online for subscribers of its print version).
In a memo by the consultant whom Home Affairs contracted to manage the project, some typical IT failure issues were mentioned.
- Lack of project ownership by the client (Home Affairs), leaving Gijima to determine and drive the project deliverables, and making project governance difficult.
- Lack of involvement and support from the client executive sponsor.
- Poorly defined business case, little budget commitment and continually changing project priorities. Points 1 and 2 create this situation.
- Low level of capability in the client making it difficult at the IT level to get agreement on technical architecture and design specifications, as well as at other levels.
- Lack of end-user skills in the client to enable the project to achieve objectives.
Reading the article made me sympathise with the project manager, who I once worked with at one of South Africa’s big banks.
The question some South Africans are asking is how and if Home Affairs and Gijima can patch things up and get the project going again. From this South African’s perspective, however, one question is how would you go about reviving this project. A place to get ideas would be from Glen Alleman’s discussion on Project Disentanglement. The other question would be, for such a high profile and high risk project, who would be prepared to take on the project management role.
How would you go about getting such a big government project back on track? And would you even want to?