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...
Gautham NBAssistant General Manager| KGISL Business Support ServicesCoimbatore, Tamil Nadu, India
I believe that the project name should be fixed keeping the product in mind. Its better to have uniformity in naming projects within a organisation like every project should only be a 3 letter acronym and the same should be used for communicating with all stakeholders.
Its good to have all the stakeholders involved in the project from the very beginning and always open up a competition for naming the project and rewarding the best name. Saving Changes...
Christian VelazquezBARA Process Lead| Cadena de Descuento BARAMonterrey, Nuevo Leon, Mexico
In some cases for the confidential characteristics of the project we name it with a code name "Atlas" or "Atenas" etc. Saving Changes...
Barbara CarkenordPrincipal Consultant| Carkenord ConsultingHilton Head Island, Sc, United States
I think you are asking about naming a directory or file structure. Those things may have limits which require acronyms but the actual Product Name should describe the business value it provides. IT people love acronyms but business people do not. Give it a meaningful name like Track Customer Purchases, or Provide Financial Oversight. I like Tata's "emotional" aspect also. It should be very easy for anyone in the organization to understand! Saving Changes...
Elizabeth HarrinDirector| RebelsGuideToPM.comLondon, England, United Kingdom
Project names here tend to reflect the deliverable or business objective. Then they all have a 4-digit numeric code which is the shorthand, and is used for filing systems. The next project gets the next number in the list. Simple! Saving Changes...
AKSHAY JAINPlanning Group Leader| YOKOGAWA, BahrainGwalior, Mp, India
Normally depending upon business of your company and classification of projects a number is assign to project which itself explain lot about the project. Saving Changes...
Faisal PatelSVP; Strategy/Solution Manager; Accessibility Champion| Bank of AmericaWest Hills, Ca, United States
Just like a logical file name, I name my project logically:
Project Name Project ID and then every document will have the same format: Project Name Project ID - Document NameDate eg. PMI Assessment 1234 - Project Scope 02232023 Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
What is the purpose of a project name?
What is the purpose of your name? It gives you an identity, others something to recognize and remember you. It can relate to positive features and experiences. You also may have a government ID number, but nobody relates you to that.
Agree with Sergio and Markus, a name is needed to give your project (and the team) self-confidence, identity and pride. Don't just call it something like R2D2.
Also from a data model design view: data content (the name) should not be misused to structure the data. If you need organization, type, date etc to find and group projects, just add these as data fields.
In one of my projects, we had a long discussion to find a name, it was MAJA. It is also a female first name, and a bee as comic figure, so we had immediately a logo and mascot to identify with. Bees are always busy, nurturing and can be stingy when attacked, we agreed to these characteristics.
And - by the way - MAJA was the acronym for the long name of the project. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
