How To use This Page
Blue headers take you through the steps of your project. (Prior to design, Design, Kickoff Meeting, During, and Post Project Wrap up)
Information 
show areas where you need to fill out information to have a successful project, most information is optional, but the more you fill out the easier it is for others within the community to help.
Ask Kiran Reddy or Chris Power for help if you have any questions.
Tasks To Be Completed Prior To Design
...
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.
...
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”.
| Info | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This is the first one. You're the only core OpenMRS developer assigned to it, and we won't be advertising in the broader community. The goals of this 2-week sprint are:
1st Sprint: Appointment Scheduler Should Have: 1st Sprint: Having the ability for the appointment scheduler to fill in the Que
Could Have: Won’t Have: |
Quick overview Notes
...
| Info |
|---|
Topic: Visit Scheduling or Queueing Lead (Product Owner): Tobin Known Developers Assigned (amount of effort in hrs dedicated to this work if possible): ~yony258, ~quix, ~dkayiwa Date: Start: TBD November 22nd |
How to Participate
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.
...