Advice on how to track requests for an approvals of project extensions
Hello all! My school is interested in putting together a procedure around tracking requests for project extensions. We'd like to do this in order to understand why our project end dates slip and potentially even add in an 'approval' step at some point. We are looking into potentially using Project Issues with a Category of "Extension Request" but have noticed that the Categories seem to be pretty much free-form from project to project and we're looking to standardize project issues Categories over all projects in our portfolios. We have also briefly considered adding a Project Attribute but we aren't sure yet how that will work.
I'm open to any advice on this. Has your organization implemented a way to track project extensions? TIA!
Answer (1)
Hello Erin,
You *can* specify sort of out-of-the-box Issue categories in a project template, which is then applied to a project on its outset. Those can be the full list of needed issue categories that you anticipate would be needed on any given project. Then just advise PMs not to create other categories on their projects.
I have very much heard of these sorts of things being tracked as Project Issue items though.
You could also track them as a Ticket in the ITSM system (like a Change ticket or Problem ticket), and link them to the project by converting the ticket into a task on one of the project's plan(s).