Handling project scope changes

In TeamDynamix there are three common ways to document project scope changes, depending on the level of rigor/formality needed.

Option #1: Project Issues

This is the simplest way to track project scope changes. You create a project issue category called "Scope change" and use the issue statuses to track whether the scope change has been reviewed or approved. With this option, anyone could potentially change the issue's status, although that status change would be documented in the issue's and project's feed.

Option #2: Project document workflow

This is a more complex option that a less common feature in the Projects application. To use a project document workflow, you

1. Define the workflow in TDAdmin > Projects > Document Workflows. (This is creating a workflow you can then apply to the project.)
2. Make sure the workflow is active.
3. Go to TDNext > Projects > the project record > Manage > Workflows.
4. Select the workflow you defined and click "+" to add it.
5. Click on the workflow and edit each step to assign the step within your project.
6. Decide whether to lock the file after approvals. (If it's locked, the file can never be changed.)
7. Create a Briefcase folder for "Project scope change requests."

Then, when there is a project scope change, create a file describing that scope change and add it to the briefcase folder. Then, open the file and under "Workflow" click "Assign to Workflow."

Option #3: Project scope change ticketing application

This is the most flexible but most intensive option. Here you create a new ticketing application for project scope changes tickets. This application has one or more workflows that apply to these tickets via automation rules. Then, when the ticket is approved, the project manager may receive a notification and/or the project manager may convert the ticket into a task to represent the work needed for implementing that scope change.