work packages
In order to achieve these goals, Scrum relies on the pull principle when processing the work to be done. The team therefore determines which and how many work packages it will carry out in the near future. To do this, the team independently fetches tasks from a pool of unfinished work. The team then estimates the relative effort per work package, taking into account the complexity and the associated risk. This effort is added up for the duration of a sprint and thus results in a team-dependent speed. Once a team has settled in, i.e. reliably estimates and delivers similar average speeds per sprint, this metric is used as a guideline for subsequent sprints.
sprints
Scrum relies on so-called WIP ("work in progress") limits. This means that only a certain number south africa telegram data of work orders can be carried out per work section. The number of work packages in Scrum projects is limited by the duration of a sprint, usually 1-4 weeks.
Roll
In every Scrum project, the three roles of Product Owner, Scrum Master and Development Team are clearly defined and have assigned tasks and responsibilities.
tools
Scrum teams can use either software or dedicated Scrum software. Which tool is best for your company depends on the scope of the tasks.