Recovering Troubled Projects
Yesterday I met with the IT Director for the Wyoming Department of Health. Ostensibly we were meeting to discuss me coming to Cheyenne as a contractor to help them turn around the Wyoming Client Information System – a project with which they have been having a great deal of trouble. It was pretty obvious from early on that my rate is a bit too high fro them and so I steered the discussion towards how they could best recover the project. I had planned fro this eventuality and had brought with me a traditional consulting leave behind that is a guide for project recovery. I had gained significant historical info and a lot of insight by speaking with members of the development team in the weeks prior to the meeting. This helped me tailor my presentation and leave-behind materials to WCIS and SoWY specifically.
Over the years I’ve developed a process I use to accomplish a recovery. I didn’t invent this process all by myself it has bits and pieces from others who’ve gone before me, but it has been tailored over the years to provide a framework that is most effective for me. This project recovery process is what I introduced the folks within SoWY IT to and what I left behind for them to use to hopefully recover the WCIS project. Here is a picture that provides an overview of the process:

My meeting with SoWY Department of Health is a perfect excuse to discuss, once again, the process for project recovery. So I’ll be breaking it up into bite size chunks over the next month and posting about the specifics. Stay tuned!! Hopefully this refresher will be beneficial.