...
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:
Won’t Have: |
Quick overview Notes
3 basic user roles
Admin: Setting schedules for (Dr., volunteers, etc), configuring basic options (example room assignments)
Receptionist: Making appointments, Accepting patients (registration)
Clinicians: See the list of patients, and see patient dashboard
Admin
1. Configure Spaces
setup room 1,2,3
2. Configure Appointment Types (gyno, family, Radiology)
type of appointment and length of appt (helps figure out how much time a room is busy for)
3. Resource scheduling
Receptionist
1. List of appointments with a status of "scheduled"
a. ability to check them in, and announces to clinician that they are here. Starts and Encounter
2. Creating appointments
a. Selecting a clinician for your need, and then it will automatically show times available
b. AI algorithmic way to make efficient (min max rooms and doctors)
Clinican
1. Time tracking starts (how long were they waiting, how long (insert variable metric)
General Info
Quick overview Notes General 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: November 22nd - December 6
| Info |
|---|
How to ParticipateThis 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:
|
Backlog
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
| Info |
|---|
Tickets involved: |
Design |
...
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 have happened 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.Looking at creating 3 parts (Possibly 2/3 different sprints) 1. Structure issues w/OpenMRS and Pair program 1 Core Dev in a complementary timezone 2. Get more people involved with core features This is where the community gets involved 3. Once in place some feedback from users to make changes. Looking to see if we an build this incrementally 1. A separation of API and UI Design Call 11/7 Proposal
|
...
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.
- Developers need more experience with the OpenMRS framework/models
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
| Info |
|---|
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. Sprint break down: https://www.dropbox.com/s/cldus4rbu4mp777/User%20Stories%20v2.pdf Kickoff Meeting |
...
Kickoff meeting Date: TBD (Meeting setup with known developers after the final design meeting, but prior to the start date): |
| Info |
|---|
Kickoff Meeting Checklist
- Do we know where we are going? (Yes/No)
- Do we know the problem we are solving (yes/no).
- Do we have a complete backlog of items to complete this work? (yes/no)
- Do we know our scope and priorities? (yes/no)
- Have we defined success? (yes/no)
- Do we know how to get there?
- Do we have any unknowns to be decided during the sprint? If Yes what are they?
- Do we know who is doing what on our project? (yes/no)
- Do we have a test to complete prior to completion beyond our normal submit process? (Yes/No).
- Do we have a high level architecture that is understood by the whole team? (This page fully completed will accomplish this) (Yes/No)
- Do we know the biggest constraint that is likely to inhibit our success? (Yes and no) If no what is it?
- Is this a part of a larger story or epic? (Yes/No) If Yes please link
- Are we set up to succeed?
- Do we have the right people? (yes)
- Have we cleared the decks of all other distractions?
Info During Project Notes
...
| Iframe | ||||||
|---|---|---|---|---|---|---|
|
| Iframe |
|---|
| Info |
|---|
Post Project (Retrospective) |
| Info |
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?
| Info |
|---|
Resources
Kickoff meeting recording: ??