...
- (either) summarize the status of the current Sprint
- (or) summarize the retrospective look at the last Sprint, and preview the next one
- this includes highlighting the developers and organizations that are participating in the Sprint
- give the calendar for upcoming Sprints
Designing a Sprint
These are required features that must be in place before a sprint can be started (or maybe even to just be scheduled)
- 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
- Must have an outcome / release for the end of the sprint
- Must have a sprint page created
Conventions During a Sprint
- Do not spend a large amount of time designing out a feature (most things should be designed already though)
- If you go more than 6 hours on a ticket/feature, bring it up to the group to make sure that its 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 24 | 1.9 Tickets | TBD |
| April 25 | May 1 | 17 | Bug fixes | TBD | Top-voted bug fixes, primarily from OpenMRS core/trunk |
April 18 | May 1 | 1.9 Feature: Web Services | TBD | Web services | ||||||
May 2 | May 16 | TBD (a module) | TBD |
|
Potential Sprints
- 1.9 Feature / Module: Web Services
- HTML Form Entry Module features
- HTML Form Entry Module bug fixes
- 1.9 Feature: Visits