Skip to main content

How we do mission-driven development

By Jack Sim - 23rd June 2021

Earlier in the year, we looked at mission-driven development and the benefits it can provide a project. In this blog, I’ll give you a step-by-step guide on how we do this at Zaizi. 

The 'missions' approach allows a team to collaborate better and reach outcomes quicker. 

Our missions are 12 weeks long. In our experience, three months is long enough to really understand a problem and come up with the right solutions, and short enough to show value quickly. Missions can be shorter, but never longer. 

We take an iterative and agile approach, constantly tweaking the potential solution based on user research. 
 

mission workflow
Mission-driven development: A look at the process of our 12 week mission work
 

Step 1: Create a mission brief 

This is a short and concise document that details:  

  • the problems/opportunities we'll try to solve in the mission
  • the team/roles we will need
  • how we will measure success 
  • definition of done - how we know when the mission is complete

Step 2: Hold a mission kick-off session 

This is essentially a sprint planning session. All members of the team, who work on the mission, review the brief and then map out potential activities for each of the problems/opportunities. 

The mission team agrees which of these activities should be done first and what can realistically be achieved in the first two weeks. 

Step 3: First iteration of a mission

In most missions, the first few weeks feel like a mini discovery. It’s really about understanding the problems we're trying to solve.

This can include activities such as user research, spike investigations, proofs of concepts. These activities help ensure we are solving the highest value problems with the right solutions.

Step 4: Show what we have delivered

It’s key to reflect at regular intervals on what is being delivered and how the team is working. Undertaking agile ceremonies like show and tells and retros every two weeks ensures stakeholders see progress within a mission. It also gives the team a chance to celebrate success or understand how they can improve. 

During a mission, when fleshing out potential solutions, we constantly take feedback — both quantitative and qualitative. These ceremonies also encourage that feedback loop. 

Step 5: Hold a close-down session

At the end of a mission, we have a close-down session to give an overview of what we've done. We show the problems we solved, the solutions we put in place, and the results. We also document and suggest enhancements for future missions.

It’s also a chance to celebrate success! 

Step 6: Firebreak

At the end of the three months, we find it’s helpful to have a ‘firebreak’. It's basically the chance for a multidisciplinary team to take a week’s pause before beginning another mission. 

Individuals in the team can take this time to work on any other non-mission related work. 
 

We're happy to share how you can apply the same mission-driven approach to your development work. If you would like to know more, feel free to get in touch
About the author: Jack Sim
Jack is a Delivery Manager at Zaizi. He has over 5 years' experience of working in project delivery, using both Waterfall and Agile methods. He's delivered multi-million-pound software development projects for our public sector clients and is passionate about making sure user needs are met. Jack, a strong advocate for Agile ways of working, is a certificated Scrum Master and Agile PM.