Retrospective and DoR — Panda Story — Episode #02

Retrospective and DoR — Panda Story — Episode #02

In the afternoon of the day is the Team Restrospective. Howard has prepared himself to take this chance to reflect on the last sprint. He was particularly concerned about how the refinement should proceed. He is now sure that the way to go — completely on efficiency — was not the right one. But he doesn’t want to give up the reins completely. He believes that a definition of Ready (DoR) could help to create a balance. For the first time the product owner will be present at the retrospective. The development team had not allowed him to be there before and he didn’t mind. This time Howard has explicitly invited him to come, to give the whole Scrum Team the opportunity to improve.

At the beginning of the Retrospective each member of the team presents their points. The Product Owner notes that he is disappointed that no thought was given to the alternative route calculation during the sprint. The Development Team is disappointed that the commitment of the Sprint could not be fulfilled. Even before there can be any analysis or discussion in the Scrum Team, Howard suggests, rather he insists on developing a Definition of Ready. He also already has a first draft with him, which looks like this:

DoR:

· PBI (Product Backlog Item) are primarily written as a user story including acceptance criteria

· PBI are estimated

· PBI have a value

Howard has reflected on everything that happened in the last few days during the Sprint together with Britta. For that reason he decides to explain the first point again to the team. He thinks it makes sense to use user stories as PBI format whenever a direct customer benefit is addressed. He knows that it was a mistake to demand that all acceptance criteria must come from the product owner. In the course of this, he presents the three Cs that he believes are a good way to develop user stories together with the team.

The Three Cs stand for:

· CARD

· CONVERSATION

· CONFIRMATION

Especially the second C is dealt with more explicitly by Howard, he remembers Britta and her comment about the Agile Manifesto. He wishes that every PBI or User Story is talked about at least once. Thus a promise for communication. Also, this communication now makes it much easier for the Product Owner, together with the Development Team, to develop the acceptance criteria (the third C) for the User Stories during Refinement, after they have discussed the function of the User Story. For this purpose, Howard has brought the Story Card, the first C of the three C’s. He suggests using this card, including a template for user stories.

As a < type of user >, I want < some goal > so that < some reason >. Howard explains, the Product Owner is the expert for the benefit, the team for the function. During the Refinement, the development team gives input on the function, because often there is a better or different function that better fulfils the benefit.

Howard is satisfied with the result of the retrospective, the team has a DoR and the user story problem is solved. In the cafeteria he tells Britta about the retrospective and the DoR. He hopes that Britta sees it the same way and that the product owner has understood that PBIs which do not comply with the DoR will not be taken into the Sprint.

Britta is pleased with the progress Howard is making and his first retrospective with the team. Britta again encourages Howard to reflect on the Agile Manifesto in relation to the DoR and his demand to the Product Owner.

Zur deutschen Version / find the german version here