Sprint Review.md

# Sprint Review

This week you will be wrapping up your first sprint by carrying out a structured sprint review. This will need to be carried out in the two lab sessions under the supervision of your lab tutor.

The review is split into three parts, focussing on:

1. The task.
2. The team.
3. The individual.

Once this is complete you will complete the sprint planning ready to start development next week.

Before we start, take a moment to reflect on the diagram below taken from John Adair's Action-Centred Leadership model.

![Action-Centred Leadership](exercises/.images/Action-Centred-Leadership.png)

## 1 Sprint Increment Review

Before the meeting, the _Product Owner_ should:

1. be familiar with the new feature to be demonstrated.
2. Print off the prioritised feature backlog.
3. Bring along a notepad and pen.

This meeting should be run by the **Product Owner** using the agenda listed below:

1. Make sure the meeting starts on time.
2. **Product Demonstration**: The product owner demonstrates the incremental changes since the last sprint increment review. Since this is the first meeting, all working features demonstrate progress. Note that there should be no technical language used here, the demonstration should only cover how the end user will interact with the system. This should take no longer than 10 min.
3. **Feedback:** Once the demonstration is complete the client provides feedback, this consists of:
    1. Sign-Off: the client is happy with one or more features and the product owner should note this down.
    2. Bug-Fixes: there might be a few points raised by the client and they will indicated what needs changing. This might be a UI tweak or something more signficant. Again, the product owner makes notes.
4. **NOW SWAP PRODUCT OWNER** (IF YOU WANT)!
5. **Backlog Review**: the product owner goes through the printout and the client discusses:
    1. whether there are additional features they now want.
    2. Whether the tasks are in the best priority order.
    3. What feature they would like the team to work on in the next timeboxed sprint.
6. **Planning**: Now, with the client present, the team should describe the feature from the user perspective using diagrams and designs. At this point the feature should be clear from both the client and development team perspectives.
7. **Next Meeting**: Finally the date and time for the next review meeting are agreed and put in everyone's diary. The client can now leave.

## 2 Team Retrospective

The next task is to reflect on how you worked together as a team and should take around 30 min. You will need a printout of the prioritised features your team put together, taken from the different agile methodologies you investigated. This task should be led by the **Scrum Master** who will need the printout plus a notpad and pen.

**NOW SWAP SCRUM MASTER** (IF YOU WANT)!

1. What went well during the last sprint?
2. What agile processed helped this, we should continue to use these.
3. What issues did your team have (be completely honest with yourselves).
4. What were the underlying causes?
5. How can you avoid making the same mistakes in the next sprint?
6. Discuss the printout of the prioritised list of agile techniques that you produced a few weeks back:
    1. Are there any agile techniques that would help you avoid the problems you faced in the last sprint?
    2. Are there any techniques that would further improve your team's performance?
    3. Pick the best three techniques from this list and, as a group investigate and discuss how you will implement.

## 3 Professional Development Review

Right back at the start of the module you produced a skills matrix. You will now review this, a process that should take around **one hour**.

1. Make a copy of the existing matrix in a second tab in the spreadsheet, call this **Sprint 2**.
2. Modify this copy:
    1. Delete any skill that your team wont be needing (discuss these with the team before deleting!)
    2. Now, as a team, identify new skills that, with hindsight, you should have added to the matrix.
    3. Revise your own abilities for the skils in the matrix using both the RAG (red, amber, green) and numerical scores.
3. Now compare the original version (tab 1) with this revised version (tab 2).

Each member of the team also produced their individual professional development plans (as MS Word documents). These were saved in a folder in MS Teams. Individually:

1. Review your original plan:
    1. Were the skills appropriate given the development work your team did in the last sprint?
    2. Did you get around to learning the three skills you identified?
2. Create a new page in the same document and, by reviewing the new skills matrix and through discussions with the rest of the team pick three skills from the updated skills matrix:
    1. Review the task you will be carrying out in the next sprint and identify one skill that will _have an immediate impact_ on your team's ability to deliver this.
    2. Review the revised skills matrix and identify a skill where the team are _generally weak_ (lots of red) and add this to your CPD.
    3. Finally choose a skill you want to improve (regardless of the overall team's skill level). This cound come from the skills matrix but could also be based on one of the lecture topics such as _psychology_ or _leadership_.
3. For each skill identified:
    1. Explain why you want to do this (task/team/indvidual needs).
    2. Explain how you will show you have achieved this.
    3. Investigate how you will carry out the CPD.

## 4 Sprint Planning

The final step is to carry out the sprint planning. This was detailed in a previous lab and should cover:

1. Architectural decisions.
2. Protocol and message formats
3. Task breakdown (adding these as issues to the issue tracker).
4. Estimation using _planning poker_
5. Adding the tasks to the Kanban board.