Revisiting Plan your dive.. than dive your plan

One of my original posts has to do with planning…  Revisiting it and adding a little to it

When i was starting out in IT, I took a lot of classes to get certifications.  Most I realize were kinda dumb and not worth it in the long run.  In fact I think most of the certifications are for companies and software that no longer exists.  But back to the story.

When building and releasing applications the teacher used a metaphor of Diving.  Being a diving instructor as well as teaching IT, he stated I am going to teach you to plan your dive, then dive your plan.  He wanted us to make sure that our turnovers went smoothly, he taught us how to make sure we created install scripts, and tested them.  He wanted each step to be documented, and timed to the minute.   Once the scripts and the instructions were completed, we had planned our dive.   The next step, dive to the plan or execute the turnover.

This has stayed with me for over 20 years of building IT projects, and does help me get things done.  But sometimes you have to know when to “alter” your plans.  Each plan needs to come with some checkpoints.  These checkpoints have to be early than often.  You dont want to go 2-3 months into a project and realize the target has changed.  Do not be afraid to change course, but only change course after you have done some evaluation

My world famous disclaimer…  so, this blog has nothing to do about my current employer.  I provide the information without warranty blah blah blah. I make no money from this blog, there is no advertising, or charges to anyone.  I do this as a brain dump, to leave something behind.  If you want to support me, instead of doing that support one of the charities i care about, the Morgan Stanley Children’s Hospital and Hockey in Newark.  I do moderate all comments, and try to remove anything that is not in the spirit of the site.  Thanks for reading.