ABSTRACT
The Software Process Model Concept Selectability is a key concept throughout this book because it really addresses tailoring of process entities at all levels of the process framework architecture. Like any architecture design, this also has a “system” design — except we’re dealing with process rather than software. Another big aspect of this software process method is that it really is a framework architecture into which process parts fit. The word “fit” is very important, especially because I’ve seen process elements in place yet people don’t know why they’re there or they don’t know where new process elements fit in the overall scheme of things. Think of a framework as the bones onto which we add the process meat. The beauty of this architectural design is that it separates the framework architecture (in the process specialist domain) from the actual process elements (in the organization’s domain). This separation will become a powerful concept later when you organize any process group to populate/control processes in any organization. As Software Engineering Process Group (SEPG) lead and process architect, I concentrated solely on the integrity of the process model whereas the SEPG members concentrated on the actual process elements within that process framework. I have had very successful process groups that have worked effectively and efficiently due to this work separation. I have to admit I led one process group where I was not allowed to make this work separation and it was less than successful — due to a boss who
just didn’t “get it.” This guy was a “my way or the highway” type of individual who had no process background and who insisted on making bad decisions. Any suggestion from me was DOA (dead on arrival) by virtue of it not coming from him. If you are a process person and get into this situation, run fast. You will never succeed. This type of boss will affix blame for all his bad calls on you.
