Use-Case 2.0, DevOps and Value
As we continue to pursue our strategies for DevOps and optimizing the value stream, along comes Ivar Jacobsen, Ian Spence and Brian Kerr with Use-Case 2.0!
The Use-Case is a very practical approach capturing requirements and much more. They also capture user experience, support test driven design and help in the application of architecture. The idea of a Use-Case is immediately recognizable. It is light weight and it scales.
The authors of Use-Case 2.0 underline six basic principals:
- Keep it simple by telling stories.
- Understand the big picture.
- Focus on Value,
- Build the system in slices.
- Deliver the system in increments.
- Adapt to meet the Teams needs.
Use-Cases are over 30 years old and their common reference by a broad cross functional group of professionals to communicate with peers and customers makes them anti-fragile. They'll be with us for another 30 years since they help us all but they are especially aligned with what W. Edward Deming mentions on page 50 of "The New Economics" "Management's Job is to optimize the whole."
Our DevOps journey is focused on the optimization of the whole and the Use-Case is our essential ally in the pursuit of "concept to cash" and value stream coordination. The Use-Case is a well defined practice, compatible with continuous integration. As a light weight and flexible tool that fits agile and lean practices, it also works popular management practices.
since as a