33

TLDR: The team should be a team. We are not 'shamed' [...] developers don't want to look bad See the problem here? Whether or not your developers are being 'shamed', your developers are afraid of being shamed. That's not conducive to productive work. Is it a good idea to show 'story points by developer' graphs at their retrospectives? There is a 99% ...


11

TL;DR Your organization is fundamentally misusing the story point metric, and also conflating story points with velocity (which is also being misused). Please stop doing those things before you destroy your team cohesion and invalidate the potential effectiveness of the metrics that you could reap if they were used properly. Story Points Reflect Relative ...


10

TL;DR: Maybe you're having a XY problem. Retros are a tool for a means, not a means in itself. As yourself: Why are you asking around if the team has retros? Chances are, this question is a shortcut for a longer, more complex question similar to "how is the team materialising actual, concrete inspection and adaptation on a frequent basis? How are these ...


7

Retrospective actions are a vital part of the Sprint work, so they should be agreed with PO and tracked as such. You mentioned you use a Kanban board. Why not tracking each action as an item in the board? You may want to have a mean to separate these items from the other Stories, but it all boils down to what works better for you. In our team, we use a ...


6

I worked in an organisation some years back that decided to try and do performance reviews based on the number of story points delivered by individual developers. It was a complete disaster: the output of the team dropped dramatically. Developers were purely focused on doing the stories they were assigned and they stopped helping each other. There were a ...


5

Fundamentally, improvement is a part of any serious organizational process. Reflection and improvement is the only practice mandated in the Manifesto for Agile Software Development. It's also embodied in ISO 9001 (and all of its derivatives), CMMI, The Toyota Way, and more. That said, these events may have many different names and take different forms. They ...


5

Successful Retrospectives are for Communication and Collaboration Setting aside the fact that at least some of your agenda items seem like they are intrinsically Scrum anti-patterns (please ask why in a separate-but-linked question if you really want to know), you and the team are approaching the Sprint Retrospective event incorrectly by treating it ...


4

First, there are many ways to reflect and adapt apart from a Scrum "retrospective". However, those should be readily evident. If I take your post at face value, I have to assume there is no time set aside for reflection and improvement. This would be a big red flag for me. There are whole books written about this, but the take-away from all of them ...


4

TL;DR A Sprint Retrospective is part of the inspect-and-adapt process. The 2020 Scrum Guide says that "[t]he most impactful improvements are addressed as soon as possible," but doesn't prescribe how the team must implement any given adaptation. The whole Scrum Team is collectively responsible for working together to decide how to best implement ...


3

There are two different aspects that you want to focus on in this retrospective: product failure and the work team members have put in. For product failure, one format could be a timeline of all the product decisions taken during the project. Collect data of all the things that have happened with the product, decisions take, feedback received, etc., and map ...


3

Two cases come to my mind Is everyone ok with you sharing the information? Does it make sense to share all information? Once you clarify that everyone is ok with sharing that information and you decide that it's a valuable information to share, great. My suggestion in how to share them would be based in a bullet from this answer Do a retrospectives on how ...


3

It's interesting that you say "the company" does does not have retros. Could that mean it's a matter of policy not to have them, or does it just mean all of the teams at this company choose not to do retros? That seems like an important distinction. Retros are for the benefit of the team and each team should choose when to have them. Teams do ...


3

The purpose of the Sprint Retrospective is for the team to "plan ways to increase quality and effectiveness", and this is done by inspecting the last Sprint in the context of "individuals, interactions, processes, tools, and their Definition of Done". There are any number of tools, techniques, or pieces of information that can help the ...


1

I find it difficult to see a business purpose for this kind of statistic: presumably, all of the developers are "on the same team." It should be entirely natural that different people focus on different concerns fairly-fluidly at different times. Therefore, I see no positive benefit for presenting this measurement, and possible unwanted social-...


1

I echo the other answers, and will just add a couple of thoughts. The primary question is, are the teams meeting their performance objectives? If not, by definition they need to improve, and some form of reflect-and-adapt meeting like Thomas Owens mentioned needs to happen on a regular basis, at least monthly. (If the company does not have performance ...


1

I'm assuming you are using Scrum. For a team that is relatively new to Scrum, the initial few retrospectives are more about learning to solve problems themselves than actually solving lots of problems. Are you in the Scrum Master role? If you are, then you could research some potential retrospective formats. Probably the most common of these is to gather ...


1

TL;DR Agile frameworks like Scrum are founded on empirical control and validated learning, so "failing fast" is not inherently a negative. In fact, canceling a project that can't be salvaged is often the best way to avoid chasing sunk costs. However, understanding the Five W's of the failed project can lead to process improvements if and only if ...


1

You're conflating several competing objectives here. Celebrating the hard work or worrying about future, less challenging work is not an objective of a retrospective. If you want to celebrate the work performed, then go celebrate. That would involve food, drink, and someplace nice to socialize. If you want to worry about future work, that would involve ...


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