Enhancing Scaled Agility with Use Case 2.0 and BDD Gherkin
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.
- Better support for Agile programs by supplying development teams with the right amount of work at the right time
- Delivering more value to the business faster as the development team began to specify realistic specifications
- Waste was reduced as better feedback from the business and users was incorporated in a timely fashion