this post was submitted on 06 Feb 2024
14 points (100.0% liked)
Ask Experienced Devs
1064 readers
1 users here now
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is it fair to say that your process has stabilized in a good place? It sounds like your team is happy with the current way of doing things.
Rather than a reactive retrospective, you could try running experiments. The ol "what if we stop doing x" or "do more of y".
Whenever I read about kanban, the author eventually talks about gathering metrics so the team can run experiments and see what happens to the metrics.
I think that's largely true. Not trying to assume intention, but I do think a few more of the junior folks on the team read something in a book or blog and think we have to do it that way. Or that it'll work for us because it worked for Etsy/Netflix/ThoughtWorks/etc.
You know, metrics might be a great way to discuss some of these concerns/ideas are coming up. For example, the topic on Jira was related to Cycle Time. If we were concerned about Cycle Time, changing how we use Jira for a few weeks would see what happened to the metrics.