Project Naming Convention

Owned by Mojgan Amini
Last updated: Mar 29, 2022
1 min read

General Guidelines (for project long name a.k.a. project summary in Jira)

  • Use functions and not technology/product name, add tech/product name only if it is a prominent part of project, i.e. Student Admissions Slate

  • Use technology/product name only if project intent is solely dependent on that technology, i.e. upgrade of the technology, i.e. Microsoft Exchange Server upgrade v67

  • Expand name and include acronym, i.e. ESR Strategic Organizational Change Management (SOCM)

  • Prefix projects with the program name, i.e. ESR Student Information Systems (SIS), ESR Enterprise Identity Management (EIM), etc. 

  • If project is split up across workstreams and being managed in separate spaces, use the same project name but qualify by appending the specific work, i.e. ESR SIS Reporting, ESR SIS Downstream Remediation, etc.

  • If separate releases or versions are managed in separate projects, use same project name but qualify by appending version/release number, i.e. HR Recruitment HireOnline v2.0

  • Prefix internal department initiatives with ITS, i.e. ITS Service Owner Handbook, ITS Torrey Pines Center South Renovation and Move, etc.