When you are growing a startup, you don’t have time to walk! That’s why we sprint. Our entire ecosystem runs on weekly sprinting following agile practises to help us move quickly and fail fast. 

Table of Contents

What are sprints?

If you have not worked in sprints before, don’t worry, it’s really simple. A sprint is a time-boxed ‘run’ towards a common goal. Sprinting is very poplar in software engineering teams and is starting to filter out into wider teams.

Our sprints last one week and allow our teams to remain extremely aligned and agile. How do you eat an elephant? One bite at a time.

How does it work?

Our weekly sprints run on the following agenda:

Monday 10:10am – Sprint kick off

On Monday morning, all team members join a Zoom call where we kick off the week’s sprints. Team leads share their sprint goals for the week, setting the context for the week and aligning everyone.

They also share key initiatives which make up the sprint. 

Tuesday to Friday 10:10am – Daily Standups

Each morning the whole company meets on Zoom to do a type of standup. This lasts for around 20 minutes and aligns everyone in the company.

Friday Afternoon 15:00pm – Sprint wrapup and retrospective

This is a celebratory call to review how well the sprints have performed against the goals, team leads share results and shout out the wins achieved during the week. We then work over a retrospective, you can learn more about our retrospectives here.

The types of sprints we run

 We have a few different types of sprints:

  • Team Sprints – our most common sprinting are team sprints, where each team focus on their own startup.
  • Swarms – an ecosystem wide sprint where the whole ecosystem jump in to support a single goal, more details here.
  • #Allhands – Each quarter we all get together to socialise, learn and connect, more details here.

Who sets the sprint goal & backlogs?

For team sprints each team will set their own sprint goals and manage their own tasks and backlog. Swarms are run slightly differently and require a deeper level of planning to ensure everybody can contribute and be involved in the sprint. 

How do we evolve and learn?

Retrospection is built into the agile methodology,  by constantly reflecting, we can improve and adapt very quickly. Every week we ask every team member to reflect and answer the following questions:

  • Yippee – What went well this week
  • Opps – What went less well
  • Lightbulbs – Any key learnings or takeaways
  • Questions – What are you unsure about / have questions about