Product backlog - do you really need an app for that?

Some time ago I encouraged you to put your sprint backlog on the wall because of transparency and efficiency. Today I want to ask you to go even further and put your backlog on the wall (or whiteboard if you want). The whole product backlog? Yes - the whole product backlog - with each story that belongs to it.

And the great question is: But why? Let's see.

replacement?

Using a dedicated application is really easy and user friendly and some of us can argue that without such support we are losing many benefits, like storing attachments related to user stories. And what about Definition of Done? How is it even possible to put it whole on small sticker? Regardless of how tiny our letters would be, we would always - rather sooner than later - reach the limit.
That's true, and that's why I'm starting with this to clarify one important thing - I don't want you to replace your product backlog, but to create something what I'm calling "a quick overview". Something what will help you to manage the scope and plan your next sprints easily and fast.

just ask me how?

There's a common problem with almost each software which lives more than a half year - numbers of stories grow rapidly and they don't want to stop. Applications let us to put into them as much information as we want to and there's a really small chance that we will reach their limits. And it's good, right?
My answer is no.

Immense amount of items allows us for nothing more than storing garbage, to avoid cleaning from time to time. I know that product backlog should be cleaned once a while and it's even mentioned a few times in Scrum Guide, but... many people around as just see that as a useless activity, wasted time. If I have possibility to add whatever I want I will just put a newly created stories on top (ok, I will look at a few on top as well to do so called “backlog sorting”).
Once again, I agree that we should avoid such behavior, but people are lazy (which is not always a bad thing) and if they cannot do something they definitely will.

how does it change with PB placed on the wall?

Limited space forces us to cleaning backlog, even if we would like to, we cannot avoid this. And while doing this, meanwhile, we are sorting backlog as well.
Solution like this requires small duplication because we need to have story on the wall and in the application (as a reference for more information), but if you will keep stories' names short and descriptive this additional effort won't be even noticed.

what about scale?

This is a really good question, important to answer.
In a huge project it would be impossible to put all stickers with all user stories on the wall. There's just too many of them. What you can do instead is either use epics, not stories or split backlog for teams or sets of teams.

don't wait - try

As it goes for true Agile people, one main characteristic should be being eager for improvements, it should be done continuously. That's why I encourage you to try. It costs nothing and can bring you a lot of benefits.

The main purpose is not to allow product backlog to grow to unmanageable proportions. This is why you should find a way to force yourself to keep it clean. And if your wall can help you with that… why not?