How much is Just Enough Documentation?
Johanna Rothman writes "Sure, we can start defining requirements. And we should spend as little time as possible, and make that definition as low fidelity as possible as long as the fidelity is appropriate for your project's context. So if you're developing a product that doesn't have human life implication, timeboxing requirements, paper prototypes, storyboards, informal use cases and other fast and low fidelity techniques are suitable." Granted, some product managers try to get by with a requirement on a cocktail napkin. Yet many product managers spend too much time trying to get the requirements acceptable to development--as if developers were assembly line workers without the ability to reason. Too much time spent writing the Market Requirements Document leaves too little time to interview clients--to understand the needs for the next product or release. The MRD can only give guidelines for developing products but never truly defines the final result. Starting from the requirements, our developers add some code, some experience, and some creativity--little of which is specified in the MRD. Are you writing Just Enough Documentation? "Just enough" is adequate communication but not so much that nobody reads it.
Looking for the latest in product and data science? Get our articles, webinars and podcasts.