The Art of Project Management: Expert advice from experienced project managers in Silicon Valley, and around the world
TOPICS:

A System Perspective on Project Management Part II -The Mega Project

 

As I write this I am helping to facilitate a workshop dealing with how to transition the US portion of the International Space Station (ISS) into the first National Laboratory in space.  We have 200 experts from all over the world working to figure out what the early experiments should be and how to implement them over the next 5 years.  Just the planning for this workshop has been quite a lesson in project planning and execution.  Chaired by Nobel Prize winner Baruch Blumberg and with a keynote address by J. Craig Venter of human genome fame it has been quite an interesting event.  It has caused me to think back on the lessons that I have learned over the last twenty three years I have been involved with the space station about managing mega-projects.  

For those of you who are not familiar with the ISS it is a permanently manned,16 nation collaboration that is in orbit overhead every 90 or so minutes.  It is over 300 ft. long and weighs over 400,000 lbs.  When construction is complete in 2010 it will weigh over 1 million lbs.

To say the least it is a very complex vehicle and by the time it is completed American taxpayers will have spent upwards of $100 billion to build and operate the ISS.  I have been involved with the ISS in its various incarnations since the early 1980’s.  There are some good and not so good project management lessons learned in this project.

 

1)      Don’t start vast projects with half vast resources.  When the ISS (it was called Space Station Freedom back then) was first announced by then President Reagan in 1984 the ISS was supposed to cost $8 billion.  As we can see it cost more, a lot more.  There have been so many redesigns over the first fifteen years that it is hard to keep them all straight and all these changes cost big money.  Having Congress in the loop holding the purse strings doesn’t help either.  So make sure you have a handle on the costs and that the value proposition is well defined and that you get alignment with the customer.  Which brings us to our next lesson learned;

2)      Spend 10% of the project budget making sure you understand problem, the key technologies involved, and have looked at all of the options before you dive into the detailed design.  Many studies have been done that show by the time 5% of the project budget has been spent 70% or more of the project cost will be locked in and not just the development cost but the life cycle cost.  So cutting this upfront study effort is a really bad idea but we do it all the time.  If there is a better example of penny wise and pound foolish I can’t think of it.

3)      Keep the team as small as possible.  Having been on several of these mega-projects they seem to grow magically.  People are attracted to the project like moths to a flame.  But be careful in that all of these people need to be managed and if left to their own devices they can be much more trouble than they are worth (more on this later).  You need to make sure that have the proper skills and technologies represented and some good systems thinkers who can see the “big picture” we talked about last time.  Even on an effort that could grow into a billion dollar program starting off with 8-12 really good people is much better than starting off with hundreds of confused or clueless people.  Be careful of people who are just there to stake out turf for later phases of the project.  They can sabotage your project (intentionally or unintentionally).

4)      Don’t bring on the design engineers too soon.  One of the worst things you can do in the early phases of a project is to bring on a bunch of detailed design engineers and then not give them clear direction and close supervision.  What will these bright and motivated folks do in a situation like this?  They will deign something.  Even if they don’t really understand what the problem is and even if they don’t have any requirements they will start designing something.  It is kind of like going to the symphony where there is no score and each musician just plays their favorite piece as loud as they can.  I don’t know about you but this isn’t something I want to go hear.

Well I have to go and facilitate the output of 15 working groups that are addressing how to implement this National Lab in space that has never been done before.  It will be interesting to see if what they come up with.  If you are interested in the workshop output and the potential for microgravity research you can take a look at our website www.alliancespace.net.   The results of this workshop should be posted shortly and there will be streaming video of the presentations.

 

More soon. 

Bruce 

Share

About the Author

Bruce Pittman has been involved in high technology product development, project management and system engineering for over 25 years. He spent 11 years working for NASA on planetary exploration and space based infrared astronomy projects. From 1985-1998 he was a consultant and educator for both industry and government in project management, system engineering, concurrent engineering, risk management and planning, both in the US and abroad. From 1999-2002 Bruce went back inside corporate America as a Director for two high technology firms, one in telecom hardware manufacturing and the other in enterprise software for new product development. He reactivated his consulting practice in 2003 with a 6 month consulting assignment in Costa Rica with a high tech medical device company. In 1993, Bruce co-founded Profit Engineering Technologies (PET), a high technology project management consulting and education firm. PET developed an integrated set of training courses and consulting services designed to improve organizational efficiency and product development process performance. Bruce also worked with both government and industry project teams as a facilitator, coach, and mentor to increase the speed and quality of the development process and reduce overall project risk. As a consultant, coach and trainer Bruce has worked with a wide variety of both Fortune 1000 companies and smaller companies in the US, Europe, Asia and Central America, including Align Technology, New Focus, Varian, Westinghouse, Lockheed Martin, Northrop Grumman, Cepheid, Behring Diagnostic, and government agencies such as NASA, and DoE. Bruce has also participated in a number of startups in such diverse areas as aerospace, energy, semiconductor manufacturing and medical devices. Bruce has a BS in Mechanical Engineering from UC Davis and a MS in Engineering Management from Santa Clara University. He is a Vice President and member of the Board of Directors of the Society of Concurrent Product Development. Bruce is also an Associate Fellow of the American Institute of Aeronautics and Astronautics. As a member of the International Council on System Engineering (INCOSE) Bruce co-authored the EIA 632 ANSI Standard “Engineering of Systems”. He has published over two dozen papers on technical and management topics and edited two NASA workshop volumes. Bruce has been an invited speaker at many professional society meetings and conferences. In addition to his consulting work Bruce is also a member of the adjunct faculty in the Graduate Engineering School at Santa Clara University. While working at NASA Bruce was awarded two Sustained Superior Achievement Awards and two Group Achievement Awards. He was also presented a Distinguished Leadership Award by the AIAA.
Creative Commons License
Note: This work and all associated comments are licensed under a Creative Commons Attribution-Noncommercial 3.0 United States License.

Leave a Reply

*