| Exploring Solution Spaces © Copyright 2003-2006, by C. Keith Ray | ||||||||||||||||||||||||
|
Archives
Subscribe |
2008.Jan.27 Sun
Making a Waterfall Project Succeed
Many moths ago, I read an informative and often amusing book called It Sounded Good When We Started: A Project Manager's Guide to Working with People on Projects by Roy O'Bryan and Dwayne Phillips about (among other things) a waterfall hardware/software project whose management got disconnected from reality and the author had to take over project management to get the project back on track. Many of the techniques he used (putting the project plan on the wall as a frequently-updated information radiator, low-overhead daily updating of current and near-future planned tasks, avoiding delays between engineering activities and quality assurance activities) are also used in Agile projects. I think of Agile development methods as including lightweight ways of incorporating feedback into the process. It turns out making a Waterfall project successful requires the same thing: frequent, timely feedback. Step Into Your Agile Groove With Industrial Logic’s Greatest Hits |
|||||||||||||||||||||||