Timeline for Why single backlog for cross-functional teams is important?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 31, 2019 at 19:52 | vote | accept | m-80 | ||
| Aug 30, 2019 at 15:20 | answer | added | richardlpalmer | timeline score: 1 | |
| Aug 29, 2019 at 23:41 | answer | added | dyson | timeline score: 0 | |
| Aug 15, 2019 at 7:17 | answer | added | Barnaby Golden | timeline score: 4 | |
| Aug 14, 2019 at 21:56 | comment | added | Todd A. Jacobs♦ | It seems like you're using some form of scaled Scrum, but without any real process scaling. You don't have to use a single backlog for each team in multi-team Scrum, but you will inevitably reduce cross-team collaboration and integration if you don't have a master Product Backlog to hold and track the real cross-team increments. | |
| Aug 14, 2019 at 21:15 | review | First posts | |||
| Aug 15, 2019 at 9:50 | |||||
| Aug 14, 2019 at 21:14 | history | asked | m-80 | CC BY-SA 4.0 |