Agile Learning

Winston Royce first drew what we now call the waterfall model in 1970

He didn’t draw it as an example of how we should develop software – but as an example of how not to do software development.

I believe in this concept, but the implementation described above is risky and invites failure.

—Winston Royce

Winston goes on to point out that it's not until further downstream when we test working software that we really see problems - the sorts of problems that cause us to go all the way back to requirements

Cleverly built into a waterfall process are a variety of scapegoating mechanisms that allow us to blame other people, or outside influences for failure. Given that important value of demonstrating personal competence, and keeping me personally safe, a waterfall process seems like an ideal process choice.

Agile folks don't believe they can effectively predict the future, or estimate development time

Be sensitive to culture shock

In particular, people who've spend a great number of years working in software development may be feeling something they haven't felt for many years – uncomfortable doing their own jobs. They may feel like someone has drugged them, put them on an airplane, and dropped them off on a foreign country without their consent. They may have incorrectly assumed they were just learning a new process.