...
Anyone interested in joining a sprint should let either the sprint lead know or just send a general request to be on one to the dev list.
Sprint Details
- Sprints are focused on one topic, and are usually 2 weeks long (
- some could be 1 or 3 weeks long as appropriate for the topic at hand
- Each sprint should include 2+ OpenMRS developers. We may occasionally have multiple sprints going simultaneously , as
- not everyone needs to be assigned to every topic.
- We should always try to decide on a sprint topic 4 weeks before it starts.Each sprint should will schedule and publicize Sprint topics ~4 weeks in advance
- this will give developers at other organizations a chance to organize their time to participate
- Sprints should always have a release in JIRA. The tickets in , unless they're around a core topic like "work on 1.9 tickets", in which case we'll use a "label" in JIRA.
- Tickets in the release should be partially organized one week before the sprint.
- They must be finalized by the day before the sprint.
- (The scope and tickets are locked-down once the sprint begins.)
- Each Sprint has a leader, who is in charge of the ticket list, and can help assign tickets to participating developers.
- All developers working on a Sprint should be in a real-time group chat
- We'll start by experimenting with Skype and a dedicated IRC channel
- To keep improving, each sprint ends with a retrospective look at what did and did not work with the previous week.
Weekly Emails
You should expect to see an email from Ben and Darius every week which will:
- (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
Schedule
2011
May
- 2nd - 16th: a module focused sprint
April
...
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 |
...
March
...
April 11 | April 24 | 1.9 Tickets | TBD |
|
April 25 | May 1 | Bug fixes | TBD | Top-voted bug fixes, primarily from OpenMRS core |
May 2 | May 16 | TBD (a module) | TBD |
|