How User Stories are Different from Requirements

How User Stories are Different from Requirements

How User Stories are Different from Requirements

This post is a part of a series:Everything You Ever Wanted to Know About User Stories But Were Afraid To Ask

I was packing up my things, ready to leave after a long week of training.  Susan, the lead business analyst, had been dutifully attentive all week.  She took excellent notes, asked probing questions, and seemed to be integrating the new knowledge smoothly.

“Hey Tirrell, I have a question for you…”

“So exactly how are user stories different from requirements?”

You get the idea.  One problem with documenting requirements this way is that its very very tedious and time consuming.  Another problem is that its boring to do, and even more boring to read, which is why long detailed requirements documentationrarely gets read.  Lastly, because requirements are written at such a granular level, its difficult to understand the big picture.

Traditional requirements are created from the perspective of the system and its associated activities.  Problems with interpretation of these activities lead to pain and missed deadlines because they tend to be interpreted as edicts rather than points of discovery.  In other words, they tend to over specify.  This leads us to a situation where highly paid intelligent engineers don’t get the opportunity to solve user’s problems, they are stuck implementing a sub optimal solution.

Read Also:
3 Steps to Align Culture With Business Strategy

Unlike traditional requirements, user stories tell is what the user is attempting to achieve.  This is important because it gives context to how we view the requirements.  Since there are multiple ways to help a user accomplish the goal, it ensures the solution meets the goal (or the problem the user is trying to solve).

 



Data Science Congress 2017

5
Jun
2017
Data Science Congress 2017

20% off with code 7wdata_DSC2017

Read Also:
The Titanic Teaches us About Data Assets and Reflexivity

AI Paris

6
Jun
2017
AI Paris

20% off with code AIP17-7WDATA-20

Read Also:
Should the BI Scrum Master report to the team or the PMO?

Chief Data Officer Summit San Francisco

7
Jun
2017
Chief Data Officer Summit San Francisco

$200 off with code DATA200

Read Also:
What Marketers Need to Understand About Augmented Reality

Customer Analytics Innovation Summit Chicago

7
Jun
2017
Customer Analytics Innovation Summit Chicago

$200 off with code DATA200

Read Also:
3 Steps to Align Culture With Business Strategy
Read Also:
Why financial firms are missing out by not embracing the cloud

HR & Workforce Analytics Innovation Summit 2017 London

12
Jun
2017
HR & Workforce Analytics Innovation Summit 2017 London

$200 off with code DATA200

Read Also:
Digital disrupts traditional outsourcing market in 2016

Leave a Reply

Your email address will not be published. Required fields are marked *