Feral Sunar // Allianz Türkiye - Agile Coach
As long as the path is the same, the point you reach is not much different. When the questions you ask are the same, the answers do not change. That's why it's good to change the questions from time to time.
Why aren't the cameras on during 'daily'?
Why can't we be 'brutally' transparent in 'retrospective' sessions?
Why are 'sprint planning' meetings getting longer and longer but the desired result is not achieved?
I could extend the list with these types of questions.
The question of why deepens the questioning in order to get to the root of the cause, but my mind is stuck: Could it be that this sometimes prevents me from seeing a 'clear enough' truth and going for a solution quickly and makes me slow it down?
Let me tell you the incident that led to the 'enlightenment' I experienced on this subject.
I did not receive detailed training on the use of Jira, the platform where our HEY! teams track their work. I learned by trying. I always advanced the work by asking an expert.
Instead of giving a comprehensive Jira training to the support teams that we have transformed into agile, we made a brief transfer before the first sprint where we focused on the parts that would be useful for them.
We solved the problems they experienced during the sprint by talking and writing one-on-one in the field, and we still solve them when needed.
At first, the most common problem I encountered was canceled "user stories". Things always seem to be canceled because a "user story" entered in Jira and was pulled from "to do" to "done" without going through the "in progress" field, therefore sprint performance could not be calculated correctly.
Where did I go wrong?
For every team I've had this problem with, I've emailed the team: I explained it on their 'Daily'. Despite this, I was running into the same problem at least once every sprint. The first question I ask myself in every encounter was ‘Why are their jobs being cancelled?’
The response was, "I guess they didn't read their emails or didn't listen/understand me well enough on the 'daily'."
I mean, it's obvious!
When this is the answer, action is standard without thinking: Email again, mention on 'daily' again. So it's a vicious circle!
I think I had the enlightenment I mentioned for the third time when I was about to send the same email as a reminder to the same team.
I was unconsciously asking myself the question 'why' but I was always missing the 'how'. My transition from 'why' to 'how' started that day.
At that moment, I felt that the control was completely in my hands, not the other parties.
In this case, my question, "Why are their jobs being cancelled?" transformed into “How can I make them select ‘in progress’ before selecting ‘done?”.
If they had not opened Jira only at the beginning and end of a sprint, the problem would have been solved. That's what happened. I never faced such a problem again in teams that started talking about their business through Jira in their 'Daily'.
After this experience, many of my questions naturally evolved from “Why is ... happening?” to “How can I ...”
I asked “What kind of change will help turn on the cameras?” instead of “Why aren't the cameras on?”
I started to ask “What kind of environment should be created so that the capacity of getting cross-work, and the enthusiasm of the team increases” instead of “Why don't they do cross work?”
Essence of the story:
The idea of solving some of the gangrenous issues that we thought were unsolvable by asking less 'why' and more 'how' was a bit unbelievable, wasn’t it?
I think you should try this at least once and feel the change. Maybe the solution is simply changing the question patterns and asking the right questions.
P.S. You can contact us by clicking here to share your experiences and ask questions about the agile working method.
Comments