The hardest single part of building a software system is deciding precisely what to build.
|--Frederick Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering”|
“I understand the requirements, but what does it actually do?” is a question often asked by systems analysts, business analysts, product managers, and programmers when confronted by two hundred pages of traditional IEEE-standard-style “The system shall . . .” functional requirements. After reading these convoluted documents, many of us have often gone back to the customers and pleaded, “What do you want this system to do? Tell me a story about how you are going to use this system.”
People like stories, and from ...