What is a Sprint? In the scrum framework, all activities to implement the requirements happen during Sprints. Sprints are cycles of work activities to develop shippable software product or service increments. Sprints are also sometimes called iterations. You think about sprints as if they're microprojects. As the term "Sprint" implies, a sprint doesn't take long, and it's maximum for four weeks. Sprints are always short, usually between 2 to 4 weeks. But depending on the reliably foreseen amount of work or for Exploration Sprints, a oneweek long Sprint is also typical. With the approval of the Scrum Product Owner, a Scrum Team may need an Exploration Sprint to investigate new technology, build a mockup or a proof of concept.
Different from a running race, at the end of a Sprint, the Scrum Team shouldn't be out of breath and power. Instead, the Scrum Team should be fresh, and they should energetically start the next Sprint. The Scrum Software Development and Delivery Framework has nothing to do to create pressure and stress for its team members. It's a wellknown fact that people perform best when they can work focussed, relieved, and undistracted. If it's applied correctly this is what Sprints help us accomplish. Every Sprint starts with a Sprint Planning Meeting. During the Sprint Planning Meeting, the Scrum Team decides what and how many requirements they will implement in this given Sprint. Subsequently, the Scrum Team starts the execution of activities to deliver requirements. Daily Scrum (Daily Scrum Meeting) happens every day at the same time in the same place. The goal of this meeting is to align all members of the Scrum Team regularly. Scrum Team Members can also ask help from the Scrum
72
