There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. One failure symptom of a botched agile transformation is the frustrated Scrum Master.
📺 Join me and explore the consequences of a Scrum Master who has thrown in the towel in 92 seconds.
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. To make things worse, a crucial success factor of every Scrum team is not even mentioned in the Scrum Guide: Any organization that wants to employ Scrum to learn faster than its competitors needs to have a solid failure culture.
📺 Join me and explore the consequences of not living a failure culture in less than three minutes.
Contrary to popular belief, the Scrum Master success principles are tangible, when we guide the analysis with an outside perspective.
Read on and discover four Scrum Master success principles: From when not to use Scrum to product quality to supporting the Product Owner to putting self-management at the center.
Do you need an emergency fund as a change agent—whether you are acting as Scrum Master, Product Owner, or agile coach—because conflict is inevitable, but change is not? Speaking truth to power probably comes at a price.
In my experience, speaking truth to power, pointing at the emperor’s new clothes and the reality in the trenches, is necessary a trait for every change agent — including Scrum Masters and agile coaches — in organizations that lack strong leadership.
Learn more, how this form of professional honesty can backfire when the incumbents, privileged by the existing system, strike back.
There has never been a shortage of articles claiming that Agile is either dead, failing, disrespectful, or useless, with authors ranging from respected signatories of the Agile Manifesto to click baiters to people who never experienced the real thing in the first thus lacking a standard for comparison. (See the links below.)
The question from my perspective, though, is: Have we finally have reached peak agile?
Imagine you’re a Scrum Master and the line manager of your team believes that the best sign for a successful agile transformation is a steady increase in the Scrum Team’s velocity. Moreover, if the team fails to deliver on that metric something is wrong with the Scrum Team. Alternatively, something is wrong with you as you are the Scrum Master and hence responsible for the team’s performance. (Apparently, not faking agile metrics, or being transparent in this case, does not seem to be valued here.)
Learn more about how to coach these kinds of line managers and help them overcome their preference for the industrial past with a simple exercise on how to cook the agile books.
