![]() |
![]()
|
| Main Site > Software / IT Channel > Methodologies > Management | Search: | for |
|
Business Process Management for Software Development
By Gary A. Gack The term "business process management" (BPM) is often encountered in conjunction with Six Sigma and Lean initiatives. Typically it refers to identification of core business processes, assignment of process ownership and definition of measures (and perhaps benchmarks) that indicate the health of a particular process. These measures are often influential in selection of Six Sigma or Lean projects. Ideally, processes are defined in a way that is independent of the specific organization structure used to execute those processes. Hence, they are best described in terms of what is being done without regard to who or how in a solution-free, action-verb form. Though BPM is less frequently encountered in software development organizations, it can be equally powerful as a guide to identification and prioritization of improvement opportunities in software companies. Core Process in Software DevelopmentSoftware development processes may be grouped into two process areas lifecycle processes (analogous to core business processes) and cross-lifecycle processes (analogous to supporting business processes). Primary lifecycle processes in software organizations might be described as follows:
Primary cross-lifecycle processes typically include:
Process Measures in Software DevelopmentPerformance of all software processes can be appropriately characterized by some combination of the following metrics:
Essentially, the software development dashboard or scorecard boils down to a set of measures that answers three questions for each process:
Answering these questions in a meaningful way requires the use of compound measures that qualify conclusions in relation to factors known to be influential. The following table illustrates contents of a dashboard that succinctly provides answers to the above questions.
While there are potentially additional measures that may be of interest, any organization that has all of these is certainly far ahead of the pack. About the Author: Gary A. Gack is a founding partner of Six Sigma Advantage, based in Rockland, Massachusetts (USA). He has an MBA from the Wharton School, and is an ASQ-certified software quality engineer and a Six Sigma Black Belt. During his 40-year career in the software and IT industry, he has managed a variety of large-scale software projects and has consulted with dozens of Fortune 1000 firms. Mr. Gack co-authored Six Sigma Advantage's Black Belt, Green Belt and foundation curriculum. He can be reached at ggack@6siga.com. Reproduction Without Permission Is Strictly Prohibited Copyright Requests Publish an Article: Do you have a Six Sigma tip, learning or case study? Share it with the largest community of Six Sigma professionals, and be recognized by your peers. It's a great way to promote your expertise and/or build your resume. Read more about submitting an article.
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home | Discussion Forum | Event Calendar | Job Shop | |
| Link To iSixSigma | Rate This Page | Report A Problem | Free Content For Your Site | Submit Article For Publishing | |
| Terms of Service. �2000-2009 iSixSigma. All rights reserved. v3.0lb, 0.1 |
About iSixSigma � Contact Us � Privacy Policy � Site Map. |