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 ...
Thomas Owens's user avatar
  • 19.4k
22 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 don't think those complications are valid" are ...
hamena314's user avatar
  • 498
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 ...
Bart van Ingen Schenau's 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 ...
Daniel's user avatar
  • 16.9k
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, ...
Bogdan's user avatar
  • 15.2k
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 ...
Barnaby Golden's 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 ...
RubberDuck's user avatar
  • 1,370
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. ...
Ewan's user avatar
  • 926
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 ...
nvoigt's user avatar
  • 8,505
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 ...
Barnaby Golden's user avatar
15 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 ...
Todd A. Jacobs's user avatar
  • 50.4k
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 ...
Sarov's user avatar
  • 14.8k
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 ...
Daniel's user avatar
  • 16.9k
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 ...
Todd A. Jacobs's user avatar
  • 50.4k
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 ...
Todd A. Jacobs's user avatar
  • 50.4k
12 votes

Does running an agile squad mean that all squad members can do any work, or work should be divided based on skill set?

Cross Functional has more than one layer of meaning. At the lowest level, a cross functional team simply means that all skills needed to deliver a usable increment are present on the team. At this ...
Joel Bancroft-Connors's user avatar
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 ...
Sarov's user avatar
  • 14.8k
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 ...
Aziz Shaikh's 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 ...
nvoigt's user avatar
  • 8,505
10 votes
Accepted

How to deal with a Product Owner who refuses to write user stories?

TL;DR You're not wrong for writing the stories; it may be wrong in continuing to do so without change Scrum doesn't say PO has got to write product backlog items or that they be user stories ...
jason.t.knight's user avatar
10 votes
Accepted

What metrics can we generate from t-shirt sizes (rather than story points) when estimating user stories?

Summary To calculate velocity when using non-numeric relative sizing, you first need to map your story sizes to numeric values. I provide a working example of how to do this with tee shirt sizes, and ...
Todd A. Jacobs's user avatar
  • 50.4k
10 votes
Accepted

User story decomposition into frontend and backend

TL;DR As a rule of thumb (there are always edge cases and exceptions), user stories should represent a potentially-shippable unit of work related to the Sprint Goal. Unless you can ship the front end ...
Todd A. Jacobs's user avatar
  • 50.4k
10 votes
Accepted

Does a user story need to be small and why, when using Kanban

In a word: feedback. Whether you’re coaching a soccer team, flying a drone, planning a city, or writing a dissertation, the sooner you can get feedback, make adjustments, and get more feedback, the ...
Patrick McElhaney's user avatar
10 votes
Accepted

How can I create an Epic based on requirements following best practices?

There are two schools of thought about what an Epic is. Some define an Epic as a large user story, often one that cannot be delivered in a single iteration. However, it can be placed and ordered in a ...
Thomas Owens's user avatar
  • 19.4k
9 votes
Accepted

How can we deal with a big story that does not break down?

Breaking stories down can be a real challenge. One trick is to step away from the original business story and evaluate if it is possible to deliver something smaller but that still produces business ...
Barnaby Golden's user avatar
9 votes

How to write implementing HTTPS as a user story?

First of all, you are potentially misusing user stories as a mechanism. A user story emerges from a real need, it should not be invented or changed to fit the process. Anyway, it could be something ...
Vlad's user avatar
  • 346
9 votes
Accepted

To what framework do "User Stories" belong?

The earliest reference that I could find were that the terms 'story card' and 'user story' were used when Alistair Cockburn visited the Chrysler C3 project. Kent Beck and Ron Jeffries were responsible ...
Thomas Owens's user avatar
  • 19.4k
9 votes

Should I assign user stories per team or per team member?

You are seeing the real velocity. Stories that aren't done don't count. If people keep working on new stories while old stories aren't moved to done yet, that means your team isn't working like a team ...
Erik's user avatar
  • 1,299
9 votes
Accepted

How to break down an 8 point story into smaller stories in Scrum?

I would walk the team through the Story splitting flowchart. Often someone has an idea how to split it, utilising the full team to split is often better than just trying to split it by yourself. Split ...
Niels van Reijmersdal's user avatar
9 votes

Should I leave building the database for the end?

US3 and US4 seem to be the same thing to me. If you need to display the last 5 messages, then that means saving them somewhere, so US3 should somehow deal with that. If US3 does, then US4 is redundant ...
Bogdan's user avatar
  • 15.2k

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