Software project survival guide

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

You really think that the only thing you need to produce a shrink wrapped game that is in production for 2 years is someone to code and someone to take care of art and design? And you really don't understand why I would say that project management on that project is very different than project management on a website that delivers incremental revisions every week? Sorry, but you clearly have some things to learn. Go pick up http://www.amazon.com/Software-Project-Survival-Guide-Practi... and learn what a stand alone project on the scale of that game needs to do just to have a reasonable chance of success. Virtually none of that book applies to the incrementally developed website. Oh, and don't forget that the game has no chance of success without a lot of non-software work such as licensing and marketing.

How to price a project. Hmmmm. As a project strategist-manager, recommend the books Software Estimation: Demystifying the Black Art (2006) and Software Project Survival Guide (1998). Used the SPSG templates as the basis of my pricing process. SPSG book is one of the few books that still sits in my bookshelf