Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS »
Discussion: OpenMRS Talk »
Real-Time: IRC Chat

Resources

Skip to end of metadata
Go to start of metadata

If you are considering hosting or having a sprint, please see How-To Have a Sprint for best practices

This page is out of date and does not reflect our current active sprints. Please check with devs on IRC (http://irc.openmrs.org) for now until we get this page updated with current information.

 

The OpenMRS core development team uses the a semi agile sprinting mechanism for getting features written in a coordinated fashion. This allows new features to move forward at a quick pace. It also distributes the knowledge of different features to a wider audience.

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
    • not everyone needs to be assigned to every topic.
  • We 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, 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.)
    • The sprint leader should give an 'estimated time' for each ticket in a sprint.
    • Developer should log the total number of hours he/she spent on a particular ticket.
  • 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 in our 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

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
    • 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

Being a Sprint Leader

See the Being a Sprint Leader page

During a Sprint (for developers)

  • You should not have to spend a large amount of time designing out a feature. (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 you are going in the right direction

Schedule of Sprints

(included from the Sprint Schedule page)

On this page:

2013 Development Sprints 

Sprint schedule calendar

Sign up for a sprint!

Want to join a sprint that interests you?

  1. Find a team to the left to join and click it.
  2. Click the "Edit" link.
  3. Add your name in the "Who" field and click OK.

If you can only participate in part of a sprint, click the "Add Event" button to the left and add your name and the days you are available.

Active sprints

We are using JIRA Agile Board for organizing sprints. If you want to learn what we are currently working on and what are the available tasks, go to

jira OpenMRS Sprint Board

All active sprints are listed at the top following the "Sprints:" label. Sprints are named starting with a date when the sprint began followed by the topic e.g. 2016-11-29 Platform 2.1.0 or 2016-12-06 Android Client.

Usually we have one active sprint, but at times it may be more sprints running in parallel. You can switch between different sprints by simply clicking on them, which should load a page containing issues for that sprint.

Issues are organized in 5 columns: In Desing, To Do, In Progress, In Review, Done. You are welcome to pick any issue from the To Do column by simply opening it and clicking Claim.

When you are done you should click Request Code Review and provide a URL to a pull request on GitHub in comments under the issue.

Once your solution is accepted, your code will be merged and the issue moved to the Done column. If it requires more work, it will be moved back to the In progress column. You need to respond or make changes and Request Code Review again. Do not get discouraged as the process may take a few rounds of code reviews until a pull request is accepted. It is expected as we aim for the highest code quality.

Please explore Developer Guide to learn more about developing code for OpenMRS.

Sprint list

From

To

Topic

Product Owner

Lead Developer

Developer Effort Estimated

Kickoff Meeting Held?

Goals Outlined?

Retrospective Completed?

2017-02-072017-02-21Cohort Builder SprintStephen Senkomago MusokeOnodje Daniel  Yes 
2016-11-292016-12-13Platform 2.0.1 Sprint 1 Rafal Korytkowski   
2016-11-152016-11-29Open Concept Lab Sprint 3  Rafal Korytkowski    
2016-11-012016-11-15Open Concept Lab Sprint 2Jonathan PayneRafal Korytkowski    
2016-02-142016-02-23Platform 2.0 Beta - RESTWSOpenMRS CommunityMayank Sharma NoYes 
2016-01-172016-01-31Platform 2.0 BetaOpenMRS CommunityMayank Sharma  YesYes
2015-07-272015-08-07Admin UITBDWyclif Luyima NoYesNo
2015-01-082015-01-25Registration v2David DeSimoneWyclif Luyima YesYesNo
2014-11-102014-11-14OpenMRS Platform 1.11 pre-alpha-release testing and bug fixingOpenMRS CommunityKaweesi Joseph NoYes 
2014-10-272014-11-10Working on OpenMRS Platform 1.11 Release Test Failed ticketsOpenMRSKaweesi Joseph  Yes 
2014-10-122014-10-26Testing OpenMRS Platform 1.11 Release Tickets Sprint 3 - 2014 (iteration 3)OpenMRS communityKaweesi Joseph  Yes 
2014-10-072014-10-21Allergies (Iteration 4)Jonathan Teich, ShashaDaniel Kayiwa  Yes 
2014-08-142014-08-28Testing OpenMRS Platform 1.11 Release Tickets Sprint 2 - 2014 (iteration 2)OpenMRS communityKaweesi Joseph  Yes 
2014-07-302014-08-13Testing OpenMRS 1.11 Release Tickets (iteration 1)OpenMRS communityKaweesi Joseph  Yes 
2014-09-012014-09-15Allergies (Iteration 3)Jonathan Teich, ShashaDaniel Kayiwa  Yes 
2014-03-182014-03-31Order Entry (Iteration 5)JSS, KenyaEMR, OpenMRSWyclif Luyima Google HangoutYes

 

 

2014-02-252014-03-17Order Entry (Iteration 4)JSS, KenyaEMR, OpenMRSWyclif Luyima Google HangoutYesYes
2014-02-042014-02-24Order Entry (Iteration 3)JSS, KenyaEMR, OpenMRSWyclif Luyima Google Hangout

Yes

Yes
2013-12-162014-02-03Order Entry (Iteration 1 & 2)JSS, KenyaEMR, OpenMRSWyclif Luyima Google HangoutYesYes
  Reporting SprintJames ArbaughMike Seaton NoYes 

Sprints In Planning

Name

Product Owner

Lead Developer

Goals Outlined?

Next Planning Meeting

Next Design Meeting

Estimated Start Date

Kickoff Meeting

Comments

External Authentication

Svend / Bill Lober

Darius Jazayeri (TBD)

 

 

 

 

 

 

App Framework

 

 

 

 

 

??

 

 

HTML Form Entry

James Arbaugh/Ampath

 

 

 

 

??

 

 

Module Architecture SprintDarius or Rowan or Mike SeatonBen or any devYes    See 2013-06-13 Developers Forum minutes
Spike on moving Audit Log Module into core?? Probably Roger FriedmanWyclif      
Performance AnalyticsHamish Fraser Yes     
OpenMRS-HMISWesley Brown No     
Ad Hoc Analysis Tool (Cohort Builder replacement) Darius Jazayeri     Version 1 of this is built (by Mirebalais). Goal of this sprint is to (1) add bells and whistles, (2) support searching more domain objects.
Allergy support in OpenMRS 2.x       Significant design conversations have already happened.
Clinician UI for Capturing Encounters in OpenMRS 2.xBurke Mamlin      Consider incorporating the Bahmni data capture tool into the Reference Application, with refactoring, i18n, etc.

Sprint Ideas (Not in any order)

Name

Product Owner

Developer Lead

Suggested Developers

Initial Discussion Date

Comments

Import/Export of CCD

Burke/Paul

 

 

 

 

Reporting Module Renderers

Mike Seaton

 

 

 

 

Order Entry Wrap Up (Implementing the new Order Types)

 

 

Wyclif Luyima

 

 

Complete the hibernate-search branch

Rafal Korytkowski

 

 

 

Subtasks of TRUNK-2999

Publish and test the MVP dictionary with the dictionarypublishing module (1 dev spike)

Rafal Korytkowski

 

 

 

 

Cohort

Wes Brown(?), Suranga Kasthurirathne(?)

 

 

 

 

Atlas

 

 

 

 

 

Patient Data

Mike Seaton

 

 

 

 

Quarter Goals

Q1 

0%

Q1

Previous sprints

From

To

Topic

Leader

Developer Effort Estimated

Met Goals?

Designed Properly?

Kick Off Meeting?

Retrospective?

March 28

April 10

Reference Application iteration 0

Darius Jazayeri

All

2 wks

Yes

 

 

Mar 14th

Mar 27th

Sync

Mike Seaton

2 wks

Yes

 

 

 

Feb 28th

March 13th

Community Development Swim Lane

Wyclif Luyima, Rafał Korytkowski, Daniel Kayiwa

2wks

Yes

 

 

 

 

Feb 7th

Feb 27th

Merging the RESTWS and RESTWS-19ext modules

Roger Friedman , Rafal Korytkowski

3wks, 3D

Yes

Yes

Yes

Yes

Jan 24

Feb 6

Patient Summary

Joaquin Blaya, Mike Seaton

Daniel, Wyclif, Andrea, Mike, Rafal

Yes

Yes

Yes

Yes

Jan 9 2013

Jan 23

Reporting Module: integrating with Calculation module, integrating with MDS, etc

Mike Seaton

2 Weeks

Yes

Yes

Yes

Yes

Dec 24

Jan 8

Prep for Merging the RESTWS and RESTWS-19ext modules

Rafał Korytkowski

Rafal (spike)

Yes

Yes

No

No

01/08/1415/08/14Allergies (Iteration 1)Jonathan Teich, ShashaDaniel Kayiwa  Yes 
15/08/1429/08/14Allergies (Iteration 2)Jonathan Teich, ShashaDaniel Kayiwa  Yes 

Dec 10

Dec 24

Registration Core Module Sprint

Jeremy Keiper

 

Yes

No

No

Yes

November 22

Dec 6

Visit Scheduling or Queueing

Tobin Greensweig

 

 

 

 

 

Nov 7

Nov 20

Community Requested Issues Sprint and Mockito

Daniel Kayiwa

2 weeks, Wyclif on Mockito

N/A

N/A

N/A

N/A

October 24

November 6

Mirebalais User Interface Sprint

Darius Jazayeri

2 weeks, Wyclif and Daniel

N/A

N/A

N/A

Yes

October 1

October 21

Sharing Concept Dictionary

Rafał Korytkowski

3 weeks (Implementer Conference- Oct 9-12)

 

 

 

 

September 17  

September 30

Patient Summary Sprint

Mike Seaton

2 weeks, full team

 

 

 

 

September 10

September 16

RESTWS Mini Sprint

Ben Wolfe

1 week

 

 

 

 

September 3

September 9

Spikes by Core Developers

Ben Wolfe/Darius Jazayeri

1 week,

 

 

 

 

August 13

September 2

Your Votes Sprint

Ben Wolfe

3 weeks, full team

 

 

 

 

July 30

August 12

Export of HL7 Messages Sprint

Suranga Kasthurirathne

2 weeks, full team

 

 

 

 

July 16

July 29

Bug Fixing Sprint-July 2012

Rafał Korytkowski

Rafal lead & Volunteers

 

 

 

 

July 2

July 15

XForms Sprint 2

Daniel Kayiwa

Daniel lead, but doesn't code

 

 

 

 

June 18

July 1

Testing & HTML+Report Module Sprint

Ben Wolfe

Full team 2 week sprint

 

 

 

 

June 4

June 17

CleanUp Sprint - June 2012

Rafał Korytkowski

Full team 2 week sprint

 

 

 

 

May 21

June 3

Roles and Privileges Sprint

Daniel Kayiwa

Full team 2 week sprint

 

 

 

 

May 7

May 20

Event and AtomFeed Modules

Ben Wolfe

1 week, full team

 

 

 

 

Apr 29

May 5

Order Entry Wk 2

Mike Seaton

2 core developers

 

 

 

 

Apr 29

May 5

Minor drug table+ui changes

Jeremy Keiper

1 week, Jer + core dev

 

 

 

 

Apr 22

Apr 29

Atlas Module 1.0 - tickets

 

1 core Developer

 

 

 

 

Apr 22

Apr 29

Order Entry Wk 1 Design Prep

Wyclif Luyima, Mike Seaton

2 core developers

 

 

 

 

Apr 15

Apr 20

Get Web Services to 1.0

Darius Jazayeri

1 week. Darius, Rafal, Roger, Saptarshi, ?

 

 

 

 

Apr 15

Apr 20

Atom Feed Spike/Prep Wk 1

Ben Wolfe

2 weeks, Ben only

 

 

 

 

Apr 2

Apr 15

Reporting Module

Mike Seaton

 

 

 

 

 

Mar 26

Apr 1

Catchup Sprint

Ben Wolfe

 

 

 

 

 

Mar 12

Mar 25

Logic, take 2

Mike Seaton and Wyclif Luyima

 

 

 

 

 

Feb 27

Mar 11

Bug Fixing Sprint

Ben Wolfe

 

 

 

 

 

Feb 13

Feb 24

Pentaho

Darius Jazayeri

 

 

 

 

 

Jan 30

Feb 12

HTML Form Entry

Mark Goodrich

Planning notes: Ben missing first week

 

 

 

 

Jan 16

Jan 29

1.9 Beta bug fixes, Rest WS, SMART Container

Wyclif Luyima

Planning notes: Ben missing second week

 

 

 

 

Jan 2 2012

Jan 15

Metadata Sharing

Rafał Korytkowski

 

 

 

 

 

Also see the 2011 Sprint Schedule History