Retrospectives

[Smitha Joseph]

Could some help with insight into how to begin to include the POs in retrospectives. Do we need to schedule a separate, shorter retro for them to participate, and what kind of mechanism for them to provide feedback on the sprint itself, aside from the demo.  Would be great if someone can suggest options to assist.

[Robert Wen_Cprime_]

Wait, why is the PO left out of the retrospective?  Aren't they a part of the team?

[Smitha Joseph]

The Tech Architect too wants to be a part of the retro to provide feedback on sprint apart from the demo feedback 

[Robert Wen_Cprime_]

Maybe it's best for you to explain how you operate your sprints.  Who (as in roles) is on your team, full-time and part-time?  They should be in the retrospective.

The idea of the retrospective is to evaluate how the entire team performed during the sprint.  What went well for the team, what didn't go well, and what improvements are needed.

[Smitha Joseph]

@Robert Wen_Cprime_ : some scrum team included the PO in retro and some just the SM, Developers & QA team but not the architects and rest .. 

[Robert Wen_Cprime_]

Let's start with whoever wants to help the team continuously improve (architects, PO, etc) should be going to the retrospective.  There shouldn't be a need to have a "separate" meeting.  This would then apply to all your scrum teams.

[Smitha Joseph]

Thanks @Robert Wen_Cprime_ for that insight. The DEV team is quite reluctant to open up when the audience is larger