Nice article David. Agree with everything you say, just one exception. I think 5 hours a week in the backlog is a bit extreme. It’s too much. My own metric is “a few hours,” more than that and we’re spending too much time analyzing and not enough time building. I’m also very careful about deleting versus archiving – if there’s a decision (“not to build this feature” for example), I want that recorded. The backlog archive is documentation. So yes delete the fluff but not the history.
Five hours is the max to me. If you can do it faster, I value it a lot. I want to make the point that backlog is only part of the job, not the whole job.
Nice article David. Agree with everything you say, just one exception. I think 5 hours a week in the backlog is a bit extreme. It’s too much. My own metric is “a few hours,” more than that and we’re spending too much time analyzing and not enough time building. I’m also very careful about deleting versus archiving – if there’s a decision (“not to build this feature” for example), I want that recorded. The backlog archive is documentation. So yes delete the fluff but not the history.
Five hours is the max to me. If you can do it faster, I value it a lot. I want to make the point that backlog is only part of the job, not the whole job.