Comments by "" (@ContinuousDelivery) on "Tips for Retrospectives | A Chat with Aino Corry" video.

Thank you to Aino for being such a great guest!
12
Ignoring the purjorative comment "failed programmers", and reading it rather as "former programmers", my real answer is that I don't know. I am a current programmer, and I guess, sometimes a coach, though I probably do less programming than I would prefer. Many coaches do come to coaching from programming, finding that they enjoy the coaching more, or that they can contribute more through coaching than through programming. I know many coaches that also came from other routes though, so no idea which route is more common. I guess that it is pretty obvious that a reasonable proportion of coaches started off as programminers, in the same way that a reasonable proportion of football coaches started off as footballers. Playing the game gives you a different kind of insight into the game.
7
Hmmm, and I thought that Jagermeister was its own problem 🤔 😁
4
I think that it is a failed retrospective if it is used to assign blame to people. The object of a retro is to identify common problems, or current blocks to progress and agree how to fix them. It should be much more "what lessons can we learn" than "who can we blame". I agree with you that there is an important place for "trusted private conversations", but they serve a different role I think.
2
As well as Barry O'Reilly's stuff, several of my videos talk about this topic, not necessarily about how to apply that to 'people' but certainly for some of the more technical aspects of development, here are a few suggestions, but there are many more on the channel. Experimenting at SpaceX drives 'Engineering' https://youtu.be/v8f6q4ruvds (These are amongst my first videos, the sound has got a lot better since then!) Experimenting with releases https://youtu.be/r_E3OyOCvV8 Experimenting with product design https://youtu.be/iV81CHby3r0
2
We had fun recording it, thanks.
1
Yes, I think it is the same idea 🤣
1