We will use the Nexus framework to scale Scrum
What is Nexus? Nexus is a framework within the Scrum methodology that guides multiple Scrum Teams on how to collaborate to deliver an integrated product in every Sprint. This framework is useful for larger, more complex projects.
There will be three Scrum Teams in the Nexus:
Scrum Team #1: CoCo Team:
Slowly taking ownership of CHEFS. Collaboration with Team #3 is yet to be defined. Matthew and Catherine are leading the conversation with them.
Scrum Team #2: Health Team
This is the CGI team, representing the Ministry of Health of BC and carrying forward their vision of the Product to serve their interest, while keeping in mind the fact that we are enhancing a Common Compoent.
Scrum Team #3: NRS (Showcase) Team:
Original CHEFS client. Then CHEFS went beyond NRS. They do not take part in development of new features. They're just making sure the product works for them.
Right now they do have a "Maintainer" who's role is to review and approve the PRs so that new code can be merged with the main repo.
Nexus Integration team (aka Nexus Team):
The Integration team is in charge of the supervision and the coordination between the different Scrum Teams. It is represented by the Product Owner, Scrum Masters and other important roles that would help with integration, coaching or coordination.
Our Nexus Integration team will be the following:
Keyvan (SM CoCo Team)
Killian (PO Health Team)
Andy (PO CoCo Team)
Patrick (Architect Health Team)
Conrad (Architect CoCo Team)
Anurag (DevOps Specialist CoCo Team)
??? (Developer CoCo Team)
??? (Developer Health Team)
UX/UI Team:
The UX/UI team will be responsible for implementing the User-Centered Design approach with the clients. Emir and Jordan will work with Miranda to help gather requirements, meet with end users and define real User Stories.
This team will help carry the vision of the Product, keeping in mind that each new feature discussed with the client should become a "Common Component".
Emir and Jordan will report to Keyvan and Andy while Miranda will report to Killian and Samuel
Sprint Duration:
2 weeks
Ceremonies:
Ceremony | Description | Duration | Frequency | Attendance |
|---|---|---|---|---|
Ceremony | Description | Duration | Frequency | Attendance |
Nexus Daily | meeting to report on what each team is doing and whether we have blockers. To be held before individual Daily Scrums | 15 min | Every day or every other day | Keyvan, Andy and Killian. Matt as optional, Samuel as optional. Others as needed |
Team Daily | Each individual team member gets a chance to answer the following questions:
| 15 min | Every day | The whole Scrum team. Samuel as optional |
Nexus Refinement / Planning | Look at the overall backlog and define the Dependencies between the stories. This will feed the individual Sprint Planning sessions. | 1hr | Every week | Nexus Team + Bring in Jordan and Emir and Miranda |
Team Refinement | Backlog refinement sessions lead by each individual Scrum team. This is the opportunity to detail the User Stories and estimate them | 1hr | Every week | The whole Scrum Team. Samuel as optional |
Team Planning | The goal is to clearly identify the scope of the new Sprint and estimate Stories that haven't been estimated during the refinement sessions. Ideally the Planning meeting should be more about confirming than preparing. | 1hr / 1.5hr | Beginning of the Sprint | The whole Scrum Team + Samuel |
Nexus Review | All the Scrum teams get to meet to demonstrate their accomplishment during the Sprint (e.g. new features, important bug fixes, documentation, design, etc.) This is a celebration! If issues are identified during the Review, they should be addressed through a different, dedicated meeting | 1.5 hr / 2hrs | End of each Sprint | Everybody + client |
Team Retrospective | This is an informal meeting to get closure on a Sprint and to get everyone to share their thoughts about what is going well and what could be improved or worked on. It is a good way to check on the health of the team and its members. | 1hr | End of each Sprint | The whole Scrum Team + Samuel |
Nexus Retrospective | As needed, after each sprint the Nexus team can meet to reflect on what is going well and on what could be worked on to improve the collaboration between the teams | 30 min / 1hr | End of each Sprint | Nexus team |
Major Review | Will be used when a major release or milestone is about to be reached. This would happen with the specific impacted stakeholder to be able to gather as much feedback as possible before the usual Nexus Review | 1hr to 1.5hr | As needed | As needed |
Backlog:
One common backlog
Managed in JIRA and Confluence
Each Story will be tagged and assigned to a specific Scrum team through Components. We will create a "Health" and "CoCo" component to differentiate the Stories
Estimation method (sizing):
Will use the Fibonacci sequence to be able to track velocity accurately
We will need a reference Story, which will be defined by the Nexus team
Definition of Ready:
Standard DoR
Each User Story will need to be reviewed by the Nexus team through a Refinement meeting before it can make it into a Sprint.
Dependencies with other stories have to be defined during the Nexus refinement.
Definition of Done:
Confluence:
https://bcdevex.atlassian.net/wiki/spaces/CCP/pages/986382368/Ministry+of+Health+MoH
Testing:
Internal Testing is defined in the DoD. Before "Done Done" status Scrum teams can have their own cyclical Usability/Exploratory phases with end users.
To be defined by each individual teams