Good morning!
I have a question about setup a correct name to every project.
In absence of Organizational Process Assets clearly defined about this topic, I would like to know how do you assign acronyms to projects to recognize and store them.
Today I'm dealing with projects regarding different topics and different companies, and I really need a tool to standardize this meltin' pot.
Requirements:
- Automatically order projects (e.g. inside a root folder), for example by start date
- Understand project topics without open the Project Charter.
(Usually I apply the same name to Outlook folders)
I thought about something like:
TTTYYMM_XXX - brief description
Where:
TTT - initials of company name
YYMM - starting date, year and month
_XXX - Initial of project description.
(For example, a new warehouse feasibility study could be WFS, a East Europe scenario analysis could be ESA, etc)
Furthermore, I'm doubtful whether it's better to create - to say - 10 different topics to standardize the kind of projects and then specify the exact project only in the description.
e.g every BPR (business process reengeneering) has the same intials:
COM1603_BPR - Inventory policy
What do you think about pro and cons to use this names? What are your current strategies in naming projects?
Thank you in advance for your time,
Best regards
Francesco Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
What I will say trying to add something is that you have the project name and the project ID, the last one is what you stated above. The project name is critical because all people have to remember it and will help you in stakeholders engagement. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I personally name the projects as follows:
Company Initials - Project Initials - Project Country - Project No. - Project Year
For example:
A project in Canada for XXX Company and the project is about building a high rise in downtown and the high rise name would be YYY:
XXX - YYY - CAN - 0001 - 2016
In correspondence, I use the XXX - YYY only but for any other official matters, like documentation, I use the whole name.
Hope this helps. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
People, sorry, but I have to insist on this. The name of a project is the same of a name of a product. And that is because we need to sell the project in some way. So, you need to assign a name following the rules for any product in the market. On the other side, I fully agree with you that the project ID or code will be diferent.
...
2 replies by Markus Kopko and monica leal
Mar 23, 2016 4:54 AM
Markus Kopko
...
Hey Guys,
i have to second Sergio here.
The OP is not really about project name but it is more about administrative things and ordering and how to name related project folders and documents.
So, the initial disussion question/title is somekind missguiding ...
Regards,
Markus
PS: Regarding how to name project folders/documents we follow a same approach like you suggested or like Rami mentioned. You just need to figure out what works best for you and your colleagues.
Jun 14, 2016 9:43 AM
monica leal
...
I use the ID of the Strategy Map BSC and sequence the portfolio , followed by the short name of the project , which may be an acronym or name " fantasy " and sequence an acronym for the document type. The names of our projects are large and start with a verb in the infinitive . For files and for use in media, the "fantasy" name is intended to reduce the name and make it closer to a product ( a marketing vision) .
Saving Changes...
Tata RahulBusiness Analyst / Project Manager| Ace Manufacturing System LtdBengaluru, Karnataka, India
Everyone has their own methodologies for naming.
In my personal opinion and what we practice, following things should be considered while naming:
1. The project name should be unique in the organization in order to avoid duplicates.
2. The project name should not be long as its quite difficult to accommodate the name.
3. Last and most important the project name should have emotional touch and at the same time as per company's existing culture.
Why I have said the last point as important is that we have to remember that project can only be successful if we have buy-in from all stakeholder (for bigger organization restricted to project team), and the best way to get buy-in is to get them involved from the very important process of naming.
In our organization, we usually keep an competition and the best one is rewarded.
Also I have seen one more advantage is that, people take pride calling themselves part of the project.
Naming is the first stone and it should be decided very carefully and most important it has to be attuned with the company's culture. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Mar 22, 2016 1:14 PM
Replying to Sergio Luis Conte
...
People, sorry, but I have to insist on this. The name of a project is the same of a name of a product. And that is because we need to sell the project in some way. So, you need to assign a name following the rules for any product in the market. On the other side, I fully agree with you that the project ID or code will be diferent.
Hey Guys,
i have to second Sergio here.
The OP is not really about project name but it is more about administrative things and ordering and how to name related project folders and documents.
So, the initial disussion question/title is somekind missguiding ...
Regards,
Markus
PS: Regarding how to name project folders/documents we follow a same approach like you suggested or like Rami mentioned. You just need to figure out what works best for you and your colleagues. Saving Changes...
I understand Markus and Sergio's point, no doubt you have to start with a project ID.
My question is actually for everything-administrative-following practicies, and I wonder which are yours and the reason of your choices.
Personally, I alredy started to rename all previous projects (keeping the original ID) and half the way I came back to the original naming because new aspects I did not previously get.
Do you have any other tips for this topic? Thank you!
Francesco Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Francesco (like Totti. Sorry, I am living in Argentina and everything is about futbol for me (hehehehe)-Hope the reference do not bother you). I will write about my personal experience where, because I was directly involved into process definition, I have created the project ID nomenclature lot of times. 1-I tried to create a code that was self-descriptive. I mean, when somebody see it easily detect some projects attributes. After made this from years I have to say it has no sence. People remember the project using the project name. 2-About your ID style I can say nothing. It could be as good as it helps you to identify the project at first sight. 3-What I really do and help me a lot is to thing a nomenclature for project deliverables (sorry because is not your question). Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I agree with the fact that the name of the project should reflect the name of the product and so does the initials. This is how we used to name out projects for example when I worked in Oil and Gas, we used to call Gas to Liquid Projects: GTL Project and so on. Saving Changes...
monica lealPMO Manager | ATI Recife, Pernambuco, Brazil
Mar 22, 2016 1:14 PM
Replying to Sergio Luis Conte
...
People, sorry, but I have to insist on this. The name of a project is the same of a name of a product. And that is because we need to sell the project in some way. So, you need to assign a name following the rules for any product in the market. On the other side, I fully agree with you that the project ID or code will be diferent.
I use the ID of the Strategy Map BSC and sequence the portfolio , followed by the short name of the project , which may be an acronym or name " fantasy " and sequence an acronym for the document type. The names of our projects are large and start with a verb in the infinitive . For files and for use in media, the "fantasy" name is intended to reduce the name and make it closer to a product ( a marketing vision) . Saving Changes...
You can use 'Clarity' for managing projects. A unique ID will be automatically added to the project name, and like others suggested you can keep the project name to reflect the name of the product or service. Saving Changes...
Community Champion
