Guiding the Crew: Strategies for a Successful Captain Week

In agile teams, leadership is not limited to managers or tech leads. One way to build shared ownership and facilitation skills is through a rotating “Captain” role. For one week at a time, a team member steps into this role to guide ceremonies, keep work flowing, and help the team stay connected. It is not about taking control, but about creating an environment where everyone can contribute effectively.

A couple of weeks ago, we started implementing what we call the Captain rotation in our team. What used to be the responsibility of a single team member is now shared among all of us.

This change was made not only to avoid bottlenecks and dependencies, but also to sustain accountability for the team’s process, commitments, and to each other, while developing leadership skills across the team. It is meant to be a safe space where everyone can practice leadership and collaboration skills.

What’s Expected of a Captain

The Captain role is a one-week rotating facilitation role. You guide the team, you do not run it.

Your focus is to keep agile ceremonies on track, surface blockers early, maintain a clear board, coordinate planning and refinement, and support healthy team norms. It is about inclusive facilitation and helping the team work effectively together, not doing all the work yourself.

My First Week: A Reality Check

I was completely on board and looking forward to my turn as Captain. But I finished my week feeling flustered and frustrated.

We often underestimate the mental shift it takes to go from being a participant to being the facilitator, even in the safest spaces. When you are Captain, others start relying on you for guidance. That means you cannot stay in the same “mode” you were as an engineer.

You need to start seeing things from a broader perspective, sometimes even adopting a different “voice” or way of speaking. It is a change in identity, and it is not as simple as it sounds.

Learning from Experience

After that week, I decided I wanted to get better. I read more about agile facilitation and reached out to Brad Smith, a much more experienced teammate who is comfortable switching between roles.

I asked him: What makes a good Captain?

From that conversation and some self-reflection, I gathered a few tips that I believe can help anyone stepping into the role for the first time.

Practical Tips for a Successful Captain Week

1. Write Clear and Valuable Jira Issues

For user stories, combine persona + behavior + reason. Example: “As a user, I want X because Y.”
Ensure every story maps to direct or indirect customer value. If it cannot be justified, refine it or remove it.
For bugs, always include: steps to reproduce, expected behavior, observed behavior, relevant logs or screenshots, and when the issue started.

2. Facilitate Without Losing the Room

Be willing to interrupt dominant speakers politely, acknowledge their point, then bring focus back to the meeting’s goal.
Keep discussions on track by repeating the purpose of the meeting or story being discussed.
Ask relevance questions like: “Is this a hard requirement?” or “Can we do this later?“

3. Use the Parking Lot Effectively

Move tangents or deep dives that are not essential to the current conversation into a parking lot list.
Keep this list visible and follow up, either in a later meeting, Slack, or refinement session, so items are not lost.

4. Switch Between Roles Intentionally

Use verbal or physical cues, such as “putting on my facilitator hat,” to signal when you are moving from engineer to facilitator.
When facilitating, hold back technical opinions until others have spoken. Part of good leadership is knowing when to be quiet.

5. Keep Ownership Collective

Ensure all team members are present during backlog refinement so diverse perspectives are heard whenever possible.
Encourage everyone to ask questions, even “basic” ones, to clarify business logic or requirements.

6. Manage Notes and Avoid Overload

Use a text file or quick notes to capture to-dos, action items, and conversation threads.
If you are capturing live in Jira, type literal words first and edit later or ask the team to pause so you can document accurately.
Leverage tools such as Slack reminders or a meeting transcription tool to follow up on action items.

7. Aim for Quality While Maintaining Momentum

Refining more stories can help keep the pipeline moving, but speed should not come at the cost of clarity.
Make sure each story refined has enough shared understanding of the why and the what to prevent confusion or rework later.
Striking the right balance between quantity and quality sets the team up for smoother delivery.

Closing Thoughts

My first week as Captain was definitely not perfect, and honestly, that is the whole point. This rotation is not about nailing it from day one. It is about building confidence, trying new approaches, and sharing ownership of how we work as a team.

Every Captain is going to have their own style, and that is actually what makes this work. Different perspectives make us better, as long as we are willing to learn from each other. If we keep focusing on clarity, good facilitation, and true team ownership, each rotation will run a little smoother than the last.

So when your turn comes up, jump in with curiosity, a bit of humility, and a willingness to adapt. You are not steering the ship alone, you are there to help guide the crew.

I would love to hear how other teams run rotating facilitation roles. What has worked well for you, and what would you add to this list?