Do you read the manual?
Let’s face it: when you unwrap a new product, chances are you won’t read the manual. Manuals aren’t read because people just want to start using the product. And besides, the product should be easy enough to use without a manual. When it comes to software development, documentation is like the manual. No one wants to read through reams of specifications; they want to start doing. Enter the user story.
What’s the story?
A user story is the fuel of an agile project. It is the requirement against which code is written and the project planned. Unlike the requirements documentation you may have seen in the past, a user story is very simple: a title and a sentence or two of plain English to describe it. Most importantly, ...