A sprint is a set period of time during which work is manufactured.

There are plenty of materials in the web about sprints. In Mashup, we treat sprints somehow different.

Sprints are no longer just an activity for the development team but now also involves other teams and departments. Including, partners & clients. Everyone needs to be involved in the product development process.

We implement different kinds of sprints on per project such as:

  1. Planning sprints
  2. Design sprints
  3. Development sprints
  4. Stability sprints
  5. Technical debt sprints

Business owners, designers, QAs have their own sprints now.

One major use case is, some features are complex require researching should be done ahead of time during the "business sprint" period.

So are features that require a "design" needs a "design sprint". This ensures a clear idea of what the goals of the feature are and most especially, how to implement them.

Sprints run concurrently with each other, managed separately, and some being a few steps ahead of (technical planning, design sprints) of the development sprint.

The sprint lifecycle

This is our Sprint Lifecycle indicating activities for a 10-working-day sprint that is primarily focused on the core services we are providing. We'll discuss each stage throughout this playbook.

Further reading

There are a lot of books and resources out there that discusses Agile Development so we won't discuss them much here.

However, here are some key references that our team draws inspiration from: