Contact

Blog

Use Cases are the Hub of the Software Development Lifecycle

Since their inception some 30 years ago, use cases have been used to identify, organize, synthesize and clarify system requirements for organizations across the globe. In most recent years, they have been used in techniques such as user stories. Use-Case 2.0 is the new generation of use-case driven development – light, agile and lean – inspired by user stories, Scrum and Kanban. Although they are much more agile and lean, they still embody the same popular values from the past while expanding to architecture, design, test, user experience, and also instrumental in business modeling and software reuse. But, for the adoption of use cases to be seamless, there should be a balance of principles applied.

Features or Use Cases for Agile Development?

In this first of a new series of blog articles, author Roly Stimson discusses how Use-Case slices are a simple but powerful technique to identify and prioritize small increments of releasable value and how these can be split (if and when needed) into smaller items that you can independently prioritize, schedule, build, test and demonstrate.

Agile Features and Use Cases for software development

In this first of a new series of blog articles, author Roly Stimson discusses how Use-Case slices are a simple but powerful technique to identify and prioritize small increments of releasable value and how these can be split (if and when needed) into smaller items that you can independently prioritize, schedule, build, test and demonstrate.

Use Case 2.0 and Agile Software development - Ivar Jacobson

Use-Case adoption is growing again: In this interview 'Use Cases and its role in Agile Software Development' by Blueprint Systems, Dr. Ivar Jacobson explains how Use-Case 2.0 includes everything important about user stories, but offer significantly more for larger systems, larger teams, and more complex and demanding development projects than user stories alone. They are as lightweight as user stories but can also scale in a smooth and structured way to incorporate as much detail as needed. Most importantly, they drive and connect many other aspects of software development.

Using Use Cases and Scrum Together

In the second of this Use Cases in Practice series of blog articles, author Roly Stimson discusses how a use case model provides a simple, big, visible picture that provides critical value context, which represents a powerful tool that can be used as part of Scrum sprint reviews to ensure that the team and the stakeholders reflect meaningfully on what has been achieved in the context of the overall solution goals and value, and adjust future work objectives, priorities and plans accordingly.

Contact Us