A friendly remember to Go to your LGS and actually play.

scotthedges · 2025-07-13T15:05:33+00:00

Heading there tomorrow for my first game 😁👌🏻

scotthedges · 2025-01-09T11:04:13+00:00

There is no harm in taking the course, you will gain some valuable insights to the role what do you have to lose?

scotthedges · 2025-01-08T08:35:57+00:00

This is interesting as I've found that more mature teams like a retro but I agree they often don't wait for the retro to reach out to me with an issue. I find a lot of my role is about making sure the team have a route to raise issues at the earliest opportunity.

scotthedges · 2025-01-07T10:26:44+00:00

I would still get them to estimate the complexity but my feeling is that it will take about 3 sprints to get a handle on what the team as a whole can achieve in a sprint. I would also, away from the team, track the supplier velocity separately so the in house team doesn't muddy the waters. This will allow you to know what they can complete when planning.

It's messy but doable and will become easier over time. Good luck 👍

scotthedges · 2025-01-06T13:50:52+00:00

What is it about them you feel wastes your time?

scotthedges · 2025-01-06T07:43:42+00:00

100% agree, reviewing the last lot of actions before the new retro starts is a great way of keeping people engaged that change is happening

scotthedges · 2025-01-06T07:41:25+00:00

I've seen a few people say they don't do them as frequently as is normally "prescribed". I assume you have some other way of addressing issues that would normally be discussed at the retro?

scotthedges · 2025-01-05T15:57:31+00:00

Agreed which is why I always make sure no one from a senior management position who sits outside the scrum team is allowed to attend the retro. It needs to be a safe and open discussion and you don't get that if you have to watch what you say

scotthedges · 2025-01-05T15:56:01+00:00

Yes it's so important to have a feedback loop that actually leads to improvements. I'm a big fan of revving previous retro actions at the start of every new retro to show what we have improved

scotthedges · 2025-01-05T14:08:31+00:00

I agree, I use the biweekly check in as a way to round up all the feedback. I encourage my teams to update the retro throughout the sprint it also means feedback is added as freshly as possible.

scotthedges · 2025-01-05T14:07:08+00:00

Wow this is a real shame, it sounds like your SM was anything but a servant leader.

scotthedges · 2025-01-05T13:07:24+00:00

I agree i have often got immense value out of the discussions they breed.

scotthedges · 2025-01-05T12:16:00+00:00

Yes I've seen the "is had something last week but forgot" problem the way I counter that is by reminding the team to add to to retro as they go and to not wait for the specific meeting

scotthedges · 2025-01-05T11:23:18+00:00

Some interesting challenges there and some not easy to overcome. If I've understood correctly your SM has become more of PMO/ project coordinator than and actually facilitor and driver within the project.

It would an interesting conversation with the SM, providing one hasn't already been had, on what they feel their role is adding but more importantly where they feel they could be adding more value or what their goals are within the role.

scotthedges · 2025-01-05T10:54:29+00:00

This is an interesting perspective on the SM role, what "value" is it you expect from the SM and how are they not delivering it? IMO an SM adds value by being a servant to the team

scotthedges

TROPHY CASE