Skip to main content
edited out polling material and highlighted the questions
Source Link
jmort253
  • 9.5k
  • 7
  • 42
  • 88

What do you defines as an impediment?What exactly is an impediment? I know that Scrum say that and impediment is something that stop the team from performing the best it can. So basically it can be everything? But where goes the magical line where it becomes and internal improvement?

For example. We want to have more realistic test data in our databases, is that internal improvement or impediment?is that internal improvement or impediment? We as a team could try to solve it in the sprint along with the other stories directly, or we could say that it's an internal improvement that needs to be a story and go into the product backlog.

As I see it we have three options: 1. Handle all internal improvements as stories in the backlog and make the PO prioritize them. 2. Work with them along regular stories in the sprint. 3. Big things goes in as stories and small stuffs we can do directly in the sprint without it effecting the velocity much.As I see it we have three options:

  1. Handle all internal improvements as stories in the backlog and make the PO prioritize them.
  2. Work with them along regular stories in the sprint.
  3. Big things goes in as stories and small stuffs we can do directly in the sprint without it effecting the velocity much.

How do you handle this? We need tips and ideas on how we can do this :)Which is the correct option?

What do you defines as an impediment? I know that Scrum say that and impediment is something that stop the team from performing the best it can. So basically it can be everything? But where goes the magical line where it becomes and internal improvement?

For example. We want to have more realistic test data in our databases, is that internal improvement or impediment? We as a team could try to solve it in the sprint along with the other stories directly, or we could say that it's an internal improvement that needs to be a story and go into the product backlog.

As I see it we have three options: 1. Handle all internal improvements as stories in the backlog and make the PO prioritize them. 2. Work with them along regular stories in the sprint. 3. Big things goes in as stories and small stuffs we can do directly in the sprint without it effecting the velocity much.

How do you handle this? We need tips and ideas on how we can do this :)

What exactly is an impediment? I know that Scrum say that and impediment is something that stop the team from performing the best it can. So basically it can be everything? But where goes the magical line where it becomes and internal improvement?

For example. We want to have more realistic test data in our databases, is that internal improvement or impediment? We as a team could try to solve it in the sprint along with the other stories directly, or we could say that it's an internal improvement that needs to be a story and go into the product backlog.

As I see it we have three options:

  1. Handle all internal improvements as stories in the backlog and make the PO prioritize them.
  2. Work with them along regular stories in the sprint.
  3. Big things goes in as stories and small stuffs we can do directly in the sprint without it effecting the velocity much.

Which is the correct option?

Tweeted twitter.com/#!/StackProjects/status/213082123790323712
Source Link
Daniel
  • 71
  • 1
  • 1
  • 2

What is an impediment, and how to handle them and internal improvments in Scrum?

What do you defines as an impediment? I know that Scrum say that and impediment is something that stop the team from performing the best it can. So basically it can be everything? But where goes the magical line where it becomes and internal improvement?

For example. We want to have more realistic test data in our databases, is that internal improvement or impediment? We as a team could try to solve it in the sprint along with the other stories directly, or we could say that it's an internal improvement that needs to be a story and go into the product backlog.

As I see it we have three options: 1. Handle all internal improvements as stories in the backlog and make the PO prioritize them. 2. Work with them along regular stories in the sprint. 3. Big things goes in as stories and small stuffs we can do directly in the sprint without it effecting the velocity much.

How do you handle this? We need tips and ideas on how we can do this :)