Project/Request Sections represent the different parts of a project request or project. Administrators can control the names of these sections and which ones are active within TDAdmin.
Managing Name and Order
The Display Name and Order of the Project/Request Sections is set in TDAdmin > Portfolio Planning > Project/Request Sections. This page allows you to edit the Order and Display Name for each section. These settings will apply to all projects and project requests.
Setting Visibility by Project Type
The visibility of each Project/Request Section is controlled by the Project Type (TDAdmin > Portfolio Planning > Types > [Project Type] > Project Sections tab). Each section can appear or disappear based on the project request lifecycle, with the following stages:
- Request - sections visible during the Request phase can be viewed and edited by requestors before they submit the project.
- Review - sections visible during the Review phase can be viewed and edited by evaluators after the project request is submitted.
- Project - sections visible during the Project phase can be viewed and edited by any project resource after the project request is converted to a project.
Changing the visibility settings for a project type will not affect existing projects and requests, as the Project Type's settings are applied to the project or request when it is created. If the sections on an existing project or project request need to be edited, they can be modified from the Project or Project Request details page in TDAdmin.
Types of Project/Request Sections
TeamDynamix supports the following Project/Request Sections
- General - This is the main section of the entity. Items like the title, the start and end date of the entity, etc.
- Custom Attributes - A separate sub tab is available to easily manage, as well as clicking to the custom attributes that have been associated with the entity.
- Goals - Goals can be a component in project scoring. These are usually organizational strategic goals like Increasing Revenue.
- Systems Affected - A project might affect different systems in your organization, ex, Banner or LDAP. These items can be created in the system and then associated with requests and/or projects.
- Related Processes - A project might affect a business process, like an employee on-boarding process. These items can be created in the system and associated as needed.
- Risks - Risks can be a component of project scoring. These are usually organizational risks, an example being Falling out of regulatory compliance.
- Benefits - allows one to configure both a monetary and intangible benefit that will be gained by delivering the project. Benefits allows for the selection of a benefit type and then fields to specify the financial benefit of doing the project over a 5-year period. For more information on adding them, see the linked KB.
- Files - These are files that can be associated with the request, and these files will eventually become entries in project briefcase.
- Expenses - Expenses are used to categorize spending and are used as part of Resource Planning and Management.
- Time Types - Time types are used to categorize tracked time.
- Returns - See the linked article for the formula used by TeamDynamix to calculate returns.
- Role Forecasts - This section can be used to add Functional Roles
- Resources - Resources are actually users that can be pulled into the entity. If the request has not yet been submitted, then this tab can be used to pull other users in to collaborate on project requests. If it is already in the Projects app, then this is how resources can be added to the project to give them visibility into the project, as well as allowing them to be assigned tasks.
- Score Card Criteria - these are custom items that can be a component in project scoring. Each of these configurable choices also can have configurable choices and values.
- Stakeholders - these can be added using the RACI matrix to show what relationship that stakeholder has with the entity.
- Plans - a tab that allows you to create waterfall plans to schedule out the tasks needed to complete the entity.
- Milestones - A baked in view to see all of the Project level Milestones