Scrum: Difference between revisions

From Hive76 Wiki
Jump to navigationJump to search
No edit summary
No edit summary
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 Product Backlog, the Sprint, and the Stand-up.
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]].
== 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]
Line 6: Line 6:
* 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 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
== Sprints ==
== 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.
* Retrospectives will be held on the first Wednesday of every month to review progress, discuss what went well, and what could be improved.
Line 12: Line 12:
== 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 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 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
Line 24: Line 24:
* 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 the participators'''
== SCRUM Master ==
* The current SCRUM master is Adam K.

Revision as of 16:00, 4 November 2010

SCRUM Process

Hive76 uses a somewhat extended version of SCRUM to manage internal projects 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
  • Retrospectives 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 the participators

SCRUM Master

  • The current SCRUM master is Adam K.