Skip to content
This repository has been archived by the owner on Apr 1, 2021. It is now read-only.

Commit

Permalink
Article: Sprint Workflow
Browse files Browse the repository at this point in the history
* Create WhatIsASprint.md

* Update WhatIsASprint.md

* Rename WhatIsASprint.md to What-Is-A-Sprint.md

* Rename filename

* Rename filename
  • Loading branch information
zer0trip authored and Rafase282 committed Apr 2, 2016
1 parent 7a17729 commit 2936f8d
Showing 1 changed file with 23 additions and 0 deletions.
23 changes: 23 additions & 0 deletions Sprint.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@

# **What is a Sprint?**


A **sprint** is a set period of time broken out from a project's overall timeline with associated tasks to be completed during that period of time. That list of tasks is referred to as the sprint's *Product Backlog*.


The ideology behind a *sprint* allows a larger timeline to be easily broken into smaller, more digestible pieces in order to focus effort from all stakeholders on a few logically scheduled tasks at a time.

All deliverables from a sprint must be accepted by the key stakeholders prior to moving to the next sprint and a project will have multiple sprints until scope has been met.

In most cases, a *sprint* begins with a planning meeting where the person or persons requesting the work meet with the developers in order to determine what work can realistically be completed during the time period, or sprint, being discussed. The developer will generally have the final say on what work will be completed during the sprint.

In some organizations these meetings will be overseen by either a Scrum Master or a Project Manager in order to ensure the overall goal of the project has been met after all sprints have been completed.

Sprints, on average, will last as much as 30 days or as little as a week depending upon both the size of the project, the number of tasks to be completed, and the number of resources available to work on the sprint's tasks.

In addition, in some organizations developers will meet daily to discuss project progress, needs, and roadblocks. These meetings are sometimes referred to as SCRUM meeting or Daily Stand-up Meeting. The person or persons are sometimes invited to listen however they are only in attendance as observers.

![sprint schedule](http://i.imgur.com/l8EAw1L.png "example of sprint schedule")

The above is an example of a sprint plan which has been laid out in six 30 day sprints. You can see that there is a Sprint Dev in each of the six sprints but from Sprint 2 on there is something labeled as a __Sprint # Increment__.

0 comments on commit 2936f8d

Please sign in to comment.