Turning Around Runaway Information Technoloy Projects

I came across this article on the train ride to the J Class on a Friday. Note down some takeaways here.

Recommedations with my translation 'N comments
1:Develop a recovery plan - External Consultant
2:Manage the scope - Cut features
3:Re-evaluate the project leadership - The required skill set, Strong leadership, people-management & comm skills. Sometimes it's really hard to find a qualified candidate.
4:Re-estimate the biz case and consider cancellation - Triage, as Microsoft guys may call.
5:Re-plan the project using proper and proven estimating methods. - This is Shit! Check it out:http://www.joelonsoftware.com/items/2006/11/10b.html
6:Manage Users' expectations - Don't Try this!! You may break the contract and lose a lot of money
7:Formulate an open communication plan - Tell everybody that we've screwed the job.
8:Break the remainder of project into small portions - This is hard! And this is tipically something said by someone who has never debugged, or some really lucky guys who have never met a bug in their whole life.
9:Deal with the people issues of the project team
- Lack of required skillsets: The famous silver bullet. Do you ask your programmers-to-be write code during an interview?
-Dismissal of members: Spec & clear comment lines
10: Incorporate corrective practices in the development process -
Be Cautious! Adapting new methodologies may even further slow you project down.
But it's good and essential to do Postmortem!