Publications

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.

Use cases have been around for almost 30 years as a requirements approach and have been part of the inspiration for more-recent techniques such as user stories. Now the inspiration has flown in the other direction. Use-Case 2.0 is the new generation of use-case-driven development—light, agile, and lean—inspired by user stories and the agile methodologies Scrum and Kanban. Use-Case 2.0 has all the popular values from the past—not just supporting requirements, but also architecture, design, test, and user experience—and it is instrumental in business modeling and software reuse.

In this article I base my observations and opinions on my experience of applying the Use Case 2.0 Practice and Behavior Driven Development’s Gherkin language, within an online products division of a major US Bank that is undergoing an Agile transformation. “I’m not dead yet,” Is a classic line from the movies that Monty Python fans will instantly recognize. I start with this because I could win a lot of money betting on the response from Agile practitioners when I tell them I am using Use Cases in an Agile environment to great benefit. “Use Cases? They’re dead and buried!” “That’s RUP! (Rational Unified Process). They aren’t agile.” “What are you thinking? Use Cases are dinosaurs.” “You should know better, Bernie.” Rarely, I get a response from an experienced coach who will not poke fun, but seek the powerful questions such as, “Now why do you think that’s a good idea?”, and a valuable conversation ensues.

IJI helps Dutch Ministry introduce lean, lightweight and agile development approach - program team becomes self-sufficient in new way of working within six months.

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.

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.

KPN gains traction and hits targets with new measurement framework implemented with IJI.

Agile and lean ways of working adopted in a development organization spread across multiple time zones - highly adaptable way of working provides "just right" level of support for projects with diverse needs and varied risk profiles.