A software development sprint is typically used within the agile methodology and is a predefined set of work for a set duration of time. A typical sprint will last two weeks and will have a predefined list of tasks for the development team to deliver.
Normally, a sprint review is done once a sprint is completed. This is to gauge what has happened, what needs to be moved into the next sprint and assess the development team’s velocity.
Tasks can be assigned to the sprint based on estimated hours or a concept called story pointsStory points are a method of ranking a development task's complexity. There are a few different methods for doing this,... where tasks are assigned a complexity number from 1, 2, 4, 8. And the amount of work chosen is based on the number of story pointsStory points are a method of ranking a development task's complexity. There are a few different methods for doing this,... that can be completed within a standard sprint.