The Problem with Documentation

Heavy documentation as a means of capturing requirements has never really worked for software projects. Customers seldom get what they want. Teams seldom build what is needed. And vast amounts of time and energy are spent debating what was written, instead of doing what needs to be done.

Here are some other problems teams run into when they rely too heavily on documentation for their software requirements:

images/planning/userstories/theyCantHandeChange.jpg
images/planning/userstories/theyBuildAccordingToSpec.jpg
images/planning/userstories/theMakeBadGuesses.jpg

What If ...

Get The Agile Samurai now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.