Topic: Reporting Module Renderers
Type of Project (Spike, Sprint, Epic): Sprint
Lead (Product Owner): Mike Seaton
Known Developers Assigned (amount of effort in hrs dedicated to this work if possible):
Source code at:
This first sprint for the Appointment module will not be advertised to the whole community however those interested in working with us on future sprints should contact us!
Add your name to the list on this wiki page (with any comments about your availability). If you want to join after the sprint has started just join the IRC channel mentioned above and say hello.
The general process:
Goals: Must Have, Should Have, Could Have and Won’t Have
Must Have means we must have this as part of the solution. It is a requirement or we should rethink doing this work. This is what we will deliver before the end of the work period this also doubles as our DOD “Definition Of Done”
Should have means we would be embarrassed not to have it. We could technically produce the solution without it but people would be surprised.
Could have means anything else we could do. But this does not always mean low priority. But our selection of which could haves to include or exclude (or deliver later). Also is considered low hanging fruit (if we are in this code already for x reason wecan deliver y with little or no extra effort) or can be items or ideas for this module that can be packaged for a later spike or sprint.
Won’t Have means this will not happen. It might be technically impossible, a taboo for our organization or out of scope. It does not mean “might happen or would be nice”.
Must Have: (eg. the driver for the Sprint)
1. Finish off integrating the Birt module as a renderer within the reporting module (tie off GSoC project from last summer) -
2. Implement a renderer that can output to a Word document (might be handled by #1, or by doc4j, poi, or another library) -
3. Replace the generic ReportDesign editor UI with custom UIs for each Renderer type
There should be multiple design meetings. The first starts off with a small group working with the leader to determine the high level scope of the project and then to break down into smaller pieces to eventually place as tickets. Once those meetings havehappened use of the community design meeting time should be used to refine the tickets and if possible assign them to who will be doing the work.
Risks (these should be resolved prior to or during the design meetings):
Enter anything that is still questionable or worrisome that has not been answered: (open issues, potential concerns) Once a decision is made make sure that a summarized answer is included.
Example: Q. How will we handle issues with conflicting userID’s? A. All ID’s will have an added identifier that is unique.
Effort Accounted For: (At the end of the design call all tickets should have an estimated effort and that total should be balanced against the known available effort of the developers assigned) (Yes/No)
If not in balance in favor of success why and the action plan for remaining items
via IRC on the [#openmrs|IRC:Home] channel on freenode.
Use this channel for ALL debugging and random questions having to do with the sprint. Please avoid direct messaging to personal contacts. If you have a question, someone else most likely does too, and our geographically distributed community benefitsfrom public group discussion.
Sprint Break down: If tickets have not already been laid out or explained this is a good place for this.
Enter anything that is still questionable or worrisome that has not been answered: ?
Effort Accounted For: ?
Sprint Break down: ?
Kickoff meeting Date: TBD
Kickoff meeting recording:
(Meeting setup with known developers after the final design meeting, but prior to the start date):