PM Tutorial  (1:00 pm – 5:00 pm)

How to Define Lean Processes and Procedures

by Tim Olson, Steve Flanagan, and Scott Lewicki
Intermediate level

Summary: Many organizations suffer from processes that are too large, too complex, and too hard to use.  Most organizations are struggling with how to define “good processes” that are lean (e.g., short, usable, value added).  This half-day tutorial will describe what is a “good process”, and describe how to define lean systems and software engineering processes.  When a pilot flies an airplane, he or she doesn’t pull out volumes of process manuals.  Pilots use short and concise “expert mode” checklists.  This half-day tutorial will discuss common problems with process documentation, discuss the human aspects of using documentation, provide some lessons learned of “what works” and “what doesn’t work” in organizations, and provide some lean examples of good processes from industry.  Real lean examples from NASA JPL will also be presented.  The best practices described in this tutorial also scale up to defining complex systems engineering processes.  There will also be time for questions and answers.

Abstract: Many organizations suffer from processes that are too large, too complex, and too hard to use.  Most organizations are struggling with how to define “good processes” that are lean (e.g., short, usable, value added).  This half-day tutorial will describe what is a “good process”, and describe how to define lean systems and software engineering processes.  When a pilot flies an airplane, he or she doesn’t pull out volumes of process manuals.  Pilots use short and concise “expert mode” checklists.  This full day tutorial will discuss common problems with process documentation, discuss the human aspects of using documentation, provide some lessons learned of “what works” and “what doesn’t work” in organizations, and provide some lean examples of good processes from industry.  Real lean examples from NASA JPL will also be presented.  The best practices described in this tutorial also scale up to defining complex systems engineering processes.  There will also be time for questions and answers.

Presenters Bios:

Timothy G. OlsonTimothy G. Olson is Founder and President of Lean Solutions institute, Inc. (LSI).  While performing training and consulting, Mr. Olson has helped numerous organizations measurably improve quality, productivity, and performance, save millions of dollars in costs of poor quality, and has helped numerous organizations reach higher Software Engineering Institute (SEI) maturity levels.  Mr. Olson is a leader of applying Lean SolutionsTM (e.g., lean processes, metrics, requirements) to systems and software engineering.  Mr. Olson has been formally trained in Baldrige, Crosby, Deming, Juran, ISO, CMMI® and Six Sigma quality approaches.  Mr. Olson is a Malcom Baldrige National Quality Award (MBNQA) Examiner (2008) and a Juran Institute Associate.  Mr. Olson was a lead-author of a Software Quality Course for the University of Minnesota, and he is currently a senior member of ASQ, and a member of IEEE and NDIA.

Dr. Steve FlanaganDr. Steve Flanagan holds a Ph.D. in Aerospace Engineering from the University of Tennessee and has worked at JPL for 17 years. He is currently the Deputy Manger of the Quality Assurance Office at JPL, which includes both hardware and software quality assurance. Prior to his current position he was the Deputy Manager of the Software Quality Improvement Project, where he led JPL's successful CMMI implementation for the Engineering and Science Directorate. Previously, as a member of the Navigation and Mission Design Section, he managed the development of a new interplanetary navigation software system, led the Mission Analysis Software task, and was the lead interplanetary trajectory analyst for JPL's Cassini mission, which is currently in orbit around Saturn.

Scott Lewicki is a Senior Member of the Engineering staff at NASA's Jet Propulsion Laboratory (JPL) and currently works for the Software Quality Improvement Project in the areas of Product and Process Development and Software Process Engineering. Recently, he was instrumental in helping JPL's Engineer and Science Directorate (ESD) Mission Software achieve CMMI Maturity Level 3. He has over twenty years of experience at JPL supporting software intensive tasks including Earth Observing System instruments and the Magellan Venus Radar Mapper, and has taken on the roles of software manager, subsystem and interfaces engineer, and developer. He has a B.S. in Physics from the California Institute of Technology. Email: Scott.Lewicki@jpl.nasa.gov