Five Simple Rules for Project Names, plus Four Sample Lists
A recent post by Jeff Atwood about project names brought back memories of a previous employer, and the project naming convention we set up in our PMO. At this company, the IT group spawned maybe 30 to 50 chunks of work we would call "projects" - at least two calendar weeks in duration (anything smaller than that was just a programming request, and given a control number). Like any good PMO, we generated charters, mission statements, requirements, process maps, status…