Documentation should meet outcomes too

How do we go beyond seeing documentation as a burden and ensure that it is maintainable, reliable and valuable? Documentation is necessary to explain how something complicated works and defines a critical process to ensure a successful software release.

Architecting Software for Extremely Fast Feedback-Loops part 1

When we deliver software, we need to ensure it meets the needs of end-users. The slowest feedback-loop is a “big-bang” release – this is essentially shipping all the features at once after developing for weeks, months or even years. We know this to lead to failure far more often than not… Yet, many teams release software this way, and no we don’t recommend it.