Timeline for Multiple scrum teams moving to single backlog
Current License: CC BY-SA 3.0
31 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 22, 2013 at 18:07 | history | bounty ended | Bart van Ingen Schenau | ||
| S Dec 22, 2013 at 18:07 | history | notice removed | Bart van Ingen Schenau | ||
| S Dec 21, 2013 at 17:34 | history | bounty started | Bart van Ingen Schenau | ||
| S Dec 21, 2013 at 17:34 | history | notice added | Bart van Ingen Schenau | Reward existing answer | |
| Aug 3, 2013 at 7:22 | audit | Close votes | |||
| Aug 4, 2013 at 6:00 | |||||
| Jul 30, 2013 at 1:46 | audit | Close votes | |||
| Jul 30, 2013 at 11:04 | |||||
| S Jul 29, 2013 at 17:57 | history | bounty ended | Karl Bielefeldt | ||
| S Jul 29, 2013 at 17:57 | history | notice removed | Karl Bielefeldt | ||
| Jul 28, 2013 at 0:01 | answer | added | Brett Maytom PST | timeline score: 2 | |
| Jul 27, 2013 at 1:02 | answer | added | Mateusz | timeline score: 0 | |
| Jul 26, 2013 at 22:15 | answer | added | oberlies | timeline score: 1 | |
| Jul 26, 2013 at 16:19 | audit | Reopen votes | |||
| Jul 27, 2013 at 10:38 | |||||
| Jul 24, 2013 at 18:52 | comment | added | user53019 | @AndrewFinnell keep in mind I'm not the OP, I've merely offered up an answer with my team's observations. We don't have a burning need to split out to separate backlogs at this point in time. The OP may be interested in that approach, but that would be a separate question. It may also be out of the OP's purview to make the decision. Senior management may have declared a path irrespective of any technical considerations. | |
| Jul 24, 2013 at 18:08 | comment | added | Andrew T Finnell | @GlenH7 This sounds like something that could be solved by using a different Tool set. What tool are you using to manage the backlogs? I am attempting to think out of the box for this situation. I believe Greenhopper from Atlassian could handle this scenario. | |
| Jul 24, 2013 at 17:47 | comment | added | user53019 | @AndrewFinnell multiple backlogs prevents an easy aggregation of commitment levels as well as easy understanding of what's in flight at that moment. And they may just be tired of going to system X for team X and system Y for team Y and ... | |
| Jul 24, 2013 at 17:32 | comment | added | Andrew T Finnell | Why can't sprints be created based on multiple back logs where the highest priority items are done first? What is the perceived advantage of moving them all into a single logical backlog? | |
| Jul 23, 2013 at 18:31 | answer | added | user53019 | timeline score: 8 | |
| Jul 23, 2013 at 17:36 | answer | added | dsw88 | timeline score: 1 | |
| Jul 23, 2013 at 17:36 | history | tweeted | twitter.com/#!/StackProgrammer/status/359728762708967425 | ||
| S Jul 23, 2013 at 17:20 | history | bounty started | Karl Bielefeldt | ||
| S Jul 23, 2013 at 17:20 | history | notice added | Karl Bielefeldt | Draw attention | |
| Jul 22, 2013 at 18:16 | comment | added | Bart van Ingen Schenau | The biggest challenge I see is not for the team(s), but for the product owners of the combined backlog. They will have to agree on the prioritisation of the tasks for the different products. | |
| Jul 14, 2013 at 22:50 | comment | added | Sklivvz | Is senior mgmt combining the two product in a single product? If not, it doesn't make much sense IMO. | |
| Jul 12, 2013 at 14:39 | comment | added | MetaFight | The backlog is, by definition, product-specific. I think your management is trying to abuse a product-specific tool (the backlog) in order to make their inter-product planning easier. This is a bad idea. And because it's a bad idea I think you'll find very few people who've attempting this and, subsequently, very few people to talk to you about their experience with this. | |
| Jul 12, 2013 at 13:40 | comment | added | Malcolm | @IoannisTzikas - No both teams will remain the same. Merging the teams will make them too big. Senior management wants to combine the backlogs into one and have both teams work off the same backlog while cross-skilling the developers. | |
| Jul 12, 2013 at 13:37 | comment | added | Malcolm | @MetaFight - Senior management that want to merge backlogs and then have the two teams be feature based so they can pull the highest priority feature off the backlog regardless of the system it impacts. There are many challenges with it and I did propose the same option you did - Just move a team member over. But what I am really after is anyone can share their experience of moving to a single backlog. Did it work? | |
| Jul 12, 2013 at 10:09 | comment | added | Ioannis Tzikas | Are you merging those 2 teams into a larger one to work on different products but on a single backlog? | |
| Jul 11, 2013 at 20:40 | comment | added | MetaFight | I'm not sure I understand why you'd want to merge backlogs. Why not have team members move between teams as needed instead? | |
| Jul 11, 2013 at 17:27 | review | First posts | |||
| Jul 11, 2013 at 17:53 | |||||
| Jul 11, 2013 at 17:21 | history | edited | user53019 | CC BY-SA 3.0 | fixed the TITLE. No need to shout, either. |
| Jul 11, 2013 at 17:08 | history | asked | Malcolm | CC BY-SA 3.0 |