Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Business Analysis/Requirements Management, Scrum
What do you consider as the biggest benefit while working with user stories?

What do you consider as the biggest benefit while working with user stories? Planning, communication, easy to understand by all sides, ..?
Sort By:

They encourage having "real" conversations with users about their needs & wants

Stories provide context that can be lost in more detailed requirements. Even when writing BRD's in the past, I generally recommend that regardless, a short line for 'rationale' helps provide context and a link to the business need/value/etc. It's vital that context remains with the need.

I think it helps to align project team to gain a common understanding on what needs to be built and how.

Kiron's definition is succinct and hits the nail on the head

I agree with Kiron and Andrew's comments. They can help the user conceptualise/rationalise the requirement and weed out generic requirements that other little to no value.

None. Benefit is defined as something "extra", something that offers and advantage. User Stories is a wasted of time, no matter I am using it before it was callend "User Stoties". But, the quesion is, why to use them? As any other type of things, it must be used if and only if after an analysis is the best way to take needs/wishes/desires/wants/ etc from stakeholders to transform them into requirements.

I feel the greatest benefit of user stories is team members are able to foster direct and regular communication and mutual understanding with end users. With that, team members are able to understand the users' perspectives, difficulties, and opportunities that need to be addressed. This entails strengthening of relationship and delivering value propositions to customers.

On the other hand, as the same task is performed by the team member(s) in conjunction with the end user(s), it is necessary to consider individual's pace, task's workload, and team culture. This will ensure healthy collaboration and minimize discrepancies resulting from the diversity of team and end users.

thank you for your answers. User stories are good for communication, understanding, but I have sometimes issue that they do not provide complete picture, may be focused only on one side of the problem and then there is this "devil hidden in details". How do you cope with that?

Please login or join to reply

Content ID:

One man can be a crucial ingredient on a team, but one man cannot make a team.

- Kareem Abdul-Jabbar