Comments on: Duke Nukem Forever: When Enough Is Not Enough http://victorcaveda.com/2010/01/24/duke-nukem-forever-when-enough-is-not-enough/ Slightly Geek Mon, 10 Oct 2011 03:36:05 +0000 hourly 1 http://wordpress.com/ By: caveda http://victorcaveda.com/2010/01/24/duke-nukem-forever-when-enough-is-not-enough/#comment-28 Tue, 26 Jan 2010 19:02:35 +0000 http://victorcaveda.com/?p=281#comment-28 In my opinion, the actual problem was the lack of two key things:

- Clear requirements.
- Deadlines.

If you don’t know what exactly you want to do and when it must be done, it’s easy to figure out what will be the outcome: nothing.

By the way, good article :)

]]> By: PM Hut http://victorcaveda.com/2010/01/24/duke-nukem-forever-when-enough-is-not-enough/#comment-27 Tue, 26 Jan 2010 04:06:18 +0000 http://victorcaveda.com/?p=281#comment-27 The development of this game is a perfect example on how Project Management can go horribly wrong.

Here’s an article that might perfectly well suit this project: The Whac-a-Mole Model of Bad Project Management: it has the 2 things this never to be released product has: a game and bad project management.

]]>