0

I am new to project management and I have been reading about sprints whenever Scrum/Agile is mentioned.

Can someone explain to me what a Sprint is, or at least suggest a good reference on how to understand and execute one?

  • Does these links good read already to understand what i am asking? en.wikipedia.org/wiki/Scrum_%28software_development%29 scrumguides.org/scrum-guide.html – Kevin Marc Prijoles Dec 22 '15 at 2:31
  • 1
    Your links are fine. Is your question still existing? – Tob Dec 22 '15 at 5:27
  • 4
    The links you've provided give the answer. from the Scrum Guide : "he heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints best have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint." Read a bit more from the guide (you've linked to) – G.H Dec 22 '15 at 8:19
3

The Scrum Guide is the definitive source for this and any question regarding the Scrum framework. It's only 16 pages as a PDF and is your best source for building a primary understanding of Scrum.

According to the Scrum Guide, the Sprint is:

...a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created

If a Scrum team is at a beginner's level in their Scrum practice, I typically recommend a schedule like this:

Sprint for a beginner Scrum Team

This assumes a 2-week sprint and a repeating backlog refinement meeting on Fridays following the Daily Scrum.

It's important to note that, except for the Daily Scrum's timebox of 15 min, all the other event lengths are discretionary and fall within the Scrum Guides requirement for each. Backlog refinement is not an "event" in the Scrum guide, just a very helpful and wise practice that shouldn't consume more than 10% of the Development's capacity for a Sprint. Refinement is

the act of adding detail, estimates, and order to items in the Product Backlog.

This is typically things like:

  • Analysis
  • Decomposition
  • Discussion
  • Estimation of effort
  • Release planning

In general, the bulk of the Development team's time is still just the work of developing software. A trainer friend of mine is fond of saying, "Scrum doesn't care what you do the other 7:45 minutes of the day."

Another key part of that Sprint definition is the phrase "potentially releasable." This means the work completed in the Sprint is fit for its purpose and is ready to be given to the customer with no further work needed. In this way, each Sprint may be thought of as it's own project and is key to an organization building agility into it's software development.

Does that help?

  • As a Professional Scrum Trainer with Scrum.org, "doesn't care what you do", is a bit strange to me. We spend at least 15 minutes a day to make sure (care!) we're doing the best thing possible to reach the goal. And then spend another max 3 hours inspecting what we did, and adapting what we do the full 8 hours of the days next Sprint. There are 5 values guiding our behavior and thinking, and the principle of keeping transparency high to enable empiricism, suggest we should be Done often (so Continuous Integration/Delivery is implied) and cross-functionality ... But sure, not very explicit. :-) – Fredrik Wendt Jun 30 '18 at 6:12
  • (and the best way of being "Done" often is to slice thinly, and lower WIP (I coach all my teams in mob programming)) – Fredrik Wendt Jun 30 '18 at 6:13
3

The Sprint is the workflow cycle of Scrum. Scrum is the most popular of the many different Agile frameworks.

Scrum workflow as described on the Wikipedia:

A sprint (or iteration) is the basic unit of development in scrum. The sprint is a timeboxed effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally between one week and one month, with two weeks being the most common.

Each sprint starts with a sprint planning event that aims to define a sprint backlog, identify the work for the sprint, and make an estimated commitment for the sprint goal. Each sprint ends with a sprint review and sprint retrospective, that reviews progress to show to stakeholders and identify lessons and improvements for the next sprints.

Scrum emphasizes working product at the end of the sprint that is really done. In the case of software, this likely includes that the software has been integrated, fully tested, end-user documented, and is potentially shippable

For a practical guide to understanding Scrum and its Sprint cycle read the free eBook "Scrum and XP from the trenches" or do one of the Scrum Master courses to get you started.

1

In the simplest terms possible, a sprint is a period of time. Typically, sprints last somewhere between one and four weeks with two being a very popular duration.

During that period of time, a team has a predefined amount of work ("stories") to do, based on their own estimation of what they think they can finish. At the end of that time the team will look at what they set out to accomplish and what they actually accomplished, and use that information to do better in the next sprint.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.