11/4    What's the purpose of having codenames for projects?  To me, it's just
        yet another piece of info per project that I need to remember.
        \_ To facillitate communication across departments.
           \_ Why not use the real name of the product?
              \_ Because you get version number differences, branched products,
                 etc.  Not every dev team requires codenames, but it's a common
                 thing to do just to keep everyone on the same page.
                 \_ Also, it depends on how you define "project". If it's a
                    product, it will have a name, but that name may change or
                    be unwieldy to use on a regular basis. If it's a version,
                    the business types could change the version name at any time
                    to support sales or marketing. If it's a set of features, it
                    may not have a well-defined short name, and "the code that
                    does all that new stuff" isn't terribly descriptive. -gm
              \_ 1) project hasn't been named yet
                 2) project name is long and unwieldy
                 3) it's just a version change and maybe saying you're working
                    on "5.8.7" is annoying
                 Those are just off the top of my head --dbushong
                 \_ Project version number changes at last-minute.
                 \_ You can't say the full name of the project without laughing
              \_ They're more fun
                 \_ Just ask Butt-Head Astronomer.  -tom