From cc987e8dbc8cdcbfde83b0e4bf7707041d32b810 Mon Sep 17 00:00:00 2001 From: Sean Date: Fri, 1 Apr 2016 15:22:33 -0400 Subject: [PATCH 1/5] Create WhatIsASprint.md --- WhatIsASprint.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 WhatIsASprint.md diff --git a/WhatIsASprint.md b/WhatIsASprint.md new file mode 100644 index 000000000..ecb355166 --- /dev/null +++ b/WhatIsASprint.md @@ -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. + + +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. + +Generally 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. + +A *sprint* generally 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__. This will be further elaborated on in a future wiki article. + From aa27041228a62fed2745822c0d09270f32733bf4 Mon Sep 17 00:00:00 2001 From: Sean Date: Fri, 1 Apr 2016 19:31:06 -0400 Subject: [PATCH 2/5] Update WhatIsASprint.md --- WhatIsASprint.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/WhatIsASprint.md b/WhatIsASprint.md index ecb355166..5de66db4b 100644 --- a/WhatIsASprint.md +++ b/WhatIsASprint.md @@ -2,14 +2,14 @@ # **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. +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*. -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. +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. -Generally 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. +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. -A *sprint* generally 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 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. @@ -19,5 +19,5 @@ In addition, in some organizations developers will meet daily to discuss project ![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__. This will be further elaborated on in a future wiki article. +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__. From a943fce09b018d675a99e4f7df5e0b70e89a4d56 Mon Sep 17 00:00:00 2001 From: Sean Date: Fri, 1 Apr 2016 19:36:01 -0400 Subject: [PATCH 3/5] Rename WhatIsASprint.md to What-Is-A-Sprint.md --- WhatIsASprint.md => What-Is-A-Sprint.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename WhatIsASprint.md => What-Is-A-Sprint.md (100%) diff --git a/WhatIsASprint.md b/What-Is-A-Sprint.md similarity index 100% rename from WhatIsASprint.md rename to What-Is-A-Sprint.md From 2850abe9daa973e219075e5579a70d9e052df0b6 Mon Sep 17 00:00:00 2001 From: Sean Date: Fri, 1 Apr 2016 23:19:34 -0400 Subject: [PATCH 4/5] Rename filename --- What-Is-A-Sprint.md | 23 ----------------------- 1 file changed, 23 deletions(-) delete mode 100644 What-Is-A-Sprint.md diff --git a/What-Is-A-Sprint.md b/What-Is-A-Sprint.md deleted file mode 100644 index 5de66db4b..000000000 --- a/What-Is-A-Sprint.md +++ /dev/null @@ -1,23 +0,0 @@ - -# **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__. - From 9b04a6cc1d46232f8c0b395630ea773a4e950832 Mon Sep 17 00:00:00 2001 From: Sean Date: Fri, 1 Apr 2016 23:19:56 -0400 Subject: [PATCH 5/5] Rename filename --- Sprint.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 Sprint.md diff --git a/Sprint.md b/Sprint.md new file mode 100644 index 000000000..5de66db4b --- /dev/null +++ b/Sprint.md @@ -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__. +