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 23 [King Kong]
- Brad Fernandes (Unlicensed)
Date | Oct 26, 2021 |
|---|---|
Team | TAP Product Line |
Project Participants | @Brad Fernandes (Unlicensed) @john.humphreys @Liz Enright @Himanshu Raikar (Unlicensed) @Divyanshu Pandey (Unlicensed) @Anita Secerov @Sidra Zafar@Chanel Zheng@Abraham Thomas Karimpanal @Swathi Inapakolla @Monica Kluegel@The Ho Trang@AlainGasquet@Yeng Sembrano@Adriana Sung |
Apologies | @Manpreet Sidhu@apirami.kumaradevan |
Background
Sprint 23 achievement are listed as -
'Donor Relations Request' case queue to track work
Stewardship tiers setup
Activity report updates- Added Event
Data import wizard for ASR teams
End of year reports for ASR
Census report for 2021 for ASR
Opportunity Splits created and validation created not to exceed 100%
Log a Call functionality launched
New buttons to create Accounts -
New Corporation Account
New Organisation Account
Receipts - Restricted access to Notes & Attachments
Probability % - Opportunity field editable
Name definitions - Preferred, Alternate, Formal
@Himanshu Raikar (Unlicensed) - Clean up Prod data - Carmel Onions, Katja Forbes
Enhancements to the Event Brief
Report - Account/ Contact - Do not solicit
Opportunity to Gift - Development/ Testing in progress
Data cleansing for Phone data - Only in UAT
Probability score under 'Prospect Info' added to Contact
Mid-Tier leads dashboard created
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 |
Abe has been a great Scrum Master for the Sprint. Thank you! | 5 |
Opportunity to gift work is looking great! | 3 |
Good progress on the 'Opportunity to Gift' implementation | 1 |
Tickets were manageable this sprint (at least for me :) ) | 1 |
Limiting the number of tickets in the sprint to a manageable number | 1 |
Sprint break was good to help recharge and re-energise | 1 |
Great meeting duration and structure. | 0 |
What can be improved? | |
Point | Votes |
consider limiting sprint just to what can be done | 5 |
More description for user stories | 3 |
The percentage of tickets being completed each sprint. | 2 |
Stating rules of engagement for each type of meeting at the beginning to help with confusion. | 1 |
More structure in the sprint review to understand the business need and how is going to be helped/impacted by a new change | 0 |
consider more structure to sprint review including: 1. business context, 2. stakeholder alignment then demo | 0 |
Action Items | |
Point | Votes |
For outstanding tickets that end up being rolled over to the next sprint. It might be worthwhile to understand the following before automatically dumping them into the next sprint: (1) when they were created (2) when are they due (3) is the job still a relevant priority | 2 |
