And would you say this still applies if you are running a discovery team that is distinct from the delivery team - with the first focused on validating problems and hypotheses, the second tasked to deliver solutions? #dualtrack
Like in Highlander, there can be only one...backlog. As soon as you spread work out to multiple lists (e.g., a discovery backlog) you put the team in the position of choosing between competing priorities. One backlog normalizes all types of work and forces focused prioritization.
-
-
-
you lost me at discovery team vs delivery team :-)
- Show replies
New conversation -
-
-
Thoughts on individual debt (UX, Tech) backlogs which feed into a single backlog that is prioritized / worked from? Avoids the team having to chose between priorities, but allows shared ownership. Maybe these technically aren't backlogs and my teams have just called them that.
-
I worry that building these individual boards invests the authors in their silos rather than in the customer or the team’s backlog. It’s like using the time when others are speaking to work out your argument about why they are wrong instead of listening.
- Show replies
New conversation -
-
-
This is why design doesn’t work as a “shared service.”
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It’s better to burn down, than to fade away!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Disagree. A backlog is just a collection of things and usage/process/policy is what make it useful (or not). If I want multiple logical backlogs in one physical backlog, I’ll find a way to do it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.