October 2013
Intermediate to advanced
224 pages
7h 58m
English
Here are a couple of quick reasons why waterfall thinking still lingers. First, it can be difficult trying to break work down into smaller chunks so that something of value can be coded, tested, and have the associated product documentation completed within an iteration. We’ve been conditioned for years to think in terms of completing big chunks of stuff. (“I can’t start on the GUI until the back-end code is complete!”) In addition, because the various disciplines don’t have a history of actually working together on an on-going basis, it can be tough to break the mindset of completing just your stuff. (“I got my code done; time to move on to something else while Test does their thing.”) We tend to think ...
Read now
Unlock full access