- You like Scrum.
- You want to use it, but there is one issue. You have more than 20 people in your project and they are spread across 3 different teams (e.g. mobile, web front-end, and back-end).
- You can try using Scrum, but you might face problems such as long meetings. The mobile team may not be interested in web tasks, while the web team may only want APIs and might not be willing to address backend issues
- For such a situation, an approach called Nexus was created. Nexus is based on Scrum principles and helps coordinate multiple Scrum teams working on a single product.
- In a few words, this approach can be explained in the following way:
- You have one product backlog and a product owner who supports it. You have one or more Scrum Masters. You have several Scrum teams and one integrated team, which consists of a Product Owner, Scrum Master, and team members from the Scrum teams.
- The integration team defines common Sprint goals, plans stories for the Sprint, and spreads goals and stories across teams. Each team plans their work in the Sprint.
- The integration team supports communication between all teams and the final delivery.
- There is a short instruction that can help you implement Nexus.
- Ensure that all team members and stakeholders are familiar with the Nexus framework, its principles, and its components.
- Define the Product Owner (the product owner can have helpers) and create a Product Backlog.
- Determine the number of Scrum teams that will be involved. Each team should have 3-9 team members and one Scrum Master. One Scrum Master can support several teams, and there can be more than one Scrum Master in the project.
- Take 1-2 persons from each team and create an integration team (the Product Owner and one Scrum Master are part of this team).
- The integration team plans the Nexus Sprint.
- After planning, integration team representatives return to their respective teams to plan the team Sprint and estimate stories. If any questions arise, the process reverts to previous steps where the integration team meets and discusses issues.
- At the end of the planning session, we have formed an estimated Nexus Sprint.
- Daily, each team has its daily meetings. After these daily meetings, the integration team has their daily meeting.
- In parallel, the product owner continues backlog refinement.
- At the end of the Sprint, the integration team forms the Sprint Increment.
- After that, the team conducts a Review meeting (where the common results of the Sprint are demonstrated to stakeholders).
- After that, the team conducts their retrospectives, and after these retrospectives, the integration team conducts its retrospective.
- The team starts planning activities for the next Sprint.
- In brief, that is all. If you have any questions, please feel free to contact me:)
