97 votes
Accepted

What is the weighting difference between Epic/Story/Task

In Scrum here is the rough breakdown: Epic - something so big it probably won't fit into a sprint, is not clearly understood in terms of customer requirements and should be broken down into stories. ...
user avatar
  • 3,922
53 votes

What is the weighting difference between Epic/Story/Task

Epic An epic is like a super-story. When a story is too big to fit comfortably in a sprint and/or contains a lot of unknowns then it is usually better suited to be an epic. Epics are fine on the ...
user avatar
33 votes

How should a Scrum master handle disagreements about story-point estimates in Scrum?

With that much variation in the estimate, it seems like the work as it's currently defined is not ready for estimation yet. Based on that wide spread in estimates, I would say that the team doesn't ...
user avatar
  • 17k
23 votes

How should a Scrum master handle disagreements about story-point estimates in Scrum?

The first thing you should do is encourage the team to bring concrete arguments. "Things are more complicated than they seem" or "I dont think those complications are valid" are very vague arguments. ...
user avatar
  • 508
20 votes
Accepted

How to manage story points when several developers work on 1 story?

When estimating user stories, everyone should be estimating the complete effort it will take the team to get the story to Done. So, the back-end dev should not just estimate the effort it will take ...
user avatar
20 votes
Accepted

When does a Scrum Team assign story points to the stories in the Scrum methodology?

The only certain answer is: sometime before the story is added into the sprint. After that the story point estimate doesn't add much value. Common times that Scrum teams estimate stories: Backlog ...
user avatar
  • 16.7k
19 votes
Accepted

Do user stories which start with "As a product owner I want ..." make sense?

No, they would only make sense if you were writing a product where a "product owner" was a customer -- for example, a tool for keeping a backlog would have stories that start with "As a product owner" ...
user avatar
  • 2,414
19 votes

Does the scrum master also estimate user stories?

If you do development work in the sprint, you should estimate. If you don't, then it's better you skip on providing your own story points estimates. You can help your team with information and advice, ...
user avatar
  • 13.5k
18 votes
Accepted

What is the difference between acceptance criteria and the definition of done?

The acceptance criteria you have listed are really a mixture of stories and tasks. Given your example story: As a user I want to register and log in so that I can register on the application and ...
user avatar
16 votes
Accepted

Do you consider a defect an actual defect if it occurs in Dev prior to the acceptance of the User Story as Done?

Working software over comprehensive documentation. In general, I'd say that it just gets fixed and considered part of the work needed to complete the story. When you found the bug, you added a ...
user avatar
  • 1,390
16 votes

Is it a problem when many stories start with: "As the system,..."

Yes. Using 'the system' as a user in stories is bad. The whole point of the "as a ... I want ... So that ..." Format is to give the developer an insight in to the reason for the requested feature. ...
user avatar
  • 916
15 votes

What is the weighting difference between Epic/Story/Task

In general there are no rules but what you make. Your Product Owner would define what this means to them, then document and share it. If you look as some of the scaling frameworks available there is ...
user avatar
15 votes

Should the Product Owner dictate what info the UI needs to display?

My question is, to what extent should the PO describe the requirements of a UI? To the extent that the designers know what to design and the programmers know what to program. In your example, "as a ...
user avatar
  • 7,475
15 votes
Accepted

Should I leave building the database for the end?

It is worrying that you have no why part to your user stories. This is an important element of the user story format as it allows us to evaluate the stories and to prioritise them. It appears that you ...
user avatar
14 votes

Should I remove a User Story from a Sprint in progress if I know we can't complete it?

The Sprint backlog is a forecast, not a commitment In the 2011 revision of the Scrum Guide Jeff Sutherland and Ken Schwaber made an important change. They changed the word "commitment" to "forecast" ...
user avatar
14 votes
Accepted

User Story Title

TL;DR Titles should be short and pithy, but meaningful. Think of them as communications shorthand that give the team a handle to refer to, not as lengthy descriptors. The story labels should make it ...
user avatar
  • 47.3k
13 votes
Accepted

Should I remove a User Story from a Sprint in progress if I know we can't complete it?

From the Scrum Guide: During the Sprint: No changes are made that would endanger the Sprint Goal; Quality goals do not decrease; and, Scope may be clarified and re-negotiated between the Product ...
user avatar
  • 1,210
13 votes

Should you export data to Excel and Word?

Exporting to Excel is a solution, not a requirement. You need to go back to the owners and get them to detail their functional requirements for the data. Once done, then hand it over to the ...
user avatar
  • 36.5k
13 votes

How to write implementing HTTPS as a user story?

I would focus on the need, rather than the implementation. The user story would then simply be: "As a user, I want any personal information I give (Company) to remain private and secure." With HTTPS ...
user avatar
  • 14.7k
13 votes

How should we hand-off and ticket UI designs to the devs to ensure the developed design matches the provided UI mockups, while still being agile?

I've seen this happen with design so many times. It's a structural problem with how people and teams are organized. Now, I feel like I should say that cross-functional teams are not required to be ...
user avatar
  • 16.7k
12 votes
Accepted

How to use Story Points, if User Stories are completely different?

You can't be faulted for being confused. It is very common for organizations to try and directly match story points to a real-world measurement. This exactly defeats the purposed of using story points ...
user avatar
12 votes

How do I write user stories for Testing tasks?

Writing automated tests should still be part of each user story, as part of your definition of done for each user story. A user story should not be called complete without appropriate tests written ...
user avatar
  • 904
12 votes
Accepted

How to estimate a project budget using story points?

TL;DR For agile projects, a basic formula for estimating budget is: (totalStoryPoints / velocity * teamHoursPerSprint) + nonLaborCosts = budgetEstimate The results should be reported as an ...
user avatar
  • 47.3k
12 votes
Accepted

Thoughts on using user stories to define business/platform needs?

Identifying the Story's Primary Consumer is Acceptable The term "user" in user stories is often better understood as an actor or role in a use case, or even simply as a value consumer. The primary ...
user avatar
  • 47.3k
11 votes
Accepted

User story conversation vs. scope creep

It looks like you have a problem in the ways stories are written. Stories represent an aim which has a value for an actor. If you think about the Mike Cohn version of user stories: "[The actor] ...
user avatar
  • 2,414
11 votes
Accepted

Is it OK to defer implementation detail and consider user story to be done?

I would say no. As you note, user stories should be vertical slices. Another way of looking at that is that they should, by themselves, provide value. You should only burn down stories once those ...
user avatar
  • 14.7k
11 votes
Accepted

Should all team members be assigned user stories?

Question: Do you give each team member a user story A see an anti-pattern here. As a Scrum Master, you don't have to assign stories & tasks to team members. It's their job (under your servant ...
user avatar
  • 3,217
11 votes

How should we hand-off and ticket UI designs to the devs to ensure the developed design matches the provided UI mockups, while still being agile?

Let me challenge the frame of your question a bit: Why do you have such specific requirements that change for every ticket? Is it really necessary to have different margins between buttons on ...
user avatar
  • 7,475
10 votes

User stories - difficult to decide actor

Tl;Dr; The reason to include an actor in the story is to provide context on who it is benefiting. In this case, the site owner derives little, if any value from the story, so you'd go with the site ...
user avatar
  • 16.7k
10 votes

Should you export data to Excel and Word?

As a principle, whether having an Excel is "worth" (business-wise) or not isn't up to the development team to decide. They have to be able to tell whether it's feasible, and objectively tell what are ...
user avatar
  • 1,001

Only top scored, non community-wiki answers of a minimum length are eligible