The Sprint Team
A successful sprint begins with careful selection of people who can commit time, make decisions and create tangible outcomes. Keep the core group lean, typically five to seven, so conversations stay focused and momentum is maintained. Aim for diversity of perspective across customer, business and technology, while avoiding spectators. Everyone invited should be present for the full sprint, with calendars cleared and managers aligned on the commitment.
Core Roles
The Decider carries authority to choose a direction and release budget or resources. This person should attend every day, with clear windows for key choices after reviews and voting. If the Decider cannot be present, name a proxy with written decision rules agreed in advance, and secure rapid access to the real Decider for final sign off. The Facilitator is neutral, protects the agenda and timeboxes, manages energy, and keeps discussion productive. They prepare materials, tools and space, guide activities, and ensure remote or hybrid set ups run smoothly. Experts bring subject knowledge at the right moments, such as customer research, engineering, data, operations, legal, finance or marketing. Invite them to share facts, constraints and examples, then release them so the core team can continue.
Selecting Participants
Choose makers who can turn ideas into sketches, prototypes and testable flows, not only commentators. Include a product lead, a designer or content specialist, an engineer who understands technical feasibility, and someone close to customers such as support or sales. Add a data or analytics perspective where possible. Check authority as well as skill: the team must include the Decider and people who can commit follow up work. Keep the size tight by replacing overlapping roles rather than stacking them. Avoid passengers by setting expectations on attendance, pre-reading and confidentiality. Confirm that all participants are comfortable with the subject, willing to sketch, and open to structured critique.
Team Dynamics And Working Practices
Set ground rules at the start: one conversation at a time, stick to timeboxes, and assume positive intent. Reduce hierarchy effects by using silent work, written ideas and dot voting before discussion. The Facilitator steers conflict into clear choices, summarises options visibly. Feedback targets the work, not the person, with clear criteria tied to the sprint goal. For remote work, ask for cameras on, use a shared board with templates and plan short breaks to maintain focus. Schedule Experts with precise arrival and exit times, and build daily checkpoints for the Decider to hear the team’s view before making the call.
