As we convert from a informal undocumented environment to a formal documented one (as part of a process redesign effort, PMO will be in use), we need a structured way to name projects. We'll have over 500 projects going on at the same time once implemented. Has anyone come up with a successful naming convention for Projects? Saving Changes...
How about plain English, assuming that is the language in which you operate? Saving Changes...
Anonymous
There's a lot in a name.
First there's addressing the production naming convention, and then there is addressing a project code name. Code names define a project that is in progress and yields no release connotation. Release naming convention depends on your business model. A baseline release w/ a name is usually a good idea, and subsequent appendages denoting specifities.
I'm in a similiar predicament and look forward to some "good ideas" in this area! Saving Changes...
Anonymous
In the past, a telecom co. used a naming convention that identified both the program, project and the hardware platform. In addition, letters depicted whether the hardware was test, development or production. For example, a Long Distance program would be LD and supported a dept in Texas (TX) and it might be used for accounts payable? (whatever) the ending name convention might be LDTXAPD01. Noting the above mentioned plus the project number. This worked as an enterprise solution. I wonder, if there is a best practice survey for project naming conventions out there? Saving Changes...
