Book Series: Scrum & XP From The Trenches
Ines Garcia
InesGarcia.me, Author, Speaker, Biomimicry, Circular Economy, Agile Coach, Climate Change Coach, Carbon Accounting, Salesforce MVP Hall of Fame - Empowering evolution (not revolution) - freelance. Check out my books! ??
This entry of My Book Series goes to the directors cut version of Scrum & XP From The Trenches by Henrik Kniberg.
How I Found it
Another book recommendation that has been mentioned in the Scrum Masters Toolkit Podcast with Vasco Duarte. (Thanks again for such a great food for thought podcast, highly recommended beyond agile professionals)
What it Tells me
One doesn't master something after two days training, no matter how hard you try and how witty you may be.
“Learn from the mistakes of others. You can't live long enough to make them all yourself.” Eleanor Roosevelt
Inspecting and adapting is the way to go. Digesting and practicing the principles for your context is what makes the difference. This includes experimenting with different tools and finding what works best in your context, "just make sure you are adapting the tool to your process and not vice versa".
The fact of this version being the authors own reflection from the content and learnings over the years, makes it priceless. I can see myself reflecting in a similar manner from earlier Scrum framework thoughts on new found knowledge to my experience now years later. (and I bet my future self will also say something similar)
Food for Thought
The thing is, the work that we do is quite conceptual. What I mean with that is that we create more than we recreate or duplicate. We transform from concept to tangible outcomes, screens, response, data processing … That is also true for other goods such as architecture, music, art etc. Unlike physical products, which we can see, smell, and touch; software is in a sense intangible.
There is more room for variety and creativity, and it is harder to imagine what the final outcome will look like. Oftentimes, we only realise what we want and what we don’t want after we see the final product.
There is little correlation in time spent with value delivered. Don't force people to anything. Don't outrun the slowest link in your chain, look at the architecture of your system (both product and organisation), and experiment to learn like there is no tomorrow.
https://twitter.com/Inescapinezka/status/1326555805060042752?s=20
Find more about the book and the author: https://www.infoq.com/minibooks/scrum-xp-from-the-trenches-2/