Re: How to handle pressure fron product owners
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <CADA3vVVo_gCmzcDTiCwhML7hBAkXvzovgM+hQwPXN4EXxipOXQ@mail.gmail.com> |
One of the major benefits of the entire concept of a sprint is the focus that it gives the dev team because they are protected from mid-sprint scope changes. If the domain that you work in can change that drastically mid-sprint, maybe your sprints are too long for the environment. Or maybe the PO's value sense needs some work. I have a hard time believing that what was the absolute highest priority at the beginning of the sprint is not obsolete or of zero value. That just blows my mind and smells of a more systemic problem. On Tue, Nov 17, 2015 at 1:47 PM, 'Zander Collier, III' [email protected] [SCRUMDEVELOPMENT] <[email protected] > wrote: > > > You wrote something that I think is telling: "PO just found ... might not > add business value". > > You shouldn't change course based on "might". Your PO needs better > definition than "might". > > On Mon, Nov 16, 2015 at 2:50 PM, [email protected] [SCRUMDEVELOPMENT] > <[email protected]> wrote: > >> Hi All, Good day. >> I am in between my Sprint n the team is fully functional. My product >> owner just found n informed that some of the user stories from the ongoing >> sprint might not add business value or r obsolete n wants the team to >> replace them with a new set of features which r not yet estimated. The team >> has already completed their coding n is now trying to integrate test it. >> How do v handle such scenarios or requests mid Sprint ? Should i accept >> these new features? My take would be to stop r minimize the obsolete >> features but continue with the remaining features of the Sprint without >> shortening the Sprint n later consider the new list for the next sprint? >> My po is very particular to replace them now itself. What is ur / scrum >> framework take here? There could b a discussion that if i continue with >> the current planned features, its a waste of effort n budget as v should >> anyways rework to include new features later. But if i agree to the changes >> now, i might be sending a wrong message which could become a practice to my >> po to request similar changes in future n my team might get demotivated. >> Kindly advise. >> >> ------------------------------------ >> Posted by: [email protected] >> ------------------------------------ >> >> To Post a message, send it to: [email protected] >> To Unsubscribe, send a blank message to: >> [email protected] >> ------------------------------------ >> >> Yahoo Groups Links >> >> >> >> > >