A controversial deal on the future of the .com domain has been approved by the net’s overseeing body.
Archive for 2 March 2006
The “100 Rules for NASA Project Managers” has been doing the rounds online for years, so much so that it’s probably reached the status of something of a classic by now. They’ve had their fair share of high-profile failures over the years (solid fuel boosters, Hubble mirror and so on) but these are the relative minority compared to the huge number of successful projects that the space programme has delivered. And while some of the rules fall into the category of the blindingly obvious, it’s a list worth re-reading every now and again.
[Rediscovered via ProjectSteps; the full list can be found here .]
Rule #1: A project manager should visit everyone who is building anything for his project at least once, should know all the managers on his project (both government and contractor), and know the integration team members. People like to know that the project manager is interested in their work and the best proof is for the manager to visit them and see first hand what they are doing.
Rule #2: A project manager must know what motivates the project contractors (i.e., their award system, their fiscal system, their policies, and their company culture).
Rule #3: Management principles still are the same. It is just that the tools have changed. You still find the right people to do the work and get out of the way so they can do it.
Read the rest of this entry »
