It's a question I get all the time. Should the Product Owner take part in your retrospectives?
If you're running retrospectives and your team just doesn't care, whatever you do, don't skip the retrospective!
Elizabeth Harrin is a career project and program manager. In addition to running the award-winning blog A Girl's Guide to Project Management, Elizabeth is the Director of The Otobos Group (a communications consultancy) and the author of Social Media for Project Managers, Customer-Centric Project Management, and Shortcuts To Success: Project Management in the Real World (now in its second edition). She has been named Computer Weekly's Blogger of the Year and IT Professional Blogger of the Year.
Kane Mar is the co-founder and principle consultant for Scrumology. He has been involved in the Agile community since 2001, initially as a developer and later as a professional Scrum Coach and Trainer. Kane Mar studied and worked with Ken Schweber (co-creator of Scrum) and was one of the first accredited Certified Scrum Master and Certified Scrum Trainer worldwide. Kane Mar is highly regarded as one of the most experienced and leading exponents of Scrum.
What's the difference between a sprint review, a sprint demo, and a retrospective? For beginners to scrum (and even for some who are more experienced), it can be hard to tell them apart. But they are distinct, and if your scrum team is to succeed, it is critically important to understand the differences.
Does your team run retrospectives sprint after sprint, only to make the same mistakes again and again? Are your retrospectives a chance to complain, and nothing more? Does your team mentally check out of your retrospectives before they even start?