The Importance of Waterfall in Agile

The name came from the third diagram in the problem statement of misunderstandings about software. People took that, went with it, and it got the name waterfall. Waterfall was originally called top down programming. It's a metaphor where I read a book about constraining metaphors because they help us to see something differently. And you were talking about the what I took away from what we're all saying on this episode is there's a peril in writing things down but there's an opportunity for success.