home.social

#scrum — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #scrum, aggregated by home.social.

  1. Retrospectives are a critical element in Scrum but they won't work well if your team hates them.

    It's natural that you have ideas and opinions on what the team could try to improve, but the moment you move to advocacy, the team loses trust in their facilitator. If they feel their facilitator has a personal position or opinion involved, they'll question whether the event is being run to help them, or to steer where the facilitator thinks they should go.

    But what about those times when you have ideas/issues that you feel are important to be discussed in the retrospective? Two of the four options in the post: Don't share the idea at all. If it is valuable for the team, someone else will come up with it. Or write your idea down and give it to another team member prior to the retrospective. It becomes their job to advocate on behalf of your idea and, during the event itself, you don't speak to it.

    While it's challenging when the facilitator is an active team member, having the team's manager or executive as the facilitator is far worse. Managers have power and, because of that power, participants won't feel safe being candid and honest when difficult subjects are discussed. Managers cannot facilitate retrospectives and, under most circumstances, they shouldn't even be in the room.

    Who facilitates your team's Retrospectives?

    agilepainrelief.com/blog/two-k

  2. An estimate is a qualified guess to help people make a decision about doing work. In the Agile world, one approach to estimation has become prevalent: the combination of Planning Poker and Story Points.

    Story Points are past time, according to Ron Jeffries and Chet Hendrickson, the people who created them. Hendrickson has said, "As one of the folks that sort of started all of this, let's say that it was the best we could think of in 1996, by 2001 we had discovered better ideas, and by now it should have been kicked to the curb long ago."

    The benefit of Story Points was the speed at which the numbers could be generated, but among their many faults was that they fail to make clear the uncertainty, they're often used as a commitment and, worse, for comparison of teams.

    If the people who created Story Points moved on by 2001, what keeps your team using them?

    agilepainrelief.com/glossary/e

Share on Mastodon

Enter the server where you have an account.