Nice video, I'd be interested in hearing where the business analyst fits into the picture (as product owner? and if so, what about project managers?).We try to use kanban, and have a pretty tight 'backlog' but it inevitably gets huge and then, as he says, everyone gets a bit over it - being able to say 'no' is so important.Thanks for the post!
My initial thoughts- I'm not sure why the "no"s go in the trashcan. It seems like the video said they become "no"s simply because there are too many ideas. If you have many good ideas, it seems like there would just be some adjustment in your "backlog grooming" as opposed to throwing these ideas away as illustrated.
Great overview of Agile! BAs facilitate communication and grooming of the backlog (prioritization). Rather than a simple No, the stakeholder group should consider the tradeoffs and ideally the requester will remove his or her request when the value is shown to be too low.
Alexis and Barbara,As I understand it, the idea of the "no" bin is based on training your client to align their expectations to your capacity. If things are important they'll come back. If something more important you learn to not invest in the related discovery and analysis work, saving money and increasing agility.
The "No" bin is really the equivalent of "someday/maybe" in GTD. That is, we MIGHT build this in the future. But then, we MIGHT build anything in the future. So there's zero commitment to this feature, we don't track it in a list, we don't spend any resources on it. The most honest way of communicating that is to simply say No. But in a polite way :o)
Thanks Henrik. And thanks for your many other contributions to the community.
Great clip. Well done.The concept of "the bin" is bound to spark controversy everywhere except with the dev team
Andrew, yes and for many different reasons including "my job is generating ideas for the list" I think talking with people and helping them understand the system helps ready them for change in many cases.