That is 97 things a project manager should know.
I recently participated in a webinar that dealt with the subject of what I project manager should know, or at least consider to insure success of his/her projects.
It was quite a lot of information and yet useful. There is a book of the same title: 97 Things Every Project Manager Should Know. While the presentation in the eyes of some was lackluster, I did my best to try to get the most out of it.
I’m an application developer, but definitely take the role of Project Manager often enough to warrant exploring this subject in depth. Every project has it successes and failures and sometimes the entire project bombs. Following most tips if not all will most assuredly make our lives easier.
Some things just stand out. The question was asked: Where are the users? In typical fashion we plan, design, code and when we’re ready to unveil our wonderful creation, it surprises everyone. Is not what they expected! Along the way users should be included and know fully what’s going on. It’s amazing how many times, at least part of the user groups, by circumstance or happenstance are excluded from the design process.
Egos are bruised, folks are upset, and the project needs to be rescued. An application may finally go into production, but at what cost? How much work after going live is devoted to fixing or changing things? That measure is a tell tale sign of what was left out in the design process.
So off to explore those 97 things I go!