I've seen a lot of discussion around performance metrics and trying to understand the progress of the team.
I think we need to think back to the Agile Manifesto for guidance in this area.
Working software is the primary measure of progress.
Now, let me make a little disclaimer.
If you don't work on a software team, just replace that word software with products or whatever it is that you make.
But whatever that is, it's actually working finished, whatever that product is, that's the primary measure of progress.
So, it is important for the team to keep in mind, working software is the priority measure progress, and if our goal is to get as much working over the
finish line as possible, what would we need to do to that here in this sprint?
that should be the focus of the daily Scrum.
My favorite technique to facilitate a daily scrum is to in some way shape or form project the sprint backlog.
Now that if I'm using something like Jira or some software tool I can probably put that up on a screen somewhere.
If it's not if i'm, using more of a physical board hopefully I, can roll that into the the room so people can view it.
Either way, I want the focus to shift from person to the commitment that we've made.
Our sprint backlog is the plan that put together in sprint planning.
It's what we all looked each other in the eye and said, hey, we're gonna get this work done.
I've got your back on this.
Uh, i'm gonna hold you accountable to getting this done, will you hold me accountable as well?
We're a team, were gonna accomplish this together.
So why wouldn't we focus on that every day in our daily scrum?
If you do that, then you can take a look at what items are in process at the time, talk about what needs to be done to get those across the finish line.
If if you've taken my earlier suggestion to put in place a whip limit, a work in-process limit that becomes even easier to have that discussion because
we're not pulling a new item into in processes until we finish one of the previous ones.
So the focus of the team becomes, what can I do to help get this across the finish line?
That's the conversation I wanna have in a daily scrum.
That what I want the teams to understand is the point of why we're here.
So feel free to use that, feel to experiment with that.
Or if you don't, if use some other technique, great.
If something's not working, that should be built into the DNA of you and of your team.
Hey, this isn't working.
We have to try something new.
Let's run an experiment, and then let's inspect and adapt afterwards.
So, if you're going to abandon the three questions, maybe try walking the board.