Process Oriented Design^TM (POD^TM) is an important subset of our overall methodology, the S3P^TM.

POD^TM is a new breed of software development lifecycle. As efficiency and effectiveness become more important in the software industry and with custom software implementations, more and more focus is being placed upon the process of software development. Hence, we see the popularity of standards such as CMMi and new software development methods such as extreme programming and rational being devised and touted by their followers.

It then follows suit that the processes being automated by the software will eventually come under such scrutiny. Face it, no matter what software development methodology chosen, if emphasis upon Quality of the operating processes being automated is not implemented, the resulting software products will not satisfy the needs of the user community.

POD^TM requires software professionals to account for processes first and foremost from concept through management of a new software system. POD^TM requires software engineers to learn techniques such as SIPOC, State Diagramming, CTQ, VOC, Process Mapping, COPQ, QFD, Process Variable Definition, and cycle time analysis. Further, POD^TM makes use of proprietary techniques developed by 6STG such as Key Decision Point Definition and Process Portfolio Definition.

Besides the obvious problems of not properly engineering processes nor implementing the techniques and tools for continual improvement, using these methods for BPM implementation can deceive management into thinking that because BPM is in use, the organization is implementing process excellence. When in reality, software developers have simply taken the silo centric requirements gathered from the user community and automated them using BPM.

Alternatively, POD^TM ensures that those implementing BPM use a method that drives proper definition of end-to-end processes as well as the techniques for effective engineering and continual improvement of these processes.