Publish your Sprint Goal in your README.md
- User Stories you will implement during the Sprint (number + description)
- Velocity you will implement during the Sprint
- Size H = 7 points, M = 5 points, L = 3 points
- Plan for a velocity of 18
- Number of User Stories you will implement during the Sprint
In the Spreadsheet
- Label the selected User Stories of the Product Backlog with the current Sprint number
- Create a new tab in the Product Backlog spreadsheet with the US and the associated tasks
- Decompose each User Story into tasks
- Assign each task to a team member
- Estimate the amount of time for each task
- Every student should plan for 16 hours of work minimum for a sprint
- Some of the tasks can be done using Pair Programming
In GitHub Project
- You have access to a Kanban board
- Create the US and tasks in the kanban board (as To does)
- Each of the Kanban US and tasks should be converted to issues
- Label the issues with the sprint number and the US they correspond to
- One of the team members creates the React/Android Studio project and begins to code
- The code is pushed in the team GitHub repository
- The other team members clone the repo and make some trivial push to the team GitHub repository
- Code comments are only in English
- You cannot push directly on main
- You work exclusively on your own branch (labeled with your firstname)
- You merge your branch to the main branch using a pull request
- Each developer must have at least 10 pushes / sprint
- You will only be able to merge from your branch to the main branch after one review