9. Simulation

Now that we have seen all the main concepts of Scrum, it is time to put them into practice with a full simulation. I would like you to plan a complete Sprint for a project of your choice, applying everything you have learned so far.

Instead of investing time in learning a specific piece of software, work with pen and paper (or an equivalent digital medium).

Choose a real or fictional project (it can be a website, mobile app, etc.) and follow the steps below to plan a complete Sprint:

1. Write down, on 10 sheets of paper, 6 different tasks you would like to complete in the project. This will be your Product Backlog. If you need to, search the internet for a template on how a task is structured.
2. Prioritize those tasks, ordering them from most to least important, or the order in which they should be completed.
3. Plan a 2-week Sprint; you cannot select more than 4 tasks for the Sprint:
4. Define the Sprint Goal.
5. Select the tasks from the Product Backlog that you believe you can complete during the Sprint and create the Sprint Backlog.
6. Establish the Definition of Done for the selected tasks.
7. Simulate a Daily Scrum over 10 days (you can write it in a notebook or on a separate sheet). Note down what you would do each day, what you have done, what you plan to do, and whether you have any impediments.
8. Simulate the Sprint Review at the end of the Sprint. Describe how you would present the completed work and what feedback you would expect from the Stakeholders.
9. Simulate the Sprint Retrospective. Note down at least 3 things that:
   • Worked well during the Sprint.
   • Did not work so well.
   • Improvements you would implement in the next Sprint.

Take your time.

This exercise would be more useful if you do it as a team, so if you find others interested in learning Scrum, I encourage you to do it together.