Glossary and How the user group will work

Glossary and How the user group will work

---

Glossary:

• Development is broken up into stages, and each stage is called a SPRINT (think of it as a block of time) – typically a sprint lasts either 2 or 3 weeks but in our case it is 2 weeks.  We have mapped out 5 sprints to complete this project.
• The designs which developers will work to within each sprint is called a WIREFRAME (think of it as a building blueprint).  We meet the developers twice a week to help them with an understanding on how SOAR currently works for appraisees, and how it can be improved and the wireframe is adjusted from there.

How the sprint cycle works:

At the start of each sprint, we will work with the developers to agree on what they should work on from the wireframe (they can only do so much within 2 weeks).  Whilst they do that, we meet with the design team to refine the wireframe for the next sprint.

At the end of each sprint, we would have another meeting where we review what’s been done, and also plan on what to work on in the next sprint.

During said next sprint, we will continue to refine the wireframe and test the work they have just completed.  The cycle repeats thereafter.

Timescale:

Proposed dates for the remaining sprints are as below (factoring in annual leave and public holidays etc):

• Sprint 1 = October 23 to Nov 3
• Sprint 2 = November 13 to 24
• Sprint 3 = December 4 to 15
• Sprint 4 = January 15 to 26
• Sprint 5 = March 4 to 8

The final sprint is known as “mop up” to clean and fix everything before deployment to live.

The plan is, whilst they are building the next part of SOAR based on the wireframes, we will get your input on the next sprint (essentially we will always be ahead of the curve).

 

This page was last updated on: 27/10/2023