Information choking - Leads to project arrests
In general many projects fail because information is not properly distributed among team members. Customer's intent is not known to the team. This is a major project killer.
Everyone agrees it is good for project team to know all the information about their work. But practically it is not the case. Why does information is blocked? There can be multiple reasons for this. Way to hell is paved with good intentions?
1. Work more efficiently:
Lean theories explain this in a very nice way. Many times product owners start to think making everyone work is more important than completing the sprint. It is myopic vision but people to succumb to it many time. Who is ready to contest the theory 1 + 1 = 2. So if a person is idle for a day then that effort is wasted.
Why waste time with a team meeting discussing the sprint. People will spend time on items which they are not going to work. Isn't it waste of time?
But this results in rework. As lean ideas tell concentrate on the goal. What is deliverable? Deliverable is the sprint. Project team knows best how to deliver. As a team member I know what are my strengths and how fast I can deliver the promise. When I know the plan for the sprint I also know how to plan my activities.
Efficiency bug bites the product owner and then instead of pull things gets pushed to the team. Based on some logic product owner starts assigning tasks. This results in drop of efficiency.
2. Distracted Product owner:
This is a dangerous situation. Based on the customer demand project team is expanded. Now product owner is not able to spend enough time with the team. Some people will identify the situation quickly. But others will notice the situation when things start going down the drain.
3. Fear of loosing control:
Even product owner is a human. Many times job situations threaten them. Unconsciously they start keeping information to themselves. They start giving justification why they kept some information hidden. This is another scenario which is difficult to identify. Project team does not know there is some information missing.
This situation can be identified in the retrospective. If the issues identified are due to missing information it is better to make product owner conscious about it.
Everyone agrees it is good for project team to know all the information about their work. But practically it is not the case. Why does information is blocked? There can be multiple reasons for this. Way to hell is paved with good intentions?
1. Work more efficiently:
Lean theories explain this in a very nice way. Many times product owners start to think making everyone work is more important than completing the sprint. It is myopic vision but people to succumb to it many time. Who is ready to contest the theory 1 + 1 = 2. So if a person is idle for a day then that effort is wasted.
Why waste time with a team meeting discussing the sprint. People will spend time on items which they are not going to work. Isn't it waste of time?
But this results in rework. As lean ideas tell concentrate on the goal. What is deliverable? Deliverable is the sprint. Project team knows best how to deliver. As a team member I know what are my strengths and how fast I can deliver the promise. When I know the plan for the sprint I also know how to plan my activities.
Efficiency bug bites the product owner and then instead of pull things gets pushed to the team. Based on some logic product owner starts assigning tasks. This results in drop of efficiency.
2. Distracted Product owner:
This is a dangerous situation. Based on the customer demand project team is expanded. Now product owner is not able to spend enough time with the team. Some people will identify the situation quickly. But others will notice the situation when things start going down the drain.
3. Fear of loosing control:
Even product owner is a human. Many times job situations threaten them. Unconsciously they start keeping information to themselves. They start giving justification why they kept some information hidden. This is another scenario which is difficult to identify. Project team does not know there is some information missing.
This situation can be identified in the retrospective. If the issues identified are due to missing information it is better to make product owner conscious about it.
Comments
Post a Comment