In different phases of product development cycle, there are fairly routine processes which are repeated in different workflows. For example, jointreview as a sub-process is executed for different types of work product like a project plan, system design architecture, etc. Though the processes will differ, some of the sub-processes like review go through same steps to achieve the end result.

In Stages, such routine processes can be modeled once and reused in workflows which consume the process.

Model the routine process process in a workflow. The details of this routine process should be generic enough for it to be consumed in other workflows.

Joint Review Process is a typical peer review that happens at differents areas of product development lifecycle. It is held within development phases, between milestone reviews, on completion of work products. Defining it as a routine process allows to keep the details of the process consistent and standard across any form of review.

The activities in this routine process contain generic work products (e.g. work product under review) and roles (e.g. Joint Review Coordinator) which can further be assigned to specific work products or roles in the process where they are consumed as sub-process.

Only activities in a workflow can be linked to routine process. For example, in Project management, 'Review Software Project Plan' activity refers to the 'Joint Review' routine process to show how to perform the review. When a user clicks on this activity, they will view the joint review routine process below the project management workflow.

To model a routine process into a workflow, select the activity (e.g. Review the Software Project Plan) and navigate to the widget Find Details in and select the routine process (e.g. Joint Review). Additionally, specify the work products, phase, roles and other details for the activity in context of the workflow it belongs.