Jason GormanIf you already know what's in your backlog for the next N iterations of your product, you're not doing iterative development. You're working through a plan.
craignicol@jasongorman but without a backlog how would we keep track of the low priority work that's never going to get done?
Andy Wootton@craignicol @jasongorman That's not the point of a Backlog. It's there to remind you why you said "No!" the previous 3 times they asked for this and ignored your reasons why it was a Really Bad Idea (in case anything has changed. I never experienced that happening but it could.)
@jasongorman @woo I've got a "to-don't" list for that. Put the item, and the reasons why, and until any of those reasons change, it stays there.
@craignicol @jasongorman Ahh, so you do have a backlog but call it something else :-).
Must, Should, Could and Won't, or 'To Not Do'. MoSCoW.
Must, Should, Could and Won't, or 'To Not Do'. MoSCoW.
@jasongorman @woo I have a backlog the same way this is my junk mail filling cabinet 🗑️