Sprint

Sprint is an iteration in Scrum, during which the functional growth of software is created. It is rigidly fixed in time. Sprint duration is from 2 to 4 weeks.

In some cases, for example, according to the Nokia standard, the duration of the sprint should not be more than 6 weeks. Nevertheless, it is believed that the shorter the sprint, the more flexible the development process, the releases go out more often, the feedback from the consumer comes faster, the less time is spent working in the wrong direction.
On the other hand, with longer sprints, the development team has more time to solve the problems that have arisen in the process, and the project owner reduces the costs of meetings, product demonstrations, etc.

Different teams select the sprint length according to the specifics of their work, team composition and requirements, often trial and error. To estimate the amount of work in a sprint, you can use a preliminary estimate which is recorded in the project backlog.

Sprint backlog contains functionality chosen by the project owner from the backlog. All functions are divided into tasks, evaluated by the scrum team. Every day, the team evaluates the amount of work that needs to be done to complete the sprint.

Burndown chart is a diagram showing the amount of completed and remaining work, relative to the time for project development. Diagram data must be updated daily to show real-time progress and costs in working on the sprint and project. Data must be available to all project members.

Sprint Story is the required functionality that is added to the backlog. Often the story has the following structure: "Being a user <user type>, I want to do <action> to get <result>". This structure is convenient as it is clear to both developers and customers.

Abnormal Termination. Sprint termination can be made ahead of the scheduled completion date in exceptional situations. The team can stop if they understand that they can’t reach the goal of the sprint in the allocated time. The owner of the project can also stop the sprint, if the need to implement its goal disappears. After termination, a meeting with the team is held, where the reasons are discussed. After that, a new sprint begins.