May 13, 1999 - Jack Harich
A process is a systematic series of steps to do something well. A defined process is the written and cultural expression of how things are systematically done well. Thus people, quality and process are inseparably intertwined. To succeed, a defined process has to be enthusiastically created, followed and continually improved by everyone.
Process Element
Relevance
One page summary Optional
Series of defined steps Required Clear step names Required Step objectives Optional
Step input Optional
Step deliverables Required Step exit criteria Optional
Step entry criteria Optional
Feedback loop Optional
Process Champion Required Key milestones Optional
Key approvals Optional
Summary Flow Chart Optional
Complete Flow Chart Optional
Process Checklist Optional
Deliverable templates Optional
To the right is a grid with the most common elements used to define a process. If a required element is missing the process will fail. Optional or additional elements are used to suit your needs.
In addition to the elements used to define it, a process has general traits that determine its effectiveness. These include:
Simplicity - The process must appear very simple. That's where a one page summary and short Flow Chart helps. Complexity can be hidden by drill down, optional elements, phased introduction, etc.
Understandability - A hard part of defining a process is making it understandable. Process is a new abstraction to many people, and so takes awhile to absorb. A defined process also appears to introduce more complexity to an organization (when actually it's reducing complexity) so presentation and training must be used to overcome this risk.
Ease of Use - The process should not get in the way, but instead smooth the way. It should feel fun and downright cool to use. It must not stifle individualistic artistic creativity. A Process Checklist can make following lots of steps easy.
Training - A non-trivial process cannot succeed without extensive training. Remember this training must not only educate on how to use your defined process, but what process is all about, and how to continually improve the process.
Examples - Each deliverable needs some clear examples. You can also have examples of the entire process, such as a well done past project. Examples can be used as templates, or you can have standard templates.
Flexibility - (Self explanatory)
Applicability - There's an explanation of when to use optional elements.
Internet Based - The entire process must be on the internet so that it's avaiable to all. This implies that most documents are in html.
Iterative - A waterfall process assumes all is known before each step starts, which is false. Your process must explicitly support iterations where useful without making things fuzzy.