Purpose:
Section titled “Purpose:”To discuss internally and review how the Sprint went
Scope:
Section titled “Scope:”Halo team to perform this after each Sprint ends
Responsibility:
Section titled “Responsibility:”Scrum Master and Halo team
Definitions:
Section titled “Definitions:”- Sprint Retro is completed after each Sprint to review what went well, what could be improved upon and anything else that could help improve efficiency for the next Sprint
Procedure:
Section titled “Procedure:”- First activity (Plan or preparation)
-
Scrum Master schedules and goes through with Halo team
-
After the completion of the Sprint, usually the following day after the release and capture inside of Sprint details chat box
Questions to ask:
-
What did we do well?
-
What did we learn?
-
What can we improve upon?
-
Issues we experienced.
Effectiveness Criteria:
Section titled “Effectiveness Criteria:”- What measures are used to ensure the procedure is working or is complete? Get input from all members of the Halo team
- What records are required? Sprint chat box is filled with answered questions
- Where are the records stored? Sprint chat box
References:
Section titled “References:”N/A
- EXTERNAL only – i.e., industry best practices, CIS18, this is not for cIT internal references
Process References:
Section titled “Process References:”- Link to process map.
Note: Please add KB relationships to core process, process. SOPs or other WIs on the right.