Coaching a team from dependency to self-management
This tests your ability to apply a maturity model (like Tuckman's) to Agile coaching. Outline your shift from directive teaching in Forming to challenging in Performing, retiring basic facilitation as the team matures. A red flag is a static coaching style.
What's really being asked
This question assesses your practical experience with team development beyond just knowing Scrum ceremonies. It tests your ability to diagnose a team's maturity level using a framework like Tuckman's stages (Forming, Storming, Norming, Performing) and adapt your coaching style accordingly. The interviewer wants to see you evolve from a directive teacher to a hands-off challenger, consciously making your initial role obsolete.
The full answer
A strong answer walks through the stages sequentially. First, in the FORMING stage, you are a teacher. You establish clear expectations, facilitate team charter creation, and explain the mechanics of Scrum events. Your stance is highly directive. Second, in the STORMING stage, you become a facilitator and conflict mediator. You use techniques like one-on-one check-ins and values alignment workshops to navigate disagreements, but you avoid solving problems for the team. Third, in the NORMING stage, you step back and become a supporter. You encourage the team to run their own ceremonies and introduce peer feedback loops, reinforcing their emerging autonomy. Fourth, in the PERFORMING stage, you are a challenger and optimizer. You retire direct facilitation and instead introduce advanced metrics like cycle time and flow efficiency to help the team find their own bottlenecks and opportunities for improvement.
The mistakes people make
A major red flag is describing a single, static coaching style, often vaguely termed "servant leadership," without mentioning how it changes. Candidates who can't name specific techniques for different stages (e.g., "I would just facilitate their meetings") reveal a lack of depth. Another mistake is focusing only on the Scrum Master's actions without explaining the goal: to increase the team's self-management capabilities. Failing to mention retiring certain techniques is a sign of a junior mindset.
What usually comes next
"How would you know a team has moved from Storming to Norming? What specific behaviors or metrics would you look for?" or "Describe a time you misdiagnosed a team's stage. What was the impact, and how did you correct course?" or "What happens if a new member joins a Performing team? Does the team revert to an earlier stage?"
A concrete example
In the Forming stage, I would explicitly facilitate a 2-hour team charter workshop to define roles and working agreements. By the Performing stage, I would have retired this role. Instead of facilitating, I might observe a retrospective and, at the end, ask a challenging question like, "Our cycle time for features has been flat at 8 days for three sprints. What experiment could we run to try and cut that to 6?" I'm no longer providing the process; I'm challenging their established process.
Interview question
Which statement best describes the most significant shift in an Agile coach's approach as a team matures from the Forming to the Performing stage?
- a.The coach consistently acts as a servant leader, removing impediments for the team at all stages.
- b.The coach's primary role evolves from facilitating all team ceremonies to ensuring strict adherence to Scrum principles.
- c.The coach transitions from being a directive teacher to a challenger focused on advanced optimization.Correct
- d.The coach shifts from mediating interpersonal conflicts to encouraging the team to run their own ceremonies.
Why? this is the answer
The correct answer reflects the coach's evolution from a directive teacher in the Forming stage to a challenger and optimizer in the Performing stage. A static coaching style, like consistently acting as a servant leader, is a common misconception and a red flag according to the card.
Just read this? Test yourself on what you have been reading.
Read the original → agileseekers.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles