Scrum: Difference between revisions

From Hive76 Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[image:800px-Scrum_process_svg.png|thumb|200px|right|SCRUM Process]]
[[image:800px-Scrum_process_svg.png|thumb|200px|right|Scrum Process]]
Hive76 uses a somewhat extended version of [http://en.wikipedia.org/wiki/Scrum_(development) SCRUM] to manage internal projects projects. The three primary concepts in our process are the [[SCRUM#Product Backlog|Product Backlog]], the [[SCRUM#Sprint|Sprint]], and the [[SCRUM#Stand-up and SCRUM wall|Stand-Up]].
Hive76 uses a somewhat extended version of [http://en.wikipedia.org/wiki/Scrum_(development) Scrum] to manage internal projects. The three primary concepts in our process are the [[Scrum#Product Backlog|Product Backlog]], the [[Scrum#Sprint|Sprint]], and the [[Scrum#Stand-up and Scrum wall|Stand-Up]].
== Product Backlog ==
== Product Backlog ==
* New stories are recorded in the [https://spreadsheets.google.com/ccc?key=0AsaJHIbJHv6MdF9UWVpEcGstUVZlTHZsMkloMk9pLXc&hl=en&authkey=CLGa3LwD Hive76 Product Backlog]
* New stories are recorded in the [https://spreadsheets.google.com/ccc?key=0AsaJHIbJHv6MdF9UWVpEcGstUVZlTHZsMkloMk9pLXc&hl=en&authkey=CLGa3LwD Hive76 Product Backlog]
* Anyone can add a new story to the product backlog at any time
* Anyone can add a new story to the product backlog at any time
* Each story should generally be completed within the time frame of 1 sprint
* Each story should generally be completed within the time frame of 1 [[Scrum#Sprint|Sprint]]
* Completed stories are moved to the "Done" sheet at the monthly Retrospective meeting
* Completed stories are moved to the '''Done''' sheet at the monthly Retrospective meeting
== Sprint ==
== Sprint ==
* Sprints are 1 month long
* Sprints are 1 month long
* Retrospectives will be held on the first Wednesday of every month to review progress, discuss what went well, and what could be improved.
* Retrospective Meetings will be held on the first Wednesday of every month to review progress, discuss what went well, and what could be improved.
[[image:Active-task-board.jpg|thumb|200px|right|SCRUM Wall Example]]
[[image:Active-task-board.jpg|thumb|200px|right|Scrum Wall Example]]
== Stand-up and SCRUM wall ==
== Stand-up and Scrum wall ==
* Stand-ups are held once a week, on Wednesday at 7pm sharp
* Stand-ups are held once a week, on Wednesday at 7pm sharp
* Stand-ups are led by the [[SCRUM#SCRUM Master|SCRUM Master]]
* Stand-ups are led by the [[Scrum#Scrum Master|Scrum Master]]
* Each participant will discuss what has been done since the last stand-up, what they plan to do for the next stand-up, and what issues they had.
* Each participant will discuss what has been done since the last stand-up, what they plan to do for the next stand-up, and what issues they had.
* Detailed discussion about a given task will be tabled until after the stand-up by the [[SCRUM#SCRUM Master|SCRUM Master]]
* Detailed discussion about a given task will be tabled until after the stand-up by the [[Scrum#Scrum Master|Scrum Master]]
* Only one person has the floor at a time, indicated by the Dora bat
* Only one person has the floor at a time, indicated by the Dora bat
* New tasks should be created for each story being worked on and placed into the '''Not Started''' lane
* New tasks should be created for each story being worked on and placed into the '''Not Started''' lane
* Tasks can only be added to or moved on the SCRUM wall at the stand-up
* Tasks can only be added to or moved on the Scrum wall at the stand-up
* Specific tasks should be broken up into portions that can be accomplished in 1 week's time
* Specific tasks should be broken up into portions that can be accomplished in 1 week's time
* Tasks in the '''Not Started''' lane are unassigned and can be picked up by anyone to work on
* Tasks in the '''Not Started''' lane are unassigned and can be picked up by anyone to work on
* When a task is accepted, the owner should mark the task with their initials and place the task into the In Progress lane
* When a task is accepted, the owner should mark the task with their initials and place the task into the '''In Progres'''s lane
* If a task is unable to be completed due to outside influences (vendors, people outside our group, etc.), they should be placed in the Blocked lane
* If a task is unable to be completed due to outside influences (vendors, people outside our group, etc.), they should be placed in the '''Blocked''' lane
* Already completed tasks can be placed immediately into the Completed lane
* Already completed tasks can be placed immediately into the Completed lane
* '''If you arrive after the stand-up has started, you should enter quietly to not disturb the participators'''
* '''If you arrive after the stand-up has started, you should enter quietly to not disturb other participants'''
== SCRUM Master ==
== Scrum Master ==
* The current [[SCRUM#SCRUM Master|SCRUM Master]] is Adam K.
* The current [[Scrum#Scrum Master|Scrum Master]] is Adam K.
== More Roles ==
* You can read about other standard Scrum Roles [[http://en.wikipedia.org/wiki/Scrum_(development)#Roles_2 here]]

Latest revision as of 23:00, 4 November 2010

Scrum Process

Hive76 uses a somewhat extended version of Scrum to manage internal projects. The three primary concepts in our process are the Product Backlog, the Sprint, and the Stand-Up.

Product Backlog

  • New stories are recorded in the Hive76 Product Backlog
  • Anyone can add a new story to the product backlog at any time
  • Each story should generally be completed within the time frame of 1 Sprint
  • Completed stories are moved to the Done sheet at the monthly Retrospective meeting

Sprint

  • Sprints are 1 month long
  • Retrospective Meetings will be held on the first Wednesday of every month to review progress, discuss what went well, and what could be improved.
Scrum Wall Example

Stand-up and Scrum wall

  • Stand-ups are held once a week, on Wednesday at 7pm sharp
  • Stand-ups are led by the Scrum Master
  • Each participant will discuss what has been done since the last stand-up, what they plan to do for the next stand-up, and what issues they had.
  • Detailed discussion about a given task will be tabled until after the stand-up by the Scrum Master
  • Only one person has the floor at a time, indicated by the Dora bat
  • New tasks should be created for each story being worked on and placed into the Not Started lane
  • Tasks can only be added to or moved on the Scrum wall at the stand-up
  • Specific tasks should be broken up into portions that can be accomplished in 1 week's time
  • Tasks in the Not Started lane are unassigned and can be picked up by anyone to work on
  • When a task is accepted, the owner should mark the task with their initials and place the task into the In Progress lane
  • If a task is unable to be completed due to outside influences (vendors, people outside our group, etc.), they should be placed in the Blocked lane
  • Already completed tasks can be placed immediately into the Completed lane
  • If you arrive after the stand-up has started, you should enter quietly to not disturb other participants

Scrum Master

More Roles

  • You can read about other standard Scrum Roles [here]