Adapt requirements (and your process) to your development approach! (41)

In most, perhaps even all, articles we’ve written in this series, development approaches are mentioned. Typically waterfall, V-model or iterative/incremental/agile. In this article I want to share some of my thoughts about requirements in relation to development approaches.

When organizations first started moving towards an agile way of development, the agile manifesto was embraced. The manifesto described 4, or 8 depending on how you look at it, values on how the new approach could be towards software development. One of the values, “working software over comprehensive documentation”, however frequently appears to be explained in a way that probably was never intended by the authors.