B (3:30)

Right.

A (3:30)

Because if you look at it, most history artifacts for a team are either version control commits or issue tracking items. None of those we will want to look back on very fondly and remember. Right. They are all things we want to get out of our way, put it in the past, done, check and never look at it. But looking at retrospectives can become that. Especially if you bring in into the retrospective some, some history, some identity building exercises that then get collated through the multiple retrospectives over time. So I really like that idea. And we used to do that very early on. Like this was my first Scrum team where we had all of our retrospective flip charts because it was of course, many years ago, so we were all on flip charts and we had the flip charts all over the room. It was a big room. And the flip charts kind of told the story of some of the key moments of the team over time. And that really helped to create identity and it also helped introduce new team members because we could just go to the board and point to it and kind of discuss what had been going on. Have you used your own retrospective maroboards as kind of a, let's call it the team museum as well?

B (4:52)

Yeah, you're absolutely spot on. We do.

B (4:56)

We use them as a point of celebration. I think a couple of years back it wasn't myself that created it, but a previous Scrum master who was working on the team before I took over, had taken all of the boards and created a little end of year video. You know, put together a bit of a video using snapshots of the. The board and the. And the, the walked through the year, essentially providing little celebratory moments where we could come together and. And watch this video and see what we had done, all the good work that they had done throughout the year. So yeah, yeah, it's.

B (5:40)

A great way to do it. And another actually way of telling that story as well, which we use is collecting our Sprint goals in a single place and, you know, having a walkthrough of those Sprint goals at a certain point in time. It might be the end of the year, end of the financial year, you know, gives a great history. And also, like you said, new people joining the team. And it's fantastic for them to be able to see a snapshot of things like Sprint goals or retrospectives. And Sprint reviews is another one that we do it with. So we have a single PowerPoint pack which gets built upon each sprint and it tells the Story of it tells the story from a Sprint review perspective, which also of course includes stakeholders and people who join the organization or the team can go in and listen to those and hear back what's happened Sprint by sprint. Absolutely.

A (6:43)

Scott, thank you for sharing that. That was a great intro to a different aspect of the retrospective. Right. Like the logistics of how we collect information over time. But of course we do this retros because we want to help the team succeed and ourselves. We want to succeed as Scrum Masters. So share with us. Scott, when you think about yourself as a Scrum Master, how do you define success?

B (7:09)

For me, always come back to the people and the human aspects of it. So as a Scrum Master, you're there in that servant leadership role. And if the team is thriving, so not just growing, but if the team is really thriving, then I feel that is a huge indication of success. And when I talk to the team, I mean that includes the product owner as well as, you know, the devs. So you're not only helping those on the ground, but they're doing the technical work, but also that product owner is important in that journey too.

A (7:55)

Yeah, absolutely. When you think about this idea, is the team thriving? That's a great question to start with and to start reflecting on. But how do you, Scott, how do you define that? How do you explore that question? What things do you look at? Do you keep any metrics? Do you journal regularly? How do you keep tabs on the answer to the question, is the team thriving?

B (8:19)

Yeah, sure. So we keep, we do light touch on a regular basis as opposed to having sort of checkpoints every quarter or something like that. Although we do have those checkpoints because we do quarterly planning. But on a sprint by sprint basis we will do things like mid sprint vibe checks. So we're in daily Scrum and we'll have a quick vibe check on how we're going on the sprint.

B (8:50)

So that doesn't necessarily tell you how the team's feeling or the team's health, but it tells you more about the health of the sprint. Perhaps. But we also then have quarterly planning where we do a retrospective. That's a point in time where we can check back and celebrate on the last quarter, see where we need to improve for next upcoming quarter and get a get a check in with the team in terms of how they're feeling, what their challenges are, what they're excited about, etc. And during that quarter we do a mid quarter vibe check. So that's more of.

B (9:33)

An anonymous survey where we will get a Bit of a pulse check on the health of the team. So really just half a dozen questions.

B (9:46)

To get a feel for how the team's tracking in terms of.

B (9:52)

Each individual. And it really gives us some pointers as to is there anything that we need to change?

B (10:00)

Is there anywhere we would need to pivot? So we have the, yeah, the quarterly check in the pulse and then we have our regular management who do their showcases each month. I suppose that's more of a show and tell.

B (10:19)

But you also hear a lot from the team during those showcases, which gives you a bit of an indication as to, you know, what's the excitement and the buzz around the department.

A (10:33)

So when you think about this, you call them vibe checks. So I guess these are kind of light, more kind of a question, maybe the fist of five type of checks. And when you think about that, the vibe checks that you do mid sprint and then the quarterly what kind of infrastructure have you put in place? For example, when you do the sprint vibe check, do you then somehow track that somewhere or like, how do you do it?

B (11:04)

So for the sprint vibe check we really take action there and then if someone raises an issue that we're not tracking towards a sprint goal or part of the sprint goal, then we'll talk about it during that daily scrum there. And then to understand what is it that we need to do next to ensure that we stay on track. And when we talk those sort of mid quarter vibe checks, where it's more of an anonymous survey, I'll collect the feedback. I will start to pull together some, remove any duplicates, create any themes that are, that are starting to show any patterns. I'll share that back to the department.

B (11:51)

And then co create, you know, working with them, the actions that we're going to take. And generally I'll perhaps be driving those, but working.

B (12:06)

With certain members of the team to be able to achieve any of the actions that come out of those vibe checks. Similarly, the quarterly planning, those actions are taken themes, any patterns looked for and again continually track those. And it's all about, you know, that continuous communication at certain points to let people know how we're tracking towards the actions that we've taken from the vibe check or the portal planning.

A (12:37)

And I really like the idea of tracking actions that we collect no matter when, of course, but then at those specific points when we actually do this, either mid sprint by check or then quarterly planning. And the reason for that is not because we want to track everything that is decided, that's not the goal, but rather that if you Keep that over time. You can see what kind of actions are relevant over time and you can observe the development of the team. Right. Like a team that is thriving will have certain needs. Like for example, a team that is thriving might need more support from management to continue to grow. A team that is not thriving will have internal problems with, will have basic things that are not in place. Like for example, lack of communication.

A (13:24)

Dependencies that are not handled, surprises mid sprint. Like all of those things. Right. A team that is thriving is looking forward, is trying to get better and we can see that in the actions. While a team that is not thriving will be worried about day to day things and that will also be visible in the actions. And with today's LLMs, I guess we could even probably create a score based on the actions tracked over time and kind of track that score over time.

B (13:53)

Yeah, great point. And LLMs is a big piece of what we in our department being AI, an AI domain do a lot of work with. So creating LLMs for various use cases across.

B (14:12)

Business. So that's another use case that we can take on.

A (14:17)

Absolutely. Thank you for sharing that with us, Scott.

B (14:20)

Thank you.

A (14:24)

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day we're talking access to over 700 hours of agile gold, CTO level strategy talks, summit keynotes, live workshops, E courses, Deep dive interviews, books. And if you're into no estimates, we got the pioneers of no estimates in those Deep Dive interviews as well. Agile Business Intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars, it's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community community that's shaping the future of Agile. And we have so much for you. So check out all the details@scrummastertoolbox.org membership because listening is great, it's important. But doing it together, that's next level. I'll see you in the community. Slack.

A (16:17)

We really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes. Share this podcast and let other Scrum Masters know about this valuable resource for their work. Remember that sharing is caring.