Added by James Dixon, last edited by James Dixon on Dec 21, 2007  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
10. Open Scrum by the Numbers Home 12. Summary

In the comparison table above I distinguished between open source and commercial open source projects where it was appropriate. This is because Open Scrum should adapt well to either model but the differences between the two should be acknowledged.

Even though Open Scrum has been created to meet the specific needs of open source and commercial open source projects there are some useful ideas in here for traditional closed-source, proprietary projects:

  • Adding hardening information to the Product Backlog.
  • Soliciting for stake-holders at the start of each Sprint. In many projects there are features specific to individual groups within the customer. Re-evaluating the stake-holders once the Sprint Backlog will allow these groups within the customer to know what, if anything, to expect that month.