Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Questions tagged [user-stories]

User stories are used with Agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management. It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard

12
votes
3answers
3k views

In our Agile/Scrum team, should we move or split incomplete stories?

Our Agile/Scrum teams are getting better at taking on manageable workload and completing them fully. However, sometimes for a variety of good reasons, some of the stories are not fully done at the end ...
12
votes
6answers
653 views

Why use iterations in Scrum?

I am a Scrum Master in a 7 person team. We currently use one-week iterations for our sprints. I find that sprint planning overhead is huge (2 hours each week for entire team), and not nearly as ...
6
votes
3answers
2k views

Changing backlog story point estimates mid way through a release

Background: We are mid-way through a development which was estimated for a customer on a fixed price contract. To come up with the estimate we built a backlog by trying to list all user stories and ...
9
votes
4answers
2k views

Sizing an entire backlog using story points

I'm a PM on a large multi-year project with a sizable backlog of work implementing Scrum in 4 week release cycles. I hold weekly backlog grooming sessions with the project team and key business ...
8
votes
2answers
1k views

Develop from Use Cases or Business Requirements

I'm involved in a project where the business team created a large business requirements document that were using to create product backlog items and acceptance criteria. However, they have also ...
5
votes
2answers
201 views

Handling new suggestions to resolved user stories in closed sprint

In a project managed using scrum framework, I've a situation where all tasks associated to a user story (feature) had been done successfully. No more code changes are allowed since testing is in ...
10
votes
4answers
927 views

Improve performance of feature X - should that be a new user story or something else?

We have implemented and closed user story X but found out later that the implementation is too slow and we need to improve performance. I think it was a mistake not to have acceptance criteria for ...
2
votes
3answers
373 views

Learning curve to writing user stories in the real world

How many user stories does it roughly take before a product owner has a basic fluency in writing user stories? Meaning that the idea of writing user stories has moved beyond theory, rough execution, ...
4
votes
1answer
167 views

how to cover details (side effect not desired workflow) with scrum user stories

As a scrum/agile system student, i am finding very hard the situation where you have to write up a user story in the clasical form and at the same time, describe the behaviour of parallel workflow. As ...
10
votes
3answers
2k views

Is there a difference between use case and user stories?

Is there any difference between use case and user stories? Or are these totally different terms in the context of agile planning?
3
votes
3answers
3k views

Agile Scrum Storyboards

At the moment I'm Scrum Master for my place of work. We have one Scrum Team in our organisation which is split across two sites: Site 1: Scrum Master, Developer, QA Site 2: Developer, Operational, ...
5
votes
2answers
287 views

How do you refactor a story?

We've been using Pivotal Tracker on a software library project for well over a year. I'm the (admittedly not great) PM. The team is very good about writing notes on the story cards as things ...
10
votes
3answers
776 views

What are the best practices/methods/tools/techniques for conflict identification in requirements?

For the sake of this discussion requirements = user-stories (since I'm not differentiating any process per se and would like to get rid of any ambiguities). It's quite common to have a set of about ...
5
votes
2answers
1k views

What is a reasonable strategy for estimating story points for new stories?

The project I'm running is very exploratative in that I don't know very much detail about features in advance. My boss will tell me that he wants feature A and that after feature A is finished, he'll ...
6
votes
4answers
487 views

Creating “User Stories” without a user

[University Project] I want to adopt as many practices from agile project management as I can for a university project. I've decided that the actual development approach will be based upon an FDD (...
1
vote
1answer
346 views

using the prototype for live when building CMS/CRUD systems - wrong? [closed]

I'm currently reading Steve McConnells "Survival Guide" and am thinking of how I can improve our processes on requirements development. The book seems to have very strong ideas about using prototypes ...
4
votes
4answers
6k views

When should you do sprint planning?

We tend to do our retrospective on the final day of the sprint and have found that by the end of an hour and a half, launching into a planning session is not ideal at all. When do you hold your ...
38
votes
14answers
18k views

Should bugs be treated as stories or as tasks?

If you're using scrum you should know that there is a clear difference between tasks and stories. A story is something that is valuable to user. A task is a step to produce that value to user. So, ...