I wrote an article about this many years ago, but I always recommend giving projects an inspirational name tied to the purpose of why we are doing the project as opposed to what or how the project is being done.
So rather than call it "Implement HR System XYZ", you could say "Improve employee engagement".
Think of the project name as the very first elevator pitch for your project...
Kiron Saving Changes...
Adela TataruSenior Project Manager| Self EmployedVancouver, British Columbia, Canada
A project should be have a clear name that conveys in some form the purpose of the project.
Usually it is also an inspiring, memorable and unique name.
For example:
- PowerTalent (the system implements an HRIS tool that empowers the company talents)
- WorkForce (same for HRIS)
- Star Client (for CRM projects where the client is at the center of the system)
- XData (reading as cross data for data management projects) etc
I have seen companies also giving projects the name of their own products to empower the idea of the importance of the project and the impact it has on the enterprise. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I agree with @Kiron. The name is one of the keys of project success. What we do is: Select a short name. Something that everybody can remember easily. In our case we add 3-4 letters that identifies the scope in terms of the region scope. Saving Changes...
I also agree that identity is important. For IT software I would always suggest naming the product, not the project. It's often the case that the bulk of software development happens outside the remit of a formal project. The product is what attention should focus on and the development team will benefit from having a unifying identity even when they aren't developing the software as part of a project. Saving Changes...
