Premium
2.4.1 10 Pitfalls of System Process Development with Avoidance Solutions
Author(s) -
Arnold Eileen
Publication year - 2004
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2004.tb00499.x
Subject(s) - process (computing) , usable , process management , computer science , business , engineering , operations management , world wide web , operating system
Process literature has provided excellent guidance on what to include when writing new process descriptions, but very little has stated clearly what actions must be taken by companies during the course of developing usable, integrated processes. Countless hours have and are being spent on development of company processes, which end up sitting on shelves in their unopened, shrink‐wrapped notebooks, or archived to sparsely accessed and often ignored internal web sites. Management assumes the processes must not be the right ones, or personnel would joyfully use them. The result is yet another extensive effort to “get it right” by re‐writing the processes with a different slant. Why is it that processes are not well received or utilized by some companies, yet others embrace process with open arms? This paper explores the author's experienced pitfalls of integrated, system process development at an organizational level, whether that translates to a program, division, or enterprise level, and offers avoidance solutions to help remedy the maladies. This paper is intended to provide solutions to circumvent the common maladies associated with process development and process improvement.