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

Article: Sprint Workflow #656

Merged
merged 5 commits into from
Apr 2, 2016
Merged

Article: Sprint Workflow #656

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
cc987e8
Create WhatIsASprint.md
zer0trip Apr 1, 2016
aa27041
Update WhatIsASprint.md
zer0trip Apr 1, 2016
a943fce
Rename WhatIsASprint.md to What-Is-A-Sprint.md
zer0trip Apr 1, 2016
2850abe
Rename filename
zer0trip Apr 2, 2016
9b04a6c
Rename filename
zer0trip Apr 2, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions WhatIsASprint.md
View file
Open in desktop
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 <b>Product Backlog</b>.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want to make it bold, just double asterisks are enough. You don't need any underscore in between.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't use HTML tags. You are writing in markdown, which would then be compiled to HTML. So use MD specific syntax highlighter.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is my first time using markdown and was attempting to both bold and add italics. As for the second comment, I am aware of what markdown does but thank you for the explanation.



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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you yourself have described earlier, sprint is the slice of a larger timeline. That means this sentence cannot be true. Because sprint is not the process of breaking it down.

What allows for a larger timeline to be broken into pieces is human decision making, and sprint is the result of that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not describing sprint as the process but as a tool or goal. The ideology behind a sprint allows. I have no issue adding this clarification if you still feel it is needed. Everything discussed it a product of human decision making, therefore that is not a valid comment to add.


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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the first time, you are using the phrase "Scrum Master". So, either define it. Or, link to external resource.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is also the first time I am using the term 'Project Manager' also 'Product Backlog'. I would like to come back later once I have written those articles and add those as links to other FCC wiki's.


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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The last line is not needed. If you add that wiki article, come back to this one and add a link to it. Until then, no need for the announcement.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This a fair comment thank you.