Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Sprint 12 - Sprint Review/ Retrospective
- Brad Fernandes (Unlicensed)
Analytics
Date | Feb 23, 2021 |
|---|---|
Team | TAP Product Line |
Project Participants | @Brad Fernandes (Unlicensed) @Jules Levin @alexia nicholson (Unlicensed) @Rachel Forbes @john.humphreys @Monica Kluegel @Manpreet Sidhu @Sidra Zafar @Himanshu Raikar (Unlicensed) @The Ho Trang @Yeng Sembrano @AlainGasquet@Chanel Zheng @apirami.kumaradevan@alexia nicholson (Unlicensed) |
Background
Sprint 12 priorities were -
Compliance - Receipt/ Gift Processing
External stakeholders & Mass communications
Internal TAP
Finalise Data conversion
Sprint 12 was limited to 9 business days due to TAP planning day (17/02). Additionally, ICT integrations team worked for 6 days on the Sprint as they were re-directed to Curriculum Timetable (CT) and Workday projects.
Despite the time above constraints, the team closed out 62 tickets (Done + Cancelled).
Statistics at the end of Sprint
Retrospective
Conducted using IdeaBoardz to collaborate and gather feedback. Participants were given an opportunity to vote on the feedback for discussion.
What went well? | |
Point | Votes |
Focus on core priorities to ensure proper gift processing / data mapping fixing | 4 |
Collaboration team work among task assigned work well | 1 |
Integrations are activated in Prod and number of issues identified have reduced. | 0 |
Teams Team Teams | 0 |
Systems knowledge and best practices shared with team members | 0 |
What can be improved? | |
Point | Votes |
Take into account capacity when Sprint planning | 2 |
redistribution / planning of stories towards future sprints | 1 |
Team collective energy needs to be re to be waning. | 1 |
Back to parallel handling BAU and Sprint work | 0 |
Action Items | |
Point | Votes |
Clear workload estimation of what is possible to manage within one sprint | 2 |
Transparency regarding priorities by sprint / identifying what success looks like | 0 |
Have a working group to complete data conversion testing. YS, MK, JH - Gifts, Recurring Gifts TT - Tax appeal, MS, SZ - Opportunities, CG, PD H -Receipting, iMods, | 0 |
Small sprint update shared after each sprint to the TAP Phoenix teams chat | 0 |
Build in sprint breaks to refocus and catch up - after 19th March - 4 week break? | 0 |
Decommission planning | 0 |
