Skip to main content

Advice for two retrospectives in one sprint(without and with product owner)

I have done that !!!!
Many years ago i inherited a team which had lot of issues . The PO and team didn't trust each other.

I had my first retrospective with Product Owner (PO) alone and my second retrospective with team but without PO. Usually followed by a third retro meeting with PO and team . During the first two meetings PO and team talked about the issues they had with each other. I shared the feedback to each other along with my coaching and mentoring. During the third meeting we focused on the product and common issues which we could solve together. The focus was to create trust and transparency.

 I have seen this in many other teams also because of many reasons. Team members were not willing to talk about all the issues in front of PO because they don't trust the PO.

In my case after lot of coaching and mentoring both groups agreed to have a common retrospective. Soon we became one of the best teams in our group.

Retrospective is the meeting where everyone come together for the inspection of the previous sprint . This is a very important part of the empirical process. If team members don't trust each other then they will not speak openly. A coach/ScrumMaster will have to talk to the individuals to understand their concerns. Everyone should feel safe to speak in the meeting. Also ensure that no one blames anyone personally. Once you understand the problem you can act on it. you might not be able to make change in one day , It is a gradual process. Once you establish the trust with everyone including the team and PO they will be open to talk about the issues openly. When you reach this state you will end up having only one meeting with everyone. Once the team matures more you will find them talking about issues and take corrective actions as and when it is needed. They wont even wait for retrospective meetings.


Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed.

This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team.

Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process.

Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down.

If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also brainstorms idea…

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation.
In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can upd…

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices.

Some of the rules 

The roles of Scrum
•Scrum Master -
•Product Owner
•Feature TeamThe PDCA cycle ( )  frequent communication about risks (daily)
•Plan – Sprint planning
•Do – Actual engineering sprint – deliver a potential shippable code
•Check – Sprint review
•Act – Retrospective 
The scrum guide @ will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum.
Apart from these rest of the ceremonies and artifacts are there…