When problems in a retrospective usually have a preset idea and the causes that may be occurring. This leads us to ask many times what we think is the solution as the problem or disability that we solve.
However, I believe we should bring the retrospective the real need we have, what if we succeed, we do our jobs better. That need is to be shared with the team so together, find possible causes that will not happen.
In a complex system as a software development ( Management 3.0 ), the cause-effect is not linear. Things that happen can have more than one cause, and therefore not always trigger the same causes the same effects. This complexity adds more value to analyze the problems for the team, with greater vision that only one person. If you plant your team needs you can not get it is easier to find the causes collaboratively.
In short, you could raise ideal situations rather than problems . And find out how to get to that situation by removing the causes that will prevent it. Do not favor this learning and shared vision, setting the goal before the road?
I also would like to share some ideas I been obtained over a few flashbacks (just over two years, at least every 15 days ,...):
- always think first that the problem is systemic, not people. Solve the system first, it usually limited to people.
- not avoid conflict, creates a healthy environment where they bloom. Raises
- needs to be solved, not what we think are the causes. This also helps to eliminate the position of "guilty"
- retrospective Learn techniques and know when to apply each. Help, a lot.
- Brainstorming is the most known and poorly implemented. Set clear rules from the beginning to do well: it eliminates the criticism that prevent real freedom of ideas. Always get
- actions of retrospectives, or will not be retrospective, single session of relief. " Are not bad from time to time, but those with beer in your hand much better.
0 comments:
Post a Comment