Hot answers tagged

5

Is this a standard or good practice in facilitating a retro to 'censor' known issues like this? Yes and no. I feel it's wrong to censor anything, especially talking about impediments at a retrospective. On the other hand, discussing the whole issue again and again and again when nothing has changed is unproductive and wasteful. As an example: in my old ...


4

Since you are in agile, I would treat this as new information discovered about the project and change/update User Stories / sub tasks. You are still doing a website development, so the basis of the project is the same and the team will be the same. Concerning the morale aspect. I would try some of the following (which may help in different areas) ...


3

Putting scrum aside, is the application written in a flexible manner? Although scrum welcomes change, the way the application was written should be flexible as well up to some extent. if it is too rigid at the very early beginning, you should rethink how to cope with future change requests. Second note, i had seen scrum being abused about change. Even though ...


3

The Scrum team alone cannot solve every impediment. It is a good idea to have some kind of escalation path for issues that are outside of the control of the team, but are recurring and damaging. As a Scrum Master I would often look to escalate this kind of issue using a reporting process. For example, I might produce a sprint report that says something ...


2

A retrospective should not ban topics. And a retrospective must not waste people's time, either. With that said, what you could do is categorise the retrospective items according to different influence categories: Items the team can change Items the team can influence Everything else / Items the team needs to accept Once you have done that, the team ...


1

If the same impediment is being raised Sprint after Sprint, that brings up a few questions. Is someone actively working on resolving the impediment? Maybe it can't be resolved within the Scrum Team and maybe it can't be resolved in a Sprint, but what is being done to minimize its impact and ultimately resolve the underlying issues? During Sprint Planning, ...


1

Censoring an impediment from the retrospective doesn't solve it. As it looks to be a major impediment that's blocking the team, maybe it's worthwhile to arrange a separate meeting to analyze the problem to get a shared understanding and find a way out of the impediment? The advantages of planning a specific meeting are: You can focus on the impediment and ...


1

Here are few suggestions, which you can bring together or one-by-one. SUGGESTION 1: Bring awarding best team member of the sprint in your Retro: Ask the team to vote during Retro Collect vote in room by raising hands Use vote box to vote for best developer / tester of the Sprint Before Retro, run a survey to collect Instead of asking for a single rating ...


1

Indeed Retromat is very inspirational for spicing up the Retrospectives for your developers. But at some point I faced the same issue of minor effectiveness in my team -after one year of working together, after 20 retros .. - so I started as well to think about some solutions to get higher again the attention level. Discussion was going not really somewhere ...


1

I'd look at the 5-stage retrospective approach. Retromat provides a lot of different activities that you can use for each stage. Also, there should be experimental changes (usually limited to 1 or 2) that come out of the retro with a clear idea of what should improve. These should also be reviewed at the beginning of the next retro. As long as they are ...


Only top voted, non community-wiki answers of a minimum length are eligible