In the my Previous blog I talked about a metaphor to illustrate requirements evolving from a 1-liner, to a paragraph, to a 1-pager, and then to multiple pages. In the process of building systems using agile approaches many teams have forgotten, or worse have never known how to document details around requirements. There's that pesky agile value - "working software over comprehensive documentation." Too many teams take this to mean we no longer have to write anything down. Not so fast cowboys.
Monday, October 20, 2014
Wednesday, October 8, 2014
Why have we forgotten about requirements analysis in our agile world?
As I coach teams, inevitably the discussion about requirements comes up. Some of the things I've heard from team members:
- We don't write any requirements
- A user story is all we need for requirements
- We don't have time to write requirements, we just talk with our Product Owner
- Since we don't write requirements, we just figure out the features on our own and show the completed work to our product owner
- ...
When I think of requirements, I think about who consumes them and the value that the consumers get from them. Many teams have lost their way when it comes to agile requirements and requirements related artifacts.
Subscribe to:
Posts (Atom)