-
Notifications
You must be signed in to change notification settings - Fork 11
Sprint 8 deliverables [8 14 to 8 25] and next sprint planning
kasfaw edited this page Aug 28, 2017
·
6 revisions
High level tasks accomplished
- PDF export of progress reports for IP reporting, Annex-C part 2.
- Dashboard API for cluster complete; UI for Partner Dashboard complete.
- Results section UI complete for Cluster
- IP reporting needs for PMP API here: https://docs.google.com/document/d/1bvUAmNn8PbcWky8c7QWPaud-HRwvzOhvScA1nu2yFbo/edit
- Locations model designed for implementation
Sprint 9 planning
- Tasks available and ready in IP reporting in PRP milestone currently.
- Tasks available and ready in Cluster reporting in PRP milestone currently.
Open issues to discuss / agenda items
- How should Due/Overdue report statuses be calculated, if at all, or keep just "due" status.
- (verification) Optional reports on indicator for status Met and No Progress: https://github.com/unicef/etools-partner-reporting-portal/issues/259
- (verification) Cluster activity indicator progress calculations: https://github.com/unicef/etools-partner-reporting-portal/issues/184
Goals for next sprint
- Dashboard for Cluster IMO
- xls Export functionality for cluster in place based on finalized specification
- Locations model and sync from CartoDB complete
- Stretch goal: Analysis API's in place
- Disaggregation backend and frontend changes approved in last demo.
Action points/new tickets from showcase discussions
- Locations: work with UNICEF team to see if there are further opportunities for validation, etc
- Recheck Dashboard components and ensure API endpoint is complete and serving frontend
- QA/Testing considerations should include simulation in low bandwidth settings: https://github.com/unicef/etools-partner-reporting-portal/issues/275
- IP Reporting: authorized official only person submitting - more discussion to specify roles and permissions for IP Reporting
- Followup with UNICEF on Annex C Part 2 format feedback
- Followup with UNICEF on reporting frequency and due dates are implemented in PMP (possible changes on how IP Reporting determines reporting due dates)
- refer to PMP user stories on due/overdue logic
- Cluster reports can follow same logic
-
Followup on location aggregation for each cluster activity indicator
- need to prioritize features and whether this is a show stopper for v1