Your team doesn't want to run retrospectives? Here's what to do.

[@TheAgileBroadcast]

Great tip, thanks for sharing! Interesting to hear you say at the end that "the retro is not just product oriented, but also process oriented". In my experience, I see the opposite problem! Most people I see tend to focus the retro on internal process topics, on how to get the team to work better together and ignore the product all together (they are thinking, that's the PO or business people to think about - it's not my job)... if I were to make a video on retrospective, I would probably use a similar sentence but in reverse ;-)

[@RetriumHQ]

That is a great insight! Especially as more industries outside of development start to implement agile thinking, it is important to focus on the retrospective as a tool on multiple levels.

[@TheAgileBroadcast]

@@RetriumHQ Yes. Even withing the software development world though. For a product company, it might be more natural to focus on the product, but for a services company where work is project-based, the "product" sadly becomes someone else's problem (the client). Different context, different battles I guess ;-)