It's in front of the team so that obstacles can be solved by the team. It's why it's not in front of people outside of the team. The number of times where someo

It's in front of the team so that obstacles can be solved by the team. It's why it's not in front of people outside of the team. The number of times where someone says "I'm struggling with X" and someone else says "Oh! I know about X! I can help!" has been innumerable. And, it really doesn't contribute to a etc. I've had devs spend days with basically the same status, but it also was a large task. I've had devs make incremental progress, and everyone understood. I've had devs (and been a dev!) who said "I got nothing done; I was in meetings and they drained me", and it's fine (though it helps highlight that the meetings are too much very early). The process presumes culture. It assumes the team functions together and is aligned in delivering, and isn't looking to blame one another. If the culture is bad, then, as with any bad culture, it's easy to blame the process.