In May of 2018, I published this Back to Basics post -
The intent was to refocus attention back to some of the original thinking and mindset of the early days of agile. Not to sound too nostalgic, but life was much simpler then.
I want to add to the list I shared then:
If you want to get back to the roots of agility I encourage you to research the following…
And you might want to investigate how Spotify is implementing agile practices. Not putting them up on a pedestal but considering them a role model for learning the basics of agility in practice. https://www.infoq.com/news/2016/10/no-spotify-model
Since agile methods have become a mainstream approach to software development, the coaching of agile teams is a HOT topic and role.
It seems as if EVERYONE is an agile coach nowadays. And I literally mean, everyone! I see people leaving a 2-day ScrumMaster certification class and then hanging out a shingle as a coach.
Or someone with 1-2 years of experience. But I digress.
I’ve already recommended Lyssa Adkins book in the ScrumMaster book list. But it certainly applies here as well. I’m just not going to count it against my quota ;-)
First of all, it’s been far too long for me writing something about metrics. It’s one of those topics in the agile community that keeps on giving ;-)
But I’ve been inspired (yet again) by an article that Anthony Crain wrote a while back on the topic. He introduced it as his QPPE Metrics Model, where:
Q – represents Quality,
P – represents Predictability,
P – represents Productivity, and
E – represents Engagement.
You can find the article here –
I shared this article with my friend and colleague, Shaun Bradshaw. I’ve known Shaun for the better part of two decades and he’s my go-to guy when it comes to all thing’s metrics related. Here’s his initial reaction to the QPPE post:
If you’ve read any of my work, you probably know that this role is incredibly near and dear to my heart. I’ve written a book about it. About 50% of my agile coaching revolves around aspects of product ownership. And if you search my blog, you’ll see many references to the role and activities surrounding it. For example, backlog grooming or refinement.
So, it’s hard for me to be unbiased on the topic, but I’ll try my best. And it’s even harder to keep my recommended list limited to three.
The ScrumMaster role is one of those that is simple and complex at the same time. I often speak in terms of doing agile and being agile, and the ScrumMaster role strongly influences their teams in both of those dimensions. Of course, the latter being much more difficult to manage and get right.
The good news in this space is that there are a few really solid books that explore this important role within Scrum.
I’ve been blogging for quite a while, but I just realized that I have rarely (never) made recommendations for agile books to read as part of your learning journey. And as an author, I’m surprised at myself for this gap. A gap that I intend to start closing with this post.
My inspiration for starting to share on great books comes from Jeff Payne, who shared a similar post here - https://www.techwell.com/techwell-insights/2018/03/3-must-read-books-good-agile-foundation
And this isn’t the end, but only the beginning. Look for the occasional post about learning advice for various aspects of your journey. Starting with this one…from the beginning.