Was asked "Can Scrum Master be held responsible if development team is not delivering on time?" The whole notion of "delivering on time" flies in the face of basic Agile thinking. "On time" means that you're matching an estimate of a detailed up front plan. 1/5
Detailed up-front plans are the opposite of agile thinking. Teams learn as they work. The things they learn often "slow them down." If, for example, they learn that it's not worth building the thing they're working on, they'll stop working on it. 2/5
They won't deliver that thing at all, much less "on time." Do you really want to punish somebody for not wasting the company's money building something that nobody wants? 3/5
Holding the "SM" "responsible" is even more of a dysfuntion. First, it is NOT the SM's job to keep the team "on schedule," so it's like holding your accountant responsible for a plumbing problem. An SM is ***not*** another word for "project manager." 4/5
More importantly, a culture of blame and punnishment will destroy any agility you may have. Agile systems are built on respect and trust. I see neither in the notion of "holding an SM responsible for delivering" something of dubious value on somebody else's schedule. 5/5
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.