Allen Holub
I don't use tickets. To me, a ticketing system is nothing but a detailed up-front plan, waterfall at it's worse. If I see something that needs doing, I just do it. I also don't use backlogs for the same reason.
Nov 23, 2022 at 2:46amWeb
Show threadKenNov 23, 2022

@allenholub how do you keep track of work that you know you need to do (or want to do?) without overloading your brain?

I use OmniFocus for my personal projects but what about collaborative projects

Show threadAllen HolubNov 23, 2022
@Pearapps
I usually use physical stickie notes unless I'm working with a remote collaborative team. In that case, I use Miro.com. The main thing is that I want to make sure that everything is addressed before I push. I don't concern myself much with what-if's.
Show threadKenNov 23, 2022
@allenholub okay, thank you, that is helpful!
Show threadDoug WarrenNov 23, 2022

@allenholub

ALLEN'S S.O.: Thanks for going to the store, hon. Did you get those little cookies I asked for?

ALLEN: ...Shopping lists are tantamoint to waterfall.

Show threadDenial 🐔 ShownNov 23, 2022
@allenholub tickets are often used in orgs less for "what to do in the future", and more for "what did we do already" either to provide A) evidence of value delivered to budget makers or B) key information in escalation communication to SME.
Show threadEvan Wang 王艾文Nov 23, 2022
@allenholub I agree with most of your takes, but this one I can’t agree with. It almost reads like sarcasm.
Show threadStefan RoockNov 23, 2022
@allenholub I agree that most backlogs are a kind of big upfront plan and I have worked successsully without.
On the other hand Story Mapping and alike can create a shared understanding for the whole team that enables devs to create User Stories themselves. And that may lead to not needing a backlog any longer.
Show threadAllen HolubNov 23, 2022
@StefanRoock
Yes. I love story mapping. Of course, you have to do it right—it's changing all the time as you learn.
Show threadCTO Coach 'Amazing' Stephan 🍉Nov 23, 2022
@allenholub I also think backlogs are an anti pattern - as are ticketing systems, for the same reasons you mentioned.
Show threadChristian SeilerNov 23, 2022
@allenholub How do you manage error reports from customers?
Show threadAllen HolubNov 23, 2022
@christianseiler
I have a strict no-known-bugs-on-release policy. At Hunger, which has exactly that policy, one team went 1.5 years without a reported bug. (They're also mobbing 100% of the time and have a serious commitment to a quality culture.) If you do all that, then not many bugs come in. I just fix them as soon as it's convenient.
Show threadIljaNov 23, 2022

@allenholub if you have things that need to be done, it totally makes sense to make a plan on how to do them most efficiently. That’s routine work.

But that’s not what agile is about. Developing innovative products is about exploring options. You want to have a set of options that’s bigger then what you can do. And you sift through that heap of ideas for the next thing to learn more about, so that your decisions can get better and better over time. #realoptions

Show threadAllen HolubNov 23, 2022
@ipreuss
I think we differ. It's not about exploring random options that pop into somebody's head. It's about releasing for feedback and adjusting. I see no point in keeping around a slush pile of nice-to-haves and ideas no customer cares about. That stuff does not belong in a ticketing system at all, IMO, though you may keep a notebook of them.
Show threadIljaNov 27, 2022
@allenholub a backlog if a sorted list of non-random ideas that customers and users might care about, and that therefore we might want to get feedback on by releasing something to them.
I agree that what you’re describing sounds pointless. But that’s not a reason to not use backlogs. It’s a reason to come up with better product ideas.