An Overview of the Scope Stage

What happens in the Scope stage of our Way of Working

The purpose of scope is to dive deeper into the problem statement and design a solution that is ready for development. It is important for a scope to focus on a manageable body of work, instead of a product’s entire roadmap. Scoping out one build at a time makes the project more agile and allows the development team to deliver value earlier and often. 

Scoping is performed by a Product Designer and a Product Developer from the Product Success team. Having these two specialities enables the team to consider solutions from not only the user’s perspective, but also the technical feasibility of its implementation. It is also important to involve key decision makers and stakeholders in the process, so that everyone is on the same page and is satisfied with the direction the scope is taking. Account Managers are also involved here to manage customer expectations and contribute insights from a commercial perspective. 

In general, a scope should deliver the following artefacts for an upcoming build: 

  • Scope document 
  • Non-functional prototype 
  • Requirements backlog 
  • Database model 
  • Estimations 
  • Projected roadmap for the product 

Realising these deliverables for a build typically takes between 2 and 5 weeks in length. Teams can scope for longer, however this indicates that they are scoping out more than one build of work and introduces risk during development. The further functionality is scoped out into the future, the more unknowns and uncertainty is introduced into the project. 


Customer commitment 

The responsibility level of customers and their stakeholders during scope are primarily focused around the meetings. It is normal to have two or three scope meetings per week during a scope to allow the team enough face time to ask relevant questions. While these meetings are important, it’s also crucial to allow the team enough time to deliver quality deliverables at each meeting after the previous meetings findings. Some typical meetings that happen during scope are:  

  • Kick-off session to understand the scope 
  • Deliver findings from user observations and market research 
  • Ideation & brainstorming sessions 
  • Prototype showcases, and 
  • Scope delivery