## What is Sprint? In [[Scrum]], a Sprint is a set period of time during which specific work has to be completed and made ready for review. It's essentially a cycle of work, usually lasting between one week to one month, with two weeks being the most common duration. Each sprint begins with a planning meeting and ends with a review or retrospective. During the sprint, the team works on predetermined tasks and goals but avoids making changes that could impact the sprint goal. --- ## Tags #Scrum #Agile #ProjectManagement #Sprint #SoftwareDevelopment --- ## Derived Concepts 1. [[Sprint Planning]]: This is the meeting that kicks off the sprint. The team discusses and agrees on the scope of work to be accomplished during the sprint. 2. [[Sprint Goal]]: This is a short, one- or two-sentence description of what the team plans to achieve during the sprint. It provides a shared objective, and is used to make decisions about what work will be done. 3. [[Sprint Backlog]]: This is the list of tasks and requirements that need to be completed during the sprint. It's created during the sprint planning meeting and is a subset of the product backlog. 4. [[Sprint Review]]: This is a meeting held at the end of the sprint where the team demonstrates what they've accomplished during the sprint. Stakeholders provide feedback that could influence future sprints. 5. [[Sprint Retrospective]]: This is a meeting held after the sprint review where the team reflects on their performance during the sprint, discussing what went well and what improvements can be made for future sprints. 6. [[Daily Scrum]] or [[Stand-Up Meeting]]: This is a short, daily meeting (usually 15 minutes) where each team member briefly discusses what they did yesterday, what they plan to do today, and any obstacles they are facing. 7. [[Scrum Master]]: This is a role in scrum responsible for facilitating the scrum process, assisting the team in achieving their sprint goal, and removing obstacles that may impede progress. 8. [[Product Owner]]: This is a role in scrum responsible for defining and prioritizing the product backlog, ensuring that the team is working on tasks that deliver maximum value to customers/business. 9. [[Burn Down Chart]]: A visual representation used to track work completed versus work remaining over time in a Sprint. --- ## Related Concepts 1. [[Agile Methodology]]: A set of principles for software development that prioritizes flexibility, customer collaboration, and delivering functional software in regular, small increments. 2. [[Scrum Framework]]: A framework within Agile that is used to manage complex product development with an iterative and incremental approach. 3. [[Product Backlog]]: This is a list of all potential tasks or features that could be done in a project, ranked by priority. The highest-priority items are selected for the next sprint during the sprint planning meeting. 4. [[Iteration]]: In Agile methodologies, an iteration is a single development cycle. Each sprint in Scrum is an iteration. 5. [[Kanban]]: Another Agile methodology that visualizes work and workflow, allowing teams to identify potential bottlenecks and optimize their work processes. 6. [[User Stories]]: These are informal descriptions of a feature or requirement from the perspective of the end user. 7. [[Velocity]]: A measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. 8. [[Timeboxing]]: A time management technique used in Scrum where a fixed amount of time (the "box") is allocated to each activity (like sprints). 9. [[Increment]]: The sum of all the Product Backlog items completed during a Sprint combined with all previous Increments - represents a step toward a vision or goal. 10. [[Definition of Done (DoD)]]: A shared understanding within the Scrum Team on what it takes to make a Product Backlog Item releasable into production at the end of each Sprint.