Mike Griffith's has got me thinking about PMBOK®, the Agile software development processes and a general notion of "what to do." Alec Satin has a nice "electronic book" of 72 tips for project managers. Please subscribe for some useful information.
Anyway, I've got an idea to move the several decades of experience, ideas, and actual beneficial outcomes into a book like Alec's. Here's the outline...
Now I don't have experience in all these areas. But I do have deep experience in some. So I'm going to start collecting advice from the 3 dozen or so notebooks I've filled.
Along the way, it'd be interesting to see how agile software processes can be connected as well. By connected I mean practical, field proven activities that "answer the mail" (as we say in the defense proposal business).
My personal experience is focused on building the Performance Measurement Baseline (PMB), performance measurement processes (Earned Value), programmatic and technical risk management, the ubiquitous Work Breakdown Structure (WBS), and the programmatic architecture represented by the Integrated Master Plan and Integrated Master Schedule, the measures of increasing maturity, Measures of Effectiveness, Measures of Performance (MoP), and Technical Performance Measures (TPM).
I'll make an effort to add to the list every week and store this "map" and the information on the www.niwotridge.com site.
