There’s an Extreme Programming concept, tool, practice that many have forgotten. Sure, we remember user stories, refactoring, TDD, continuous integration, and pair-programming among the more popular XP practices.
But there are some that were quite useful and meaningful that we’ve misplaced. One of them is release planning as described in the Planning Extreme Programming book by Kent Beck and Martin Fowler.
Another is the notion of “Yesterday’s Weather”, which is a much simpler concept. I want to focus on it though as a powerful thinking tool for today’s agile teams.
I saw a picture tweeted by Alex Yakima with this picture of the RTE Canvas and it inspired me to talk about this role more.
You can find the tweet here - https://twitter.com/alexyakyma/status/793491699515273216
In the canvas, he highlights five key responsibility areas for the Release Train Engineer. They are:
- Program Increment
- ART Success Indicators
- Improvement Roadmap
- Coaching & Education
I was writing another blog post about the lack of an agile engagement having a cohesive coaching team and it dawned on me that I’ve never shared what an agile coaching team might look like.
Given that inspiration, I thought I’d spend a few minutes discussing aspects of creating (finding, forming, and building) a great team of coaches for a larger-scale, agile transformation initiative.
I honestly don’t know where the quote comes from, but I’ve heard that in order for you to become a great leader, you need first to become a great follower. That by following, and putting on the mindset of service, you better understand leadership.
In our last Meta-cast, Josh Anderson and I explored the good and the bad around defining roles and responsibilities in agile contexts.
It’s a mixed bag really that requires some common sense and nuance. I think we landed on the need for them, but caution around the negative effects that they can have IF you’re trying to create a healthy instance of self-directed agile teams.
One place to start is looking at the Scrum Guide and how it handles the Scrum roles.
Beyond the basic definitions of the roles, I really like the collaboration advice given BETWEEN the roles. I’ve found that it’s the interplay between the Team, Product Owner, and ScrumMaster that really makes the difference in high-level team performance.
I’d recommend you read (and share) the guidance in the Scrum Guide.
My friend and colleague, Lee Eason, recent wrote a post entitled – Redefining Success in a Post Agile World. In it, he generally shared thoughts around the evolution occurring (and needed) in the agile community towards understanding and delivering on business factors.
First, I want to congratulate Lee on a thoughtful and well-written article. I look forward to those moments when Lee shares his thoughts. While they are infrequent, they are important and timely observations from an agile practitioner in the trenches.
However, I do want to react and add a perspective to Lee’s. One that I think he may have underemphasized or missed altogether.
Here’s a snippet from his closing thoughts:
I attended an agile coach’s gathering about a year or more ago. It was a “coaching the coaches” session and it was very valuable. But an aspect of it has stuck with me ever since. One that I’ve mulled over and over and would like to share.
There were a group of coaches in attendance from the same client engagement, a large, multi-billion-dollar organization that had been going Agile for a couple of years.
When they decided to go agile, one of the first things the client did was reach out to an agile coaching firm for help. On the surface, that sounds like a good thing to do. However, the firm was largely staff augmentation focused, so that was their background and comfort zone.
I’ve been doing more pairing lately. Much more.
I’ve been trying it in my conference workshops and talks. Pairing with Mary Thorn quite a bit on the agile quality and testing side of things. I’m also pairing with Josh Anderson on our Meta-cast and I’ve done a few presentations with him. Very enjoyable.
I’ve also been pairing more in my writing. For years, I’ve been a lone wolf writer. Nobody but myself saw my writing before it entered the light of day. But now, I’m learning the value of having reviewers and editors. Second opinions matter. A second set of eyes matter. And having a partner in your endeavors can be quite a bit of fun.
An example of this is Mary Thorn being my “Chief Story Teller” in my 3-Pillars book. We had a blast writing the book and her stories complimented my own experiences to give readers two sides to many coins.
Tanner Wortham is a ScrumMaster and coach who I’ve quoted on this blog before. He recently wrote a blog post entitled: When Can a ScrumMaster Say No which I read with interest.
I’ve been sharing of late around the notion of more prescriptive coaching stances and, at least in my mind, this seeps into the role of ScrumMaster. So I wanted to hear what Tanner had to say.
Here’s a snippet from the article:
[…] Doing away with the sprint review simply ignores the problem. Help the team experiment with new ways to conduct the review but that align with the intent. Over time, they will find their solution. At no point did we have to say no. In fact, we should avoid it. I believe our responsibility is to understand and to guide. Rarely is it to deny.
Even so, I occasionally encountered two situations where I’ll say no as a Scrum Master:
I’ve been presenting at conferences for years. Over 20 years to more precise.
One of the common occurrences is that someone points out a typo or grammatical error on one of my slides in the comment section of the feedback form. I recently had this happen in a Certified Agile Leadership class. One of the feedback post-it notes on the first day pointed out a few typos. While I appreciate the feedback, I often wonder if there is more feedback than simply minutia…
If you read the feedback on Amazon for my Scrum Product Ownership book, some of the reviewers say the same thing. They talk about copy edit quality and the errors. These folks are right. I should have spent more time and money on the editing process. But if you look at the vast majority of the reviewers, they seemed to have overlooked those mistakes and received great value from the book.
And the detractors really seem to rate the book much lower based on the simple errors, simply overlooking the real value of the book. It’s as if they can’t see the forest for the trees.
As the instructor walked us through the exercise, he made it clear that “it depends” was not an acceptable answer. I asked if we could say “I don’t know”. And that was unacceptable as well.
It seemed that his only view of a viable answer to leadership was to provide a historical, trended data forecast. To give them as specific a timeframe as possible and lightly couch the risks associated with the estimate.
His primary driver for this position seemed to be that:
If we didn’t give them a specific forecast, they would go to someone (another team, another organization, offshore firm, nearshore firm, outsourced, etc.) that would make a more specific commitment.
I.e., that because we’re afraid of losing the “bid”, we have to provide something to win their confidence and win the work. No matter the level of confidence or runway we have in our historical “velocity-based” data.