...
- 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
...
From
...
To
...
Topic
...
Leader
...
...
May 21
...
June 3
...
...
...
Full team 2 week sprint
...
...
...
June 4
...
June 17
...
CleanUp Sprint: REST Web Services, Order Entry, Calculation
...
...
Full team 2 week sprint
...
...
...
June 18
...
July 1
...
Reporting and HTML Form Entry
...
??
...
2 weeks, full team
...
TBD
...
XForms
...
...
Daniel lead, but doesn't code
...
...
TBD
...
Export of HL7 messages
...
...
...
2 weeks, full team
...
TBD
...
Patient Summary
...
...
]
...
(2 week sprint, 1 more core dev)
...
TBD
...
"App"/UI Framework
...
...
]
...
TBD
...
TBD
...
Operationalize dispensing: open boxes integration
...
...
]
...
TBD
...
TBD
...
Import and Export of CCD
...
TBD
...
2 week, Paul, Burke, 2 jembi devs, 1 core dev
...
TBD
...
Merge metadata localization branch
...
1-2 devs, 2 weeks
...
TBD
...
2.0 UI?
...
TBD
...
TBD
...
| Include Page | ||||
|---|---|---|---|---|
|