In this highly engaging speaker session from the Agile Camp Berlin 2021, Jutta Eckstein and Maryse Meinen point out the advantages of creating diverse, cross-functional teams to benefit your customers and your organization.
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. While it is common to first look outside our team for impediments, such as dysfunctional processes or other systemic issues, I would advise starting with the Scrum team’s way of collaboration: Are we aligned on the why, what, and how? Otherwise, the three following Developer blunders may diminish the team effectiveness.
📺 Join me and explore the consequences of these Scrum Developer blunders and what you can do about them in a little more than five minutes.
Update: I am running a poll on LinkedIn—join the voting: “What common ways have you observed how Developers diminish the value creation of their own work?”
Welcome to the 296th edition of the Food for Agile Thought newsletter, shared with 31,704 peers. This week, we acknowledge that rebels spark ideas, and we consider whether OKRs can restore purpose to agile teams and free them from the tyranny of the Product Backlog. Moreover, we get an inside view of how Youtube managed its early hyper-growth, and we point at the advantages of using low-code tooling to build software: Iterating faster.
We then address why the tech industry has such a high proportion of weak product managers and product leaders. We pitch the advantages of collaborative decision-making, leveraging both stakeholders’ and developers’ expertise while creating a shared understanding. Also, we share three tactics that have proven to impact getting buy-in from team members significantly.
Lastly, we enjoy an interview with Christina Wodtke on how OKR can help product managers accomplish more, and we get curious about a new Scrum software: “HappyStack is a Scrum project software tool for developers: Backlog, Sprint Planning, Standups, Reviews, and Retros done the right way.”
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. Scrum thrives when the Scrum teams are self-managing while Scrum Masters embrace their role as servant-leaders. However, this also implies that Scrum Masters fail when they are overly protective.
📺 Join me and explore the consequences of the overly protective Scrum Master and what you can do about it in less than three minutes.
Update: I am running a poll on LinkedIn—join the voting: “How can Scrum Masters fail their team by being overly protective or supportive?”
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. When Scrum becomes an element of an agile transformation, the following three common essential agile failure patterns prove to be an exceptionally tough nut to crack for any Scrum Master.
📺 Join me and explore the consequences of foreseeable failure patterns and what you can do about them in a little more than seven minutes.
Update: I am running a poll on LinkedIn—join the voting: “What is your top agile failure pattern in organizations?”
Welcome to the 295th edition of the Food for Agile Thought newsletter, shared with 31,527 peers. This week, we delve into overcoming team limits with Jeff Sutherland, the co-creator of Scrum. We also dive into an adjacent topic: Team-building in organizations that double the employee count at least yearly, and we analyze some psychological issues that might interfere with the core of agility.
We then share ten compelling reasons why to stay out of meh work. Moreover, we reflect on the necessity of loving your customer’s problem, not your solution, and we embrace a comprehensive primer on how innovators can use the JTBD framework to create successful products.
Lastly, we appreciate a new academic paper on the effectiveness of Scrum teams.
