Premium
2.1.1 Defining Lean Systems Engineering Processes and Procedures
Author(s) -
Olson Timothy G.
Publication year - 2007
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2007.tb02872.x
Subject(s) - usable , documentation , process (computing) , computer science , best practice , process management , knowledge management , software engineering , engineering , world wide web , management , programming language , economics
Many systems engineering processes and procedures are large or difficult to use. The situation becomes even worse when complexity is involved. Putting large or difficult to use process documentation on a website does not usually solve the problems. This article will describe best practices for defining lean (i.e., short and usable) processes and procedures. These best practices have been used at real organizations over the last few years to define lean processes and procedures. Measurable results include cutting organizational processes and procedures in half while making them more usable (e.g., reducing 400 pages to 200 pages), without losing any useful information. This article will also describe some success stories and describe some lessons learned. The objectives of this article are to: Describe common problems with process documentation, including some human aspects of using process documents. Discuss some best practices for defining short and usable processes and procedures. Describe some success stories in real organizations. Provide some lessons learned.