1. Deliverable Management Has Three Layers

• Admin-level deliverable configuration System admins can define the organization-wide deliverable catalog in the admin area. This helps ensure consistent standards and supports standardized execution across projects.
• Workflow template deliverable configuration Workflow template owners can link deliverables from the organization-wide catalog based on different project types or stages, making it possible to tailor deliverable requirements for each template.
• Project and execution deliverable management When closing a project or an execution, project managers and delivery team members can submit deliverables based on workflow template requirements and maintain any content that has already been submitted.

Example

• Based on company requirements, a system admin configures deliverables in the admin area for the Close Project and Close Execution actions in product-based Waterfall projects. Note: Waterfall projects include Hybrid Waterfall projects, and Agile projects include Hybrid Agile projects.

  For example, the admin adds a deliverable called Project Closure Report for the Close Project action. The applicable object/action is set to Project + Close, the scope is set to Product-based Waterfall Project, and a description and template file are added.

• A workflow template owner then configures deliverables in the workflow template for product-based Waterfall projects. In the deliverable configuration list, available applicable objects include Project, Requirements Phase, Design Phase, through to Release Phase. Deliverables configured in the admin area can then be linked to the close action for each object. Note: Deliverable configuration in workflow templates applies only to new projects.

  For example, since the admin area already defines Project Closure Report as a required deliverable for the Close Project action in product-based Waterfall projects, the workflow template can then associate that deliverable with the relevant project close action.

• When closing a project or an execution, project managers and delivery team members can submit deliverables according to the workflow template requirements and maintain the submitted content afterward.

  For example, because the workflow template requires Project Closure Report for the Close Project action in a product-based Waterfall project, the project close form displays a deliverable field for submitting the Project Closure Report.

2. Admin Deliverable Configuration

In the project model settings in the admin area, you can manage the full organization-level deliverable catalog.

Click Add Deliverable in the upper-right corner of the deliverable list page to open the deliverable creation page. From there, you can add deliverables for project and execution close actions and upload the corresponding templates.

图1

图2

图3

3. Workflow Template Deliverable Configuration

In the deliverable configuration list of a workflow template, you can link deliverables from the organization-wide deliverable catalog to the Close Project and Close Execution actions, enabling tailored deliverable requirements within the project workflow.

图4

图5

4. Project Deliverable Management

When closing a project or an execution, users need to submit deliverables based on the workflow template requirements. Submitted deliverables can also be maintained afterward.

图6

In the project list, you can view the submission progress of project deliverables.

图7

In the secondary navigation within a project, click Deliverables to open the deliverable management page, where you can submit deliverables in advance and maintain previously submitted content.

图8