Re: PO at retro
"Sivaraman Ganapathy Krishnamoorthy [email protected] [SCRUMDEVELOPMENT]" <[email protected]> Fri, 24 Feb 2017 21:54:52 +0530
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <CAAjZPpssrLAyf85psJcORka=CiA9gt0FYBGVMt8k_V79h=7mZw@mail.gmail.com> |
My experience : Retro must have PO included. When I taken over as a Scrum Master for the existing team and found during retro w.o PO - due to the misunderstanding between PO and team. When I checked with the team for the reason, got a feedback that he tried to boss over all of them and didn't discuss in details of stories. So I talked to the PO and insist on the need to explain in details of the US and his presence in the retro for the improvement of performance of the team. Believe me, it did wonder from the next sprint. Regards Siva On Fri, Feb 24, 2017 at 4:43 AM, 'Jean Richardson' [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote: > > > I’m having the “should the Product Owner be at the retrospective” > conversation again. While, years ago, the Product Owner was optional in > this meeting, a fair amount of learning has happened since then and a range > of resources has come out advocating that the PO be present—not optional. > The current edition of the Scrum Guide doesn’t help much here by referring > only to the “Scrum Team” in the section on the retro, but, then again, > maybe that’s intentional, and the Ken and Jeff now believe, based on > feedback and experiments, that the PO should be present at the retro as a > matter of course. > > > > In a situation where the relationship is not good between the PO and the > Development Team of the PO and the SM, I’m wondering about the quality of a > retro where the PO is not optional, but a required attendee. The guidance > I typically give is that the purpose of the review is to inspect the > increment and the purpose of the retro is for the team to inspect their > work processes. The most intimates changes are often within the team, and > those conversations require privacy and confidentiality to those present > unless those present determine otherwise. Therefore, I still am reasoning > that the PO is optional and included with the agreement of the Development > Team. > > > > Thoughts? References? > > > > --- Jean > > > > > > *[image: gate.site.jpg]* > > > *Jean Richardson* > > Azure Gate Consulting > > *~ **Repatterning the Human Experience of Work* > > > > *AzureGate.net* > > (503) 788-8998 > > [email protected] > <http://../../../../../../Documents%20and%20Settings/lisa/My%20Documents/CLIENT%20FILES/Jean%20Richardson/[email protected]> > > > > > > > > >
image001.jpg
(image/jpeg, 4.8 KB) - not displayed