OSE Scrum Process: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The OSE Scrum Process is a process adapted from Scrum to the particular needs") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
The OSE Scrum Process is a process adapted from [[Scrum]] to the particular needs | The OSE Scrum Process is a process adapted from [[Scrum]] to the particular needs of of a collaborative, scalable, open source, product (goods and services) development pipeline. The process has the intent of allowing many of the 87 steps to be taken in parallel - especially when a team is working in real-time 24/7 around the globe. The key is high granularity for allowing massive parallel development. | ||
Basic scrum procedure involves: | |||
*Daily standup with video broadcast, recording, and call-in for remote members. | |||
*Workshop where people pair, cross train, and pull together (swarm) on a problem if needed. | |||
*Task board with backlog | |||
*Weekly (or other duration) sprints | |||
*Planning via estimation of time requirements*Weekly (or other duration) sprint | |||
*Product Demo- at end of Sprint - broadcast, recorded, and call-in. | |||
*Sprint Planning | |||
*Online platform - XM Project Page | |||
*Constant evolution for local development at FeF and global collaboration. | |||
*Ongoing external feed of expertise, advice, and Flash Mobs | |||
[[Category:XM]] | |||
Latest revision as of 03:38, 2 April 2012
The OSE Scrum Process is a process adapted from Scrum to the particular needs of of a collaborative, scalable, open source, product (goods and services) development pipeline. The process has the intent of allowing many of the 87 steps to be taken in parallel - especially when a team is working in real-time 24/7 around the globe. The key is high granularity for allowing massive parallel development.
Basic scrum procedure involves:
- Daily standup with video broadcast, recording, and call-in for remote members.
- Workshop where people pair, cross train, and pull together (swarm) on a problem if needed.
- Task board with backlog
- Weekly (or other duration) sprints
- Planning via estimation of time requirements*Weekly (or other duration) sprint
- Product Demo- at end of Sprint - broadcast, recorded, and call-in.
- Sprint Planning
- Online platform - XM Project Page
- Constant evolution for local development at FeF and global collaboration.
- Ongoing external feed of expertise, advice, and Flash Mobs