Skip to main content
added 2 characters in body
Source Link
nvogel
  • 6.3k
  • 1
  • 10
  • 28

The reasons why it's advisable not to change the goal of a sprint backlog during a sprint are to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.

The reasons why it's advisable not to change the sprint backlog during a sprint are to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.

The reasons why it's advisable not to change the goal of a sprint during a sprint are to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.

grammar
Source Link
nvogel
  • 6.3k
  • 1
  • 10
  • 28

The reasonreasons why it's advisable not to change the sprint backlog during a sprint isare to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.

The reason why it's advisable not to change the sprint backlog during a sprint is to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.

The reasons why it's advisable not to change the sprint backlog during a sprint are to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.

Source Link
nvogel
  • 6.3k
  • 1
  • 10
  • 28

The reason why it's advisable not to change the sprint backlog during a sprint is to allow the team the best chance to deliver the product increment, to help maintain a sustainable velocity and to maintain confidence in the regular cadence of delivery. Ultimately I suggest the PO should take the decision on whether to change the scope during the sprint. The PO should listen to the team if they have any concerns, understand that there may have to be compromises made but if the PO accepts that and is willing to justify the decision to stakeholders then I think that has to be his or her call.

You should examine why this has happened. It could just be that mistakes were made during prioritisation but in some cases it could also mean that sprints are too long, making it harder to anticipate what might arise before the end of each iteration.