Sprint backlog - Coggle Diagram
The main ponits are the next
The estimated effort (that is, story points) required to develop each requirement
The tasks required to develop each requirement
A prioritized list of the requirements (for example, user stories) to be developed in the sprint
The hours estimated to complete each task (if needed)
The sprint goal and dates
A burndown chart to show the status of the work developed in the sprint
the duration of the meeting is 15 minuts.
sectional the requirements into little tasks is a great way to avoid to get lost.
The ideal way to work in our requirements is that all the team members will work together on it
we have the idea to prioritizer the requirements
The burndown table is a great way to se the progress
it is composed of two columns,
the vertical column means the hours
the horizontal means the distribution between sprints.
About the worktime
we have to avoid overexploiting our employees
the best way to get our goals talking about workhours is working between 5 to 7 hours per day
if we try to work more time, we are going to waste a lot of resources.