No matter if you are a Scrum Master or an agile coach, sooner or later, you will run into a problem that’s outside of the team’s sphere of control. The question is: How do you solve impediments of this kind? What approach has worked best for you in the past?
Barry Overeem, Christiaan Verwijs and I teamed up to provide some transparency in this matter and share your best techniques and approach with the agile community. All it takes to contribute is five minutes of your time to participate in the anonymous ‘how to solve impediments’ survey. (We expect results to be available in November.)
The seventh Hands-on Agile webinar Scrum Sprint Anti-Patterns analyzes 12 ways a Scrum team can improve its effectiveness by avoiding typical sprint anti-patterns. Learn on October 2nd, 2018, at 6 pm CEST more about gold-plating, delivery Y instead of X, absenteeism, side-gigs, and organizing people instead of the flow of work.
A meta-retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action-items. It comprises of the team members of one or several product teams—or representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers.
Meta-retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product. Read more on how to organize such a meta-retrospective.
Almost three years into building this community, I believe we might now have achieved the critical mass to organize a great conference — the Hands-on Agile 2019 Conference. Currently, I would target the second quarter of 2019 for the first Hands-on Agile conference. To reduce complexity, I would plan for Berlin as its location although London might be an alternative.
Update 2018-08-12: The survey results are in — it is Berlin, see below.
Scrum Master Duties: supposedly, a great scrum master serves only one scrum team — that's at least a popular narrative in the scrum community. Nevertheless, there is also a loud voice that doubts that approach: what would you do the whole day - with a single team? Aren't they supposed to become self-organizing over time? And if so, does the scrum then need a scrum master 24/7?
As I worked for years as a product owner on scrum teams without a dedicated scrum master-which was working well-I was curious to learn more about that question, too. Hence I ran a survey in late June and early July 2018, the results of which are presented here.
In total, 261 scrum masters participated in this non-representative survey in the two weeks before July 5th, 2018. 19 participants chose not to provide their consent to Google processing and to store their answers. Hence their contributions were deleted, resulting in a sample size of 242 responses.
Master autonomy purpose — in this article, I present a slightly different way of viewing agile maturity, through Dan Pink's lens of Mastery, Autonomy, and Purpose; as a simple and useful way of fostering conversations and ensuring all relevant perspectives are considered.