Topic: Registration Core Module
Lead (Product Owner): Unknown User (jeremy)
Known Developers Assigned (amount of effort in hrs dedicated to this work if possible):
Date: 14 Dec 2012 - 21 Dec 2012
This module will provide basic registration services for other modules to use when registering new patients. It will not have a UI of its own aside from administrative management, but will eventually provide UI widgets to facilitate building a registration form in another module. The objective of this module is to hone the registration process to a single methodology, so an implementation can focus on the data being collected rather than how use the various API services to create all necessary data involved in the process of registration.
Please clone, compile and read up on the AMRS Registration Module. This is not a reference application, but is an example of a functioning registration module. Pay attention to how filling out the form affects the search results, how a user might interact with it and what code is used in the controller. My hope is that most of this controller code will be replaced with simple calls to methods in the new Registration Core Module.
After this, please fork the OpenMRS Registration Core Module to your repository so we can begin work together.
Kickoff meeting Date: 14 Dec 2012 9:30am Eastern Time in #openmrs on IRC
(Meeting setup with known developers after the final design meeting, but prior to the start date):
Kickoff Meeting Checklist
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:
These are a combination of parent tickets with child tickets underneath to break up the work or tickets needed for completion of the work. These tickets should be made in as much detail as possible going into the design calls through use of the mailgroups and small group design meetings. Larger design calls will be used to answer questions these groups cannot or for the community to resolve.
All tickets should have in their description a DOD (Definition of Done) or what it should have accomplished
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 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.
Add notes, comments, concerns, that occurred during the sprint that should be noted to help in the retrospective.
Did we complete tickets to a 100% DOD? (Yes/No) if no, have those tickets been assessed and placed for future work if needed?
What did we do well?
What could we do better?
What should we not do again?