...
- Must have a leader assigned
- Must have X tickets for the sprint designed, not just created
- New developers should be able to pick up the ticket and know what needs to be done
- Each ticket should list the proposed solution in its description, or in a comment with the text "Proposed Solution".
- Must have an outcome / release for the end of the sprint
- Must have a sprint page created
...
During a Sprint
...
(for developers)
- You should not have to spend a large amount of time designing out a feature. (most things should be designed already though) If you go It should already have been designed before being included in the sprint.) If the design for a ticket is unclear, ask.
- If you spend, or expect to spend, more than 6 hours on a ticket/feature, bring it up to the group to make sure that its you are going in the right direction
Schedule of Sprints
2011
From | To | Topic | Leader |
|
|---|---|---|---|---|
March 21 | April 3 | |||
April 4 | April 10 | 2.x Dashboard Fragments | Learn the 2.x UI Framework by writing patient dashboard fragments | |
April 11 | April 17 | Bug fixes | TBD | Top-voted bug fixes, primarily from OpenMRS core/trunk |
April 18 | May 1 | 1.9 Feature: Web Services | TBD | Extending Web services |
May 2 | May 15 | Bundled Module: XForms | TBD |
|
May 16 | May 29 | 1.9 Roadmap Features |
| Order Entry? Visits? Concept Mapping? Multiple Providers? |
...