Perhaps all the #Backlog #Prioritization talk about "effort versus value" is nonsense?
Rather, we ask ourselves: what is the next thing we shall do and how can we do that in small, reversible steps?
Rather, we ask ourselves: what is the next thing we shall do and how can we do that in small, reversible steps?
#Backlog #Prioritization example:
1) The balance owing on your credit card is due tomorrow.
2) You don't defer that work because "it's a lot of effort". Rather, you think, "How can I make payment with the least amount of effort?"
1) The balance owing on your credit card is due tomorrow.
2) You don't defer that work because "it's a lot of effort". Rather, you think, "How can I make payment with the least amount of effort?"
#Backlog #Prioritization example:
1) The best feature to release next is ___. It will increase revenue / improve UX / etc.
2) You don't defer that work because "it's a lot of effort". Rather, you think, "How can we build ___ in increments and get feedback along the way?"
1) The best feature to release next is ___. It will increase revenue / improve UX / etc.
2) You don't defer that work because "it's a lot of effort". Rather, you think, "How can we build ___ in increments and get feedback along the way?"
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
