TL; DR: Sustainable Agility at the Enterprise Level w/ Jorgen Hesselberg — ACB21
In this highly engaging speaker session on sustainable agility from the Agile Camp Berlin 2021, Jorgen Hesselberg delves into the root cause of failing agile transformation efforts: Rejection by the organization as the transformation does not address the organization’s needs. Do we dare to say: Sometimes, agility is a solution looking for a problem?
TL; DR: Killing Product Thinking — Food for Agile Thought #300
Welcome to the 300th edition of the Food for Agile Thought newsletter, shared with 32,162 peers. This week, we delve into killing product thinking w/ Jeff Patton. Also, we remind ourselves why the idea that “building software should be like building a house” is an unsuitable metaphor and why structure drives strategy so often. (Spoiler alert: the preferred way would be way messier.)
We then reflect on the many ways you can turn a hypotheses validation into a v1, and we explain how user research fits into continuous product discovery. Moreover, we present the “3Q-DO NO HARM” framework to help you avoid causing harm at scale with your product.
Lastly, we share a team alignment exercise built on Liberating Structures.
TL; DR: How to Win with Agile Resistant Teams w/ Scott Weiner — ACB21
In this highly engaging speaker session from the Agile Camp Berlin 2021, Scott Weiner shares a case study on how to master an agile transition by creating agile resistant teams based on common sense, team autonomy, and the psychology of metrics.
Welcome to the 60 Questions for the New Scrum Master Download Page
Congratulations on your new Scrum Master position! Now what?
What has served me well over the years is a combination of observation and asking questions. The following 60 Questions for a New Scrum Master may support you in learning more about the Scrum team’s way of working and the organization’s culture.
Get Started and Inspect and Adapt along the Way
The following set of questions is intended as a starter to get a new Scrum Master airborne in a short period. Depending on how familiar your team is with Scrum, the kind of the team’s organization and its culture, and the market your Scrum team is serving, this set of questions may require change.
The questions have proven helpful in 1-on-1 conversation, in group discussion, and the form of an anonymous survey. But, no matter the format, the questions pave the way for a new Scrum Master to gather insight into the Scrum team’s way of working and the organization’s culture they need to start to support the team.
Cannot see the subscription form? Please click here
Congratulations on your new Scrum Master position! Now what?
What has served me well over the years is a combination of observation and asking questions. The following 60 Questions for a New Scrum Master may support you in learning more about the Scrum team’s way of working and the organization’s culture.
TL; DR: Learning from Spotify, The Lizard Brain & Agile—Food for Agile Thought #299
Welcome to the 299th edition of the Food for Agile Thought newsletter, shared with 32,056 peers. This week, we continue learning from Spotify: Kevin Goldsmith shares lessons learned during the hay days of the “Spotify Model.” Moreover, we delve into the psychology of our inner lizard, constantly on the alert and hiding below a thin crust of civilization and how it relates to team building. Finally, we also witness a desperate attempt by McKinsey to save the PMO by relabeling it ATO. (The sad thing is that C-level folks from BigCorp will go for it.)
We then reflect on autonomy, empowerment, agency, and what that means for work at the team level, and we try to define what “product sense” is about in design, product management, engineering, or venture capital. Also, Ken Norton shares another interview from his outstanding series on successful product practices, and there is an infographic on the differences between projects and products developed by agile teams.
Lastly, we share Patricia Thompson’s journey of teaching Agile in schools, the “triumphs and enlightenment and how we adapted along the way.”