| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Background
Sprint 17 achievement are listed as -
Cyber Security Penetration testing completed
Stata and MiniTab licenses procured and Predictive modelling commenced
Aperture DS training commenced.
Updates to the Pledge reminder notice
Enhancements to Peoplesoft files
Gift in Will stage
Updates to Opportunity - Ask amount,
Community Giving Dashboards
Funds raised by Alumni
Optimise the flows for Gift processing - Raised with Salesforce
Gift club memberships
Data conversions fixes to Addresses (suburbs)
Receipts to be on-hold -
Annual receipts
Event registration
Updates to CG dashboards
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 |
longer sprint period | 5 |
clear on stories to focus on (i.e. PowerPoint @ Standups) | 2 |
anshu completed first phase of speadsheet upload to batch items | 1 |
Balancing with BAU to address users' feedback / needs | 0 |
3 weeks sprint！ | 0 |
Have breathing space to deal with BAU and Sprint works | 0 |
We still like each other! | 7 |
Good team communication and collaboration | 3 |
clear goals in place | 2 |
Technology Roadmap provides a framework of priorities for 6 months | 2 |
Big ticket items being completed | 0 |
In office face to face discussions about different tasks help a lot in navigating it to completion. | 0 |
3 week sprint is a good idea | 0 |
What can be improved? | |
Point | Votes |
Stand-up meetings - Focus 1 activity for the day and ask team for help. | 1 |
Standups could be less frequent if working on larger ticket items | 1 |
Advise team of any planned leave | 1 |
can I suggest we reduce the standups to twice weekly and make them longer, allowing time to discuss issues with the groupbetter understand what resources are available for planning | 1 |
Focus on blocks of stories / functions to consolidate adding value per sprint (no spreading across too many elemenets) | 0 |
Mapping dependencies / stress period for external stakeholders (e.g. ASR with appeals, EOY, etc.) | 0 |
ensure must have items are allocated to a developer at the start of the sprint so we know what we can deliver | 0 |
Action Items | ||
Point | Votes | communicate all progress to stakeholders [e.g. Sprint achievements] |
0Drinks | 3 | |
...
