{"id":66306,"date":"2021-07-27T16:05:40","date_gmt":"2021-07-27T15:05:40","guid":{"rendered":"https:\/\/www.prodpad.com\/?post_type=pp_resource&p=66306"},"modified":"2023-05-03T14:15:43","modified_gmt":"2023-05-03T13:15:43","slug":"agile-sprint","status":"publish","type":"pp_glossary","link":"https:\/\/www.prodpad.com\/glossary\/agile-sprint\/","title":{"rendered":"Agile Sprint"},"content":{"rendered":"\n
\n
\n
<\/div>\n\n\n\n
\n

What is an agile sprint?<\/h2>\n\n\n\n

An agile sprint is a short period with a concentrated effort to complete certain predetermined goals, with those goals often taking the form of a new, changed, or removed feature within the product being developed. Sprints are a common way of managing time in agile product development<\/a>. <\/p>\n\n\n\n

In agile development, a sprint is usually marked by time-boxed iterations of development and experimentation<\/a>. The goal of an iteration may involve designing and prototyping, coding\/programming, testing, recognizing bugs to address, and refactoring code for better performance or security. While a sprint may be a very short period of time, it’s often a small number of days or weeks. <\/p>\n\n\n\n

What are the benefits of using agile sprints?<\/h2>\n\n\n\n

Agile practitioners recognize that building quality products takes time \u2013 but they also believe that it should never be at the expense of progress because waiting for leads to a net loss over the course of a project\u2019s life.<\/p>\n\n\n\n

Short, regular intervals of work result in increased overall productivity.
Benefits include being more time efficient, changing up how projects are executed, and potentially the most important part – getting customers engaged and involved by having them talk to everyone on each team. In a workshop setting – these short sprints help get individuals who usually collaborate together as well as those who rarely interact with one another collaborating.<\/p>\n\n\n\n

Another benefit is the short feedback loops. Completing a small piece of work in a short period of time allows it to be reviewed and feedback provided, ensuring the direction of the change is correct.<\/p>\n\n\n\n

Agile sprints have been a huge success for the software development process, as it provides a fail-safe in the event of bugs or mistakes creeping up in development (also known as scope creep). <\/p>\n\n\n\n

Using an agile sprint allows developers more time to debug issues from one phase before moving on to another stage of testing without any fear of slowing down progress on other parts of their project.<\/p>\n\n\n\n

Sprints are a key component of agile product development, particularly in in the scrum<\/a> or kanban<\/a> methodologies.<\/p>\n\n\n\n

How are agile sprints managed?<\/h2>\n\n\n\n

Sprints are usually managed via a series of agile ceremonies. These are usually known as sprint planning, sprint review, and sprint retrospective.<\/p>\n\n\n\n

Sprint planning is a meeting in the agile development process in which the product team proposes a list of tasks to take on and complete within the upcoming time-boxed sprint. This usually takes place just prior to the sprint’s start.<\/p>\n\n\n\n

The sprint review is a meeting where the team shares details on the work that has been completed in the sprint, with a view to getting that work accepted for release. It usually takes place at the end of the sprint.<\/p>\n\n\n\n

The sprint retrospective is a meeting where the product reflects on the previous sprint and identifies ways in which future sprints could be improved. The improvements identified are often process-related, but could also be related to potential improvements in the product itself. The sprint retrospective usually takes place at the end of, or sometimes just after the sprint ends.<\/p>\n\n\n\n

\nBack to The Product Management Glossary<\/a>\n<\/div>\n\n\n