37 Signals tells us that "Late projects are late one day at a time."
All in project management
Frank Patrick points to an insightful poster: The Project Breathalyzer. It's a page of nine items that act as a sanity check for whether you should be driving a project (or project management office) or not.
Michael Schrage's "Making IT Work" editorial in the January 2006 CIO Magazine riffs off the results of the magazine's State of the CIO survey. "CIOs may think that backlogs are their biggest pain point. But the real cause of IT failure is mismanaged expectations."
Jack Dahlgren suggests that we should treat "The Schedule as a Symptom" at his Project blog. I like the description of the schedule as a hoped-for picture of how the project will go.
Bill Brantly has been thinking about how KM, TOC and Strategy are all related. Now he is proposing a mash-up of all these in "Knowledge Management, Theory of Constraints, and Strategy."
I came across Itensil 's Teamlines recently, and it appears to be a good process / project management tool. And I see it as having some components of CCPM as well.
Cutting Through points to a great paper on "Making virtual teams work." Trust is a huge aspect of any teams, and as this paper discusses, our ability to create and maintain trust in virtual environments is somewhat limited.
Project managers should be responsible for all the white space between well-defined activities in a project plan, says Frank Patrick. The hand-offs are where fumbles and missteps are most likely to happen.
Scott Berkun has a "New essay: how to learn from your mistakes" in which he has some great thoughts about living this life.
Typical CCPM Project Management Implementation. I'm mostly linking this because it is a nice example of retrospectively walking through a CCPM implementation, complete with fever charts.
In an excellent discussion on the CriticalChain Yahoo Group, Larry Leach mentions a point I hadn't put together before. "If you do not have a statistical basis for predicting the project end date, you have no basis at all." Essentially, even with a "unique" project, the elements of the project (the...
The Chicago Tribune had a below-the-fold article today on FBI hits glitches as it joins digital age (registration required - here is the same article at the Biloxi Sun Herald) The new system is already months behind schedule and more than $200 million over budget, and its backbone component will not...
More from the AIChE meeting. Jonathan Worstell of Shell Chemical in Houston talked in a a number of sessions about the importance of Concurrent Engineering. In Worstell's view, the basic problem that Concurrent Engineering solves is that projects are too complex and too long for traditional serial engineering, where each phase...
I have a lot of thoughts running about my head after the AIChE conference. One of the topics that happens to have a lot of blogosphere crossover recently is working with limited resources, whether in the lab or in business.
From Knowledge Board, comes an article about The use of Knowledge Management in Project Management in Russia - 28 Oct 2003 Knowledge Management - to understand and use the value of the relations between people. In order to gain an stable profit, the relations and interactions between people within one organisation...