Project Reporting Fields

Summary

Shows the commonly used fields for reporting.

Body

The following fields are used in reports that are shared with campus leadership and utilized in Division of IT desktops in TeamDynamix. It is important that managers of projects update this information to ensure accurate reporting.

Type

Used in TeamDynamix desktops and campus wide reports. Select one of two options:

  • Operational / Maintenance Projects / Division of IT Maintenance Operations Projects
  • PCMO Evaluated / Large DoIT Project / Division of IT Project

Acct/Dept

Automatically populated with the department of the person who creates the project or if the project is converted from a ticket, it defaults to the department of the requestor of the original ticket. It is important to note that many projects are created on behalf of the requestor and show the IT department that created the project and not the department of the sponsor. It should be the department of the sponsor.

Manager
Refers to the Project Manager in TeamDynamix. This field is automatically populated with the name of the person who created or converted the project.

Executive Sponsor Division
Used in campus wide reports, providing awareness of the projects requested and currently underway by division.

Sponsor
Used in campus wide reports, When a ticket is converted to a project, the requester is mapped to the Sponsor field. It is important to check the Sponsor field to make sure that the true sponsor of the project is listed in this field. If a new project is created from scratch, the Sponsor field is left blank and will need to be filled out.

Project Name
Make sure project names convey the nature of the project; are succinct, avoid IT jargon, and avoid the use of acronyms.

Description
This is used in campus wide reporting and is meant to provide a high-level summary of the project and the outcomes the sponsor hopes to achieve when completed.

Campus Strategic Anchors
Shows how the project aligns with the campus strategic anchors. Included in campus wide reports.

IT Strategic Goals
Shows how the project aligns with the IT strategic goals. Included in campus wide reports.

Portfolios
Manually created in TeamDynamix and are used to group projects into different portfolios. Projects can have more than one Portfolio assigned to them. These are used most often by Enterprise Applications to represent the enterprise system portfolios (CRM portfolio, ERP portfolio, etc.)

Classification
Used in TeamDynamix desktop and campus wide reports and are used to indicate the size of the project. There are three classifications:

  • Project (20 - 230 Hours Effort)
  • Large Project (Generally over 230 hours)
  • PCMO Managed Project

Priority
Used in TeamDynamix desktops and campus wide reports and are used to group project request by priority level.

  • High
  • Medium
  • Low

Status
Used in TeamDynamix desktops and campus wide reporting.

Health Status
Is used in TeamDynamix desktop and campus wide reports. 

  • Green - The project is on track with no major issues or blockers
  • Yellow - When a project is at risk of missing the project deadline or an issue has come up the needs to be resolved that may impact the timeline
  • Red - When a project is blocked from moving forward or a major issue has impacted the timeline
  • On Hold

Update
Used in TeamDynamix dekstops and campus wide reports. Projects are required to be updated on a weekly basis otherwise their status will automatically change from Green to Yellow as an example. The only except is when projects are On Hold. 

Links
This is not used in reporting but it is worth noting that the Project Manager should link project documentation to the TeamDynamix project in the links section.

Resources
Used in TeamDynamix desktops and campus wide reporting. 

 

Details

Details

Article ID: 114827
Created
Wed 2/26/25 7:04 PM
Modified
Mon 3/17/25 2:46 PM