Choosing project code names

From an eWeek article: MS has chosen "Hawaii" as the code name for a future Visual Studio release "because the team plans to celebrate redesigning the IDE (integrated development environment) in Hawaii".

Now THAT is a brilliant bit of project planning. Code name your releases after beautiful vacation destinations and convince management to have the release celebration party there. I've already started lining up code names for our future products - Tahiti, Bali, Venice, Paris, Fiji...


5 Comments

  • Does make you wonder what they were thinking with the Visual Web Developer 2005 codename...Venus...

  • better yet, code name them places you have to go if you miss the shipdate, i.e.



    - Tulsa

    - Kansas City

    - Sacremento

    - Charlotte (my hometown)



    That would *definitely* help out w/ slipping ship dates IMO :-).

  • Kevin:

    I have come to the conclusion that odd project names are the best (I am mostly thinking open source projects here). If you are using the open source software, you will spend much of your life searching on Google, so you don't want to get lots of excess/unrelated info. So, the more obscure, the better :).

    Enjoy,

    RB

  • Our project can't afford trips for releases so we're naming the releases after restaraunts we can go for the celebration. Of course if we miss the ship dates we can do the same thing except the names will be The Wendy's Release or Jack in the Box Release.

  • Can I be part of the Hooters release?

Comments have been disabled for this content.