Reforming Project Management |
||
|
Wednesday, May 14, 2003
Weekly Project e-Tip: Conduct Plus-Delta Reviews to Encourage Team Openness
Here's my third weekly Project e-Tip. I've decided to emphasize the fifth lean principle, pursue perfection, in my early e-tips. This one has the added benefit of producing a team dynamic of open communication. This is key to benefit from the varied perspectives and expertise of project participants.
Note to readers: I've got five subscriptions to Business Book Summaries that I want to give away along with five copies of Purple Cow. Submit your tip. Monday, May 12, 2003
Substitute Fast Learning for Brilliant Planning
I keep hearing people say, "We spend too much time in meetings." The complainers often have a good point. Project meetings are often poorly run and don't result in action. On the other hand, there are people who complain about all meetings. Jeffrey Pfeffer, co-author of The Knowing-Doing Gap writes Don't Believe the Hype About Strategy in the May issue of Business 2.0.
Pfeffer argues that we spend too much time talking about what we will do and not enough time (and intention) on doing it. While the article is about strategy, he could have been talking about project management. Talking replaces action, planning replaces learning by doing.Pfeffer finishes the article encouraging readers (I)nstead of sitting in meetings and producing fancy PowerPoint demonstrations, develop your strategy by using your company's best thinking at the time, learning, refining, and trying again. Under almost all conditions, fast learners are going to outperform even the most brilliant planners.Projects are always about "implementing and executing." Let's substitute some fast learning on our projects for some brilliant planning. Sunday, May 11, 2003
Future of Coaching
Low Intensity Project Management, Beware of the Trojan Horse
Low Intensity Project Management by Andrew Weiss, PhD, PMP, appearing April 30, in Gantthead.
The article is both seductive and frightening. Weiss states, ...not all project management is highly structured and driven by formal tools. Towards the end of the article he characterizes low intensity projects: LIPM is far more of an emergent activity than standard project management (in other words, project management in a given organization would arise more from situational variables than from adherence to standard practices). LIPM thus tends to be more experimental than prescriptive.Are you beginning to see the seductiveness? (for me anyway) It's all the stuff in between that's scary. Weiss offers one rationalization after another describing why some organizations or situations may not be ready for the formal approaches that they really need. (my paraphrase) He sees taking a LIPM approach as a way of introducing more formal approaches to organizations. An example: Work breakdown structures. In the LIPM environment, one of the most challenging tasks is simply keeping track of what has and has not been done. Personnel are probably not used to regularly reporting on their progress or looking at their activities in a structured, hierarchical manner. However, once they are shown how to do so, the WBS becomes a powerful tool for project control.See what I mean? In short, LIPM is a Trojan horse for introducing formalized methodology and all the trappings. Still looking for just what's needed and no more? Consider designing a set of practices based on Fernando Flores description of projects. You're sure to do better than LIPM. Visit the Archives for more postings |
Reference Papers
|
|||||||
|
| ||||||||