Welcome, Guest
Username: Password: Remember me

TOPIC: Changes to Sprint Backlog

Changes to Sprint Backlog 2 months 3 weeks ago #443

  • Michael Wittenburg
  • Michael Wittenburg's Avatar Topic Author
I understand that the agreed sprint backlog is like a contract between the product owner and the delivery team and is normally not altered and cancelled only in extreme events.

My question is the following:

The sprint has been kicked-off and the development team has started working on the user stories.

Let's assume there is a storry which was not foreseen (as it was not known) for the current sprint but is of high value (e.g. could get rid of a high risk) and could be easily accomodated.

Should the sprint backlog be altered and this story be added to demonstrate "responding to change over following a plan" or should it be put in the backlog of the next sprint ...

I am tempted to say add it, as it is easy, does not jeopardize the objective of the sprint and demonstrates and agile mindset ...

But I am not sure. Any thoughts?

Changes to Sprint Backlog 2 months 3 weeks ago #444

  • Bankim Sanghavi
  • Bankim Sanghavi's Avatar Topic Author
Hi Michael,

As far as I understand, the current sprint backlog cannot not be modified.

If an extremely important user story has been identified, PO can either cancel the current sprint and start a new sprint with the important user story included in it or wait for the next sprint to add the
user story to the sprint backlog.

I apologize if this is incorrect.

Regards,

Bankim

Changes to Sprint Backlog 2 months 3 weeks ago #445

  • Michael Wittenburg
  • Michael Wittenburg's Avatar Topic Author
This is also my understanding ... but I hear from Certified Scrum People that they would change it in view of flexibility.
Your answer has been my original answer ... but I have found nowhever a confirmation.
Time to create page: 0.065 seconds