Food for Agile Thought #252
TL; DR: Resolving Team Conflict, Ikigai & Cynefin — Food for Agile Thought #252
Welcome to the 252nd edition of the Food for Agile Thought newsletter, shared with 26,787 peers. This week, we analyze options for resolving team conflict; we learn more about our team’s reason for being, and we think about how we are complicit in change fatigue.
We then advocate the unlearning of user stories, and we learn how to rejuvenate user growth by focusing on unlikely user groups. Moreover, we discover another five ways to tackle churn and improve retention.
Lastly, we embrace another help to get a hold on uncertainty and complexity with the Cynefin framework.
Did you miss last week’s Food for Agile Thought’s issue #251?
Do you want to get this article in your inbox? You can sign up here and join 26k other subscribers.
🏆 The Tip of the Week: Resolving Team Conflict
Mike Griffiths: 5 Tools for Team Conflict Resolution
Mike Griffiths analyzes five ways of resolving team conflict.
Source: 5 Tools for Team Conflict Resolution
Author: Mike Griffiths
Agile & Scrum
Jeff Gothelf: Ikigai — a formula for successful agile team leadership
Jeff Gothelf suggests a practice to learn the answer to the question of your team’s reason for being.
Source: Ikigai — a formula for successful agile team leadership
Author: Jeff Gothelf
Len Lagestee: Let’s Talk About Change Fatigue
Len Lagestee delves into how we contribute to our change fatigue and what we can do about it.
Source: Let’s Talk About Change Fatigue
Author: Len Lagestee
Harold Jarche: cynefin
Harold Jarche runs a retrospective on how the Cynefin framework has influenced his work.
Source: cynefin
Author: Harold Jarche
📅 🖥 Remote Agile Training from August 18 to September 1, 2020 — € 167
The Distributed Agile Masterclass addresses remote practices and tools for Scrum Masters, Agile Coaches, project managers, and Product Owners on how to facilitate agile events with distributed teams effectively.
The Remote Agile training class is organized in three blocks of 2.5 hours each over two weeks.
Looking for a different date? Back to the training schedule.
📅 🖥 💯 Learn more: Distributed Agile Masterclass — A Live Virtual Class.
If you are enjoying the article, please do me a favor and smack the 👏👏 👏 multiple times so other people can find it, too. Your support means the world to me!
If you prefer a notification by email, please sign-up for my weekly newsletterand join 26,787 peers.
Product & Lean
Matt Philip: Stop writing stories, start validating working software
Matt Philip advocates the unlearning of user stories.
Source: Stop writing stories, start validating working software
Author: Matt Philip
Bangaly Kaba: The Adjacent User Theory
Bangaly Kaba recalls how Instagram rejuvenated user growth by focusing on the Adjacent User Theory.
Source: The Adjacent User Theory
Author: Bangaly Kaba
Jason Evanish: Slaying Churn Monsters: 5 ways to reduce churn better than an exit survey
Jason Evanish shares five ways to tackle churn and improve retention.
Source: Slaying Churn Monsters: 5 ways to reduce churn better than an exit survey
Author: Jason Evanish
📯 Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate
Regularly, we find articles from developers detailing why ‘Agile’ in general and Scrum’s nature, in particular, deserve our collective disdain.
What has always struck me in this discussion is the emotionality. Scrum is a tool useful to accomplish one primary task: delivering value to customers of emergent products in complex environments while mitigating an organization’s exposure to risk at the same time. So, if Scrum is not working in an organization, maybe it is because Scrum is applied to the wrong cause in the first place. Or, that its application has been mechanical, driven by folks who don’t know what they are doing. (Seriously, how hard can Scrum be if the manual comprises of 18 pages, right?)
The question then is: Why would I “hate” a tool unsuited for the intended purpose or applied incompetently? Would I hate a hammer for not being capable of accurately driving a screw into a wooden beam? Probably not, as the hammer wasn’t designed for that purpose, and neither sheer will-power nor stamping with your feet will change the fact.
Read more: Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate.
🗞️ Last Week’s Food for Agile Thought Edition
📺 Join 2,300-plus Agile Peers on Youtube
Now available on the Age-of-Product Youtube channel:
✋ Do Not Miss Out: Join the 7,900-plus Strong ‘Hands-on Agile’ Slack Community
I invite you to join the “Hands-on Agile” Slack Community and enjoy the benefits of a fast-growing, vibrant community of agile practitioners from around the world.
If you like to join all you have to do now is provide your credentials via this Google form, and I will sign you up. By the way, it’s free.
🎓 Do You Want to Read more like this?
Well, then:
- 📰 Join 26,787 peers and sign-up for my weekly newsletter
- 🐦 Follow me on Twitter and subscribe to my blog Age of Product
- 💬 Alternatively, join 7,900-plus peers of the Slack team “Hands-on Agile” for free.
Food for Agile Thought #252: Resolving Team Conflict, Ikigai & Cynefin, Adjacent User Theory, Reducing Churn was first published on Age-of-Product.com.
