Age-of-Product.com’s parent company — Berlin Product People GmbH — offers Scrum training classes authorized by Scrum.org, Liberating Structures workshops, and hybrid training of Professional Scrum and Liberating Structures. The training classes are offered both in English and German.
Check out the upcoming timetable of training classes, workshops, meetups, and other events below and join your peers.
Sprint Planning is a core event, defining how your customers’ lives will improve with the next Product Increment. Learn more on how to improve its effectiveness by avoiding 20 common Sprint Planning anti-patterns.
Welcome to the 226th edition of the Food for Agile Thought newsletter, shared with 24,842 peers. This week, we address the state of agile coaching; we learn more about swarming for teams, and we go back in time to the origins of Scrum.
We also come back to the pitfalls of achieving product/market-fit; we declare backlog bankruptcy, and we check a mental model to assess whether a group of product managers is capable of handling their job.
Lastly, we embrace some unique cognitive human traits that will distinguish us from machines for all eternity. Hopefully.
Did you miss last week’s Food for Agile Thought’s issue #225?
How to make Scrum work? Read on to learn more about my top three objectives for Scrum Masters striving to achieve Scrum Mastery.
Food for Agile Thought’s issue #225—shared with 24,837 peers—addresses the importance of pair programming; we seek to excel at predicting the future with probabilistic forecasting, and we appreciate an outsight view on Scrum by following sticky notes.
We also point at a crucial stakeholder management competence of Product Owners and Scrum Masters; we enjoy new games and exercises for ideation purposes, and we consider making our product worse for the sake of improving it.
Lastly, we embrace the coining of decaf resistance—it is good to know that a habitual behavior in so many organizations now has a name.
Did you miss last week’s Food for Agile Thought’s issue #224?
There is one product, one Product Owner, one Product Backlog — a simple rule. How is that supposed to scale, you might ask, isn’t that approach turning the Product Owner into the Scrum team’s bottleneck, impeding value creation rather than spearheading it? Well, cargo cult Scrum might end up in that dead-end. The trick to avoiding this fate is to start including the Development Team as early as possible in Product Backlog management which requires a product mindset.
Learn more about how to kick-off this process with an initial day-long product mindset workshop for your Scrum team.
