Root cause analysis for why so many meeting happens
One of the common issues that every organization is facing is too many meetings!!
Is it good or bad, we can easily find out using a technique called 5 whys!!
Lets take an example -
In a typical scrum environment, after the sprint planning is over, team is again meeting to clarify some more doubts
Why#1 - why are we meeting again to clarify requirement?
response - because when team actually started working on the requirement they found more questions/gaps.
Why#2 - why team did not come up with earlier during the sprint refinement/grooming meeting?
Response - because team were busy with the last sprint activities hence did not go through the requirement gaps.
Why#3 - Why Product owner could not realize these gaps earlier?
Response - because PO was busy with the other priorities and could not focus on the requirement to analyze it thoroughly
Why#4 - Why is Product owner is so busy when it is clearly defined role.
Response - Because Product owner is handling too many projects hence do not have time to go through each and every requirement in details.
Why#5 - Why is PO handling too many projects?
Response - because of the budget issues, organization is not hiring too many POs.
Whats the conclusion --> If people are asked to handle to many things then this type situation would occur often and meetings will happen. During the sprint we will still be clarifying requirement and resolving issues which could be easily avoided if PO is free from some of his/her responsibility.
Being Agile is not to do too many things fast, it means to do most important things right and fast.
Is it good or bad, we can easily find out using a technique called 5 whys!!
Lets take an example -
In a typical scrum environment, after the sprint planning is over, team is again meeting to clarify some more doubts
Why#1 - why are we meeting again to clarify requirement?
response - because when team actually started working on the requirement they found more questions/gaps.
Why#2 - why team did not come up with earlier during the sprint refinement/grooming meeting?
Response - because team were busy with the last sprint activities hence did not go through the requirement gaps.
Why#3 - Why Product owner could not realize these gaps earlier?
Response - because PO was busy with the other priorities and could not focus on the requirement to analyze it thoroughly
Why#4 - Why is Product owner is so busy when it is clearly defined role.
Response - Because Product owner is handling too many projects hence do not have time to go through each and every requirement in details.
Why#5 - Why is PO handling too many projects?
Response - because of the budget issues, organization is not hiring too many POs.
Whats the conclusion --> If people are asked to handle to many things then this type situation would occur often and meetings will happen. During the sprint we will still be clarifying requirement and resolving issues which could be easily avoided if PO is free from some of his/her responsibility.
Being Agile is not to do too many things fast, it means to do most important things right and fast.
Comments
Post a Comment