Archiving Projects
- Erin Kilburn
Standards and procedures for closing a project in ITS-Pro (Jira). These steps are completed by the PPMO.
Notification received that project should be closed
Deleting all Kanban and scrum boards specific to the project (only if in use on that single project)
Deleting all dashboards specific to the project (only if in use on that single project)
Deleting all Jira plans specific to the project (only if in use on that single project)
Moving any associated Smartsheets to archive (only if in use on that single project)
Deleting any Jira Structures (only if in use on that single project)
Closing any open issues
Changing permissions to archive (means people can browse, but not add new issues)
Change project category to archive
Prefixing project name with “⠀[ARCHIVED]”
Updating project record to reflect updated status to Closed with appropriate resolution (Done, Incomplete, Duplicate), project end and go live dates, and any other updates
Resolution definitions
Done
Project scope achieved, hypercare exit criteria met, any necessary or remaining work transitioned to operational workstreams
Incomplete
Project scope not achieved, due to resourcing, other priorities, or technical limitations, and subsequent decision to close the project
Duplicate
Project created in error, or project consolidated into another
Won’t do
Decision made to not proceed with the project