Please note that performance does NOT include meetings, design work nor testing. Points do not reflect all the work completed but are the best measure at this time and help us understand where the effort is during the sprints.
Team Feedback
Mind the Gap (Sam):
Sprint 109 - Some vacation, started work on mCSD, 3.4.1 testing and release
Difficult to get actual work into tickets
Need to work on better breaking down work into tickets that represent actual work performed (or to be performed). Also need to improve planning for feature work.
JSI (Ashraf):
Sprint 109 - Caught with Definition of Done, a number of tickets in Review and QA at end of sprint
Communication difficulties with Sam away for testing
Team schedule was not taken into account during sprint planning
Assisting Ona team for superset reports was not captured in a ticket
What can we do to help?
Will communicate with VR (Wes) when blocked (ie, tickets not getting tested)
Current process is to ask for someone to QA tickets, not that tickets are automatically picked up. The #QA Slack channel can be used for this.
Ona (Craig):
Critical meeting at the end of Aug to define the scope for the reporting stream
This really helped to focus the team and create a work plan for the work going forward
3.4 release very focused on devops (foundation work), 3.5 is focused on creating gap reports
Planning for 3.6 should follow similar pattern to help define scope
DHIS2 will likely be scheduled
Support other teams to be able to build on top of reporting stack
Planned as part of Gap project for Jan 2019
Primarily focused on report-stack-specific work, not as much on general OLMIS work
Trying to funnel work to "best" team so that time is not spent getting up to speed on things that another team could do faster