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 4 - Configurations Retrospective
- Brad Fernandes (Unlicensed)
Date | Nov 3, 2020 |
|---|---|
Team | Configuration/ Development, Product Owners, Affinaquest |
Participants | @Brad Fernandes (Unlicensed) @AlainGasquet @apirami.kumaradevan@Dev Subramanian (Unlicensed) @Jules Levin@Manpreet Sidhu @Monica Kluegel @Trevor Lindsey (Deactivated) @Yeng Sembrano @Griffin Homan (Deactivated) @Sidra Zafar @Rachel Forbes @alexia nicholson (Unlicensed) @john.humphreys @The Ho Trang |
Background
The Sprint objectives covered the following -
Reporting
Opportunities
Gift Administration
Community Giving
Change Management
Statistics at the end of Sprint
Cumulative Flow Diagram
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 |
Collaboration and Teamwork is still going strong. | 2 |
Sprint ceremonies are running well and on time. Team is sticking to the agenda. | 2 |
Great looking dashboards | 1 |
Great delivery by developers when properly briefed / given instructions | 1 |
Everyone's skills in configuring and using the system are levelling up | 0 |
All Products Owners are very helpful in making the clearer user story criteria | 0 |
What can be improved? | |
Point | Votes |
Bit of Sprint fatigue starting to kick in. Need some motivation. | 2 |
More hours in the day! | 1 |
Alerting when overworked for others to help / take over | 1 |
Alerting when decisions with potential impact on other streams are made (new data, validated source of truths, updated process, etc.) | 1 |
Harmonising the visuals of dashboards across the teams | 1 |
Prioritising core stories to be delivered for MVP> what would make MVP a failure if not working properly | 1 |
People should vote more :D | 1 |
on user story count, performance appears to be dropping | 0 |
Workload doesnt appear to be evenly distributed with some people having many more user stories than others. | 0 |
Block out periods in the week where there are no Project meetings. (Eg. Mon-Wed-Fri afternoon). This will enable the team to focus on deliver. | 0 |
wish to be able to just concentrate in the project, but there are BAU requests are still coming | 0 |
Action items
Action Items | |
Point | Votes |
Alert the team when changes (repurposing fields) are made (e.g. impacts to reports, dashboards) - USYD map -> Use TEAMS to communicate changes | 0 |
Communication on a new custom field alert with a brief on why and what it will be used for. -> Use TEAMS to communicate | 0 |
Re-prioritise the User Stories using MoSCoW so that the Development team can focus on 'Must Have'. | 0 |