Software Engineering Stack Exchange
Software Engineering Stack Exchange

Questions tagged [sprint]

A sprints in Scrum, or otherwise known as an iteration, is the heartbeat of the Scrum cycle.

Sprints (or iterations) in Scrum are small and repeatable intervals of work in which developers complete the effort which was committed to. The outcome of a successful Sprint is usually a shippable product or version of of a product.

Durations of sprints can be 1 week (5 work days), 2 weeks (10 work days) or even 1 month (20 work days). A sprint could actually be of any per-decided length but they are rarely longer than 1 month.

References:

107 questions
81
votes
10 answers

Dealing with failed sprints and deadlines

Many Scrum books and articles say that a failed sprint (when the team fails to complete some features from the Sprint Backlog) is not something that bad, it happens from time to time, and it can actually be useful if the team learns from their…
Andre Borges
  • 1,534
  • 1
  • 14
  • 15
51
votes
15 answers

How do I handle refactoring that takes longer than one sprint?

I work with a code base that is over 500K lines of code. It is in serious need of refactoring. There have been refactoring efforts identified that will take longer than the normal two week sprint. These can't be broken up into smaller tasks as I…
Charles Lambert
  • 2,019
  • 17
  • 18
50
votes
9 answers

How to make sprint planning fun

Not only are our sprint planning meetings not fun, they're downright dreadful. The meetings are tedious, and boring, and take forever (a day, but it feels like a lot longer). The developers complain about it, and dread upcoming plannings. Our…
Yehuda Shapira
  • 875
  • 1
  • 8
  • 14
33
votes
4 answers

Scrum - What are team members busy with during a sprint

So, a scrum sprint is a fixed time period during which a specific set of features should be implemented. And a scrum team consists of all the people committed to delivering those features, the majority of them typically being developers and…
holdenmcgrohen
  • 457
  • 4
  • 5
19
votes
6 answers

What to do if a team member misses a sprint planning?

Lets say a team member is on an annual leave. He won't be attending sprint planning but he will be back by mid of iteration/sprint. Lets say he has 50% capacity i.e. as he will be available for later half of the iteration, should we: have a…
Asim Ghaffar
  • 734
  • 6
  • 13
19
votes
5 answers

How to deal with sprint planning running far too long?

I took over 5 hours in sprint planning for a week long sprint. That seems like too much. We discuss things in detail in sprint planning, as most of team members are not senior. If we don't it will lead to mistakes during implementation and redesign…
kitta
  • 687
  • 6
  • 19
17
votes
4 answers

Confused about modifying the sprint backlog during a sprint

I've been reading a lot about scrum lately, and I've found what seem to me to be conflicting information about whether or not it's ok to change the sprint backlog during a sprint. The Wikipedia article on scrum says it's not ok, and various other…
Maltiriel
  • 273
  • 1
  • 2
  • 7
14
votes
6 answers

How to handle 50% of worse than average sprints?

My understanding of Scrum is that I determine the work my team can take on in the next sprint by averaging the number of completed points for the past several sprints. This is an average, so if history repeats itself, this sprint it is 50% likely…
Paul Draper
  • 5,972
  • 3
  • 22
  • 37
13
votes
9 answers

How do you name sprints in your projects?

Some Scrum software management tools give you this option to explicitly name your sprints. Do you have a preferred way of naming your sprints or do you just use a simple scheme like 1, 2, 3, ...?
Behrang
  • 630
  • 1
  • 5
  • 13
13
votes
9 answers

How relaxed (or not) should a sprint be?

What should be the attitude towards getting stories done that are assigned to a sprint? Obviously you want to prioritize getting them done in the sprint, but to me the whole point of agile is to be dynamic: You don't want to deliberately…
void.pointer
  • 4,983
  • 8
  • 30
  • 40
12
votes
4 answers

Do "almost finished" tasks or stories justify planning with overload in the next sprint?

The case in question: The sprint is almost over and one of my Scrum teams did not finish some tasks. (The reason for this is not essential for this question and will be addressed accordingly.) One of them is a classic "90% done" case with a rather…
Stephie
  • 223
  • 1
  • 8
12
votes
5 answers

Sprint item takes longer then expected to be completed. What should we do?

What should we do if a item in scrum takes longer then expected? i am asking this because i have been noticing items that developers is struggling to complete as it is much tougher then initially thought. In such situation should we remove the…
CliffC
  • 343
  • 2
  • 9
12
votes
4 answers

Handling "related" work within a single agile work item

I'm on a project team of 4 devs, myself included. We've been having a long discussion on how to handle extra work that comes up in the course of a single work item. This extra work is usually things that are slightly related to the task, but not…
Tesserex
  • 3,015
  • 4
  • 26
  • 27
12
votes
3 answers

What happens between sprints?

I'm working on a project loosely following the scrum model. We're doing two week sprints. Something I'm not clear on (and don't have a book to consult) is exactly what is supposed to happen between sprints: there should be some "wrap" process, where…
Steve Bennett
  • 3,419
  • 4
  • 20
  • 24
11
votes
7 answers

What to do when a sprint is finished early?

What to do when a sprint is finished early? At the moment our Scrum team works off stories from the backlog, if the sprint is finished early. What happens with stories taken from the backlog? Will the stories be added to the current Sprint ? If yes,…
Jonathan Egerton
  • 531
  • 1
  • 5
  • 8
1
2 3 4 5 6 7 8