|
 |
Home > Consulting Services > Config Mgmt > Doc & Stds > Service
Process Workflow Consulting and Implementation
Intended For...
Managers of organizations who are actively improving their software development process by following the Software Engineering Institute's (SEI) Capability Maturity Model (CMM)
|
Location
At client's site (by special arrangement)
Lead Time
Four weeks
Duration
Varies with project scope
|
Consultant Information
The consulting team includes several individuals with experience in process definition, software development, local area networks, tool selection, tool integration, database expertise, process definition, and the CMM. For Cost & More Information
801/DSN 775-5555
e-mail: stsc.consulting@hill.af.mil
|
Description
Process workflow is the use of workflow technology to provide process control and discipline in software development. Workflow technology supports structured routing, review, revision and tracking of software products, and process templates that can be tailored for each project.
Following is a list of STSC services for adopting workflow technology in compliance with the SEI CMM. Interested organizations may select a subset of these services consistent with their specific needs.
| Planning and Preparation |
| • | Gathering and prioritizing requirements for the user groups |
| • | Getting management buy-in via education (see Process Workflow Workshop) |
| • | Writing the Adoption Plan and Risk Management Plan |
| • | Designating the Adoption Team and their roles |
| • | Identifying candidates for and the scope of pilot projects |
| • | Providing lessons learned from previous adoption experiences |
| |
| Process Definition |
| • | Defining the existing processes and required new ones |
| • | Writing the Process Model document |
| • | Identifying potential process improvements |
| |
| Pilot Project |
| • | Installing, customizing and integrating a workflow system |
| • | Prototyping specific risk areas |
| • | Process Model testing and workflow system validation |
| • | Examining the user learning curve |
| • | Providing training and experience to in-house maintainers |
| |
| Roll-out |
| • | Getting user buy-in for change to the workflow system |
| • | Defining the approach to cut over to the system |
| • | Preparing the users for cut over via training |
| • | Monitoring system acceptance |
| |
| Process Improvement |
| • | Capturing successful pilot project strategies |
| • | Holding a post-adoption review |
| • | Identifying areas for process improvement |
| |
At the Conclusion...
The organization will realize tangible benefits that include: |
| • | Increased discipline in the use of the organization's defined software processes |
| • | Savings of time and space |
| • | Capture of workflow process metrics |
| • | Movement up the CMM |
| • | Improved internal communication |
| • | Tool users' satisfaction |
Prerequisites
Management commitment to software process improvement based on the CMM.
|
|
