Scrum Pattern: Sprint

 

  
ContextProduct Backlog Items are ready to be realized.
ProblemWhat is the optimum amount of time a Team can work with a minimum of written communication?
Forcestoo little/too much scope to be realized
too little/too much written communication
too little/too much organizational overhead
SolutionStart a Sprint with a length of one up to four weeks.

A Development Team can work up to four weeks without relying heavily on documents. Focussing on oral communication strengthens collaboration, productivity and quality. Reduce the Sprint length if you need more flexibility, but keep in mind that there might be a loss of productivity, if it is too short.

Resulting ContextThe Development Team produced a potentially shippable increment of the product and is ready for another Sprint.

Comments are closed.