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:
What If ...
Get The Agile Samurai now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
