RE: How to handle pressure fron product owners

"Eric Gunnerson [email protected] [SCRUMDEVELOPMENT]" <[email protected]>
Newsgroups gmane.comp.programming.scrum.general
Message-ID <BL2PR03MB3543773D8F7A16B6F8203EC851D0@BL2PR03MB354.namprd03.prod.outlook.com>
If you are following Scrum, your options are to either put off the features until the next sprint or to blow up the sprint. There are only those two options so that it is obvious to the PO that blowing up the sprint is a very impactful thing to do for the team. If there is a big disconnect, I would vote for blowing up the sprint after you tell the PO what it’s going to cost.

My personal preference is to run sprints on a weekly cadence; this makes it much easier for the team to flex to whatever work has the most business value right then and it reduces the need for the product owner to blow up a sprint because they have more opportunity for input.

It also sounds to me like you have a backlog problem; if you have a good backlog, this sort of thing should come up rarely.

Eric
From: [email protected] [mailto:[email protected]]
Sent: Monday, November 16, 2015 2:51 PM
To: [email protected]
Subject: [SCRUMDEVELOPMENT] How to handle pressure fron product owners



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.
image001.jpg (image/jpeg, 359 B) - not displayed
image002.jpg (image/jpeg, 332 B) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.