naming conventions for projects?

[anovak]

Anyone out there dealt with specific naming conventions? Some folks
here want to prefix the project name with a 10-digit code; however,
the built-in meaning in some of the digits duplicate attributes
already available at the project level.

My take is that strict naming conventions aren't necessarily that
beneficial other than ensuring that you aren't trying to create a
project that already exists. On the other hand, one would think that
could be solved rather easily by using more key words that tie back to
the application name, etc.

To me, the PMs may fully understand that that long code means, but all
the stakeholders do not. I've proposed that this 10-digit code be
split out into a custom field called ProjectID so that one can sort
both on the code and on the project name.

Any and all comments, recommendations, and opinions would be greatly
appreciated.

Andy Novak
UNT

 

[Jack Dahlgren]

Sure. Naming conventions should be understandable and useful. You are right
that the use of outline codes or ID's is a great way to categorize or sort
projects. PWA can group and filter on any of these sorts of things so if you
are using Project Server then there is little reason for a 10 digit code at
the start of the project name. The project name should have enough
information to discriminate it from the other projects in a list. In most
cases a short project number and or name is good enough. But it all depends
on the situation.

If people don't know whether a project schedule exists or not then you have
a bigger problem than a naming convention.

-Jack Dahlgren

 

[Studer]

For quite some time I've been dealing with a 4 numbers + 4 letters name for
projects (ex: 1567SWHW). The 4 numbers allow you sort the projects by
contract date and the 4 letters help you easily identify the project.

 

[Ueli]

Andy,

Consider that the name-field might automatically appear on printouts, so it
it could make sense to make it human-readable. We use the following scheme:
nnnn Cccc Project Name
where 'nnnn' is the project number, 'Cccc' the customer's name (or it's
abbreviation) and 'Project Name' the full name or the generally used
abbreviation. Example: 0499 Vivo GEND v2

For sorting and filtering we use custom enterprise fields, as already
suggested by the colleagues.

Hope that helps.

 

[Dale Howard [MVP]]

Andy --

I would vote in favor of a naming convention that helps your stakeholders to
understand the projects they see in the Project Center page in PWA. This
means the naming convention for projects should be simple and direct. Given
the fact that the 10 digit code confuses some of your stakeholders, I would
drop it from the naming convention. For your PMs, I would create a custom
Project Center view that applies grouping on the custom enterprise Project
fields that include those 10 digit numbers. Hope this helps.

 

[Gary L. Chefetz [MVP]]

Andy:

Sometimes it's more important to understand what makes the name familiar and
comfortable for the user than worry about redundant information. In many
pharmaceutical and biotech companies I've worked on, for instance, I've
found that often users really know their projects by their code numbers. If
this is the language that the organization speaks, you should try to
accommodate it.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[anovak]

Andy:

Sometimes it's more important to understand what makes the name familiar and
comfortable for the user than worry about redundant information. In many
pharmaceutical and biotech companies I've worked on, for instance, I've
found that often users really know their projects by their code numbers. If
this is the language that the organization speaks, you should try to
accommodate it.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com

I hear you Gary. The problem is this code is familiar with the
development team, but completely unfamiliar with all the other
stakeholders, including executives.

I just don't understand why it can't just be placed in a custom field.

Best,
Andy

 

[Gary L. Chefetz [MVP]]

Andy:

Clearly it could, but choose your battles wisely my friend.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[anovak]

Andy:

Clearly it could, but choose your battles wisely my friend.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com

I hear you Gary.