By mitchp
via agile.dzone.com
Published: Dec 26 2012 / 10:14
I needed to fail with modern methods for requirement gathering in order to understand old methods for requirements gathering. Many software projects write requirements in what is refered to as “user stories”. But a use story is not a story at all. There’s no drama, no action and no resolution. Instead, user stories are often just a bunch of interactions between the user and the system laying in a big heap in a shoe box. Or even worse: In an issue tracking system. Using the form of use cases, a requirement form that had failed me in the past, I have reinserted the drama into my projects.
-
Javascript URL Object
-
ASP.NET FriendlyUrls ViewSwitcher and jQuery Mobile
-
Stumbling Into the Cold Expanse of Real Programming
-
Spring Framework 4.0 Milestone 1 Now Available
-
Introducing My Cloud Deployment Service, OnCheckin.com - Diary Of A Ninja
-
Join Microsoft on the 20th of June 2013 to learn about Windows Azure in Education
Add your comment
