Skip to main content
8 events
when toggle format what by license comment
Jun 8, 2016 at 8:19 comment added bobo2000 How are you measuring stacked ranking i.e. via the position of the backlog?
Jun 7, 2016 at 21:42 comment added RyanTheJenks @bobo2000 is correct. Your manager isn't feeling the pain or seeing the cost of these late changes. If they request a shift in priorities, you need to show the the backlog and ask where this new feature should be prioritized. The great thing about a stacked rank is that it becomes very clear that when you insert one tiny story, everything else is pushed down. That makes the cost very clear.
May 25, 2016 at 12:08 comment added Bart van Ingen Schenau @bobo2000: Abnormal sprint termination should not happen very often. But it is also a very clear message to management that changing the priorities of work being produced right now is costly. That alone should be enough to let them think twice about how important the new request really is.
May 25, 2016 at 11:59 comment added bobo2000 @BartvanIngenSchenau defeats the point of Scrum in my opinion if I keep having to recreate the sprint backlog once a change requests comes through. Often individual stories gets changed, not the entire backlog from experience.
May 25, 2016 at 10:54 comment added Bart van Ingen Schenau @bobo2000: Even with Scrum you can use the described approach. The major difference is that you will take a set of stories from the product backlog at once (this becomes the sprint backlog) and if you boss wants to change the set of stories in the sprint, the complete set gets dropped and you start planning a new sprint (this is called abnormal sprint termination).
May 23, 2016 at 19:38 comment added bobo2000 Often thought about switching to kanban, but that means ditching burn down charts - there is just something about scrum that I like
May 23, 2016 at 16:23 review First posts
May 24, 2016 at 8:10
May 23, 2016 at 16:19 history answered RyanTheJenks CC BY-SA 3.0