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 15 [Cake]
- Brad Fernandes (Unlicensed)
Date | May 4, 2021 |
|---|---|
Team | TAP Product Line |
Project Participants | @Brad Fernandes (Unlicensed) @alexia nicholson (Unlicensed) @Rachel Forbes @john.humphreys @Manpreet Sidhu @Sidra Zafar @Himanshu Raikar (Unlicensed) @The Ho Trang @Yeng Sembrano @AlainGasquet@Chanel Zheng @apirami.kumaradevan@Monica Kluegel |
Apologies |
|
Background
Sprint 15 achievement are listed as -
[BF] Aperture DS setup
[BF] Salesforce Architect reviewing Jarvis (Dev environment setup)
[YS] Transactions designation (100k records)
[YS] Chinese addresses (Contact/ Account)
[YS] Automation of Opportunity split
[YS] KPI counting
[MS] 2 flows
Staff member updates campaign member status > workflow registers anyone who has a particular status to linked event > workflow also updates registration as guest
Created a flow that creates the different types of member status' when ‘Event Invitation’ campaign type is created to standardise these status' to ensure the above flow runs smoothly
[MS] Relationships with Contacts
[HR] Added Tax to the Dues transactions
[HR] Updates to Receipts (i.e. Printed date, Sent date)
[HR] Populating batch items - Oct and Nov batches
[SZ] Pledge reminder field - Batch item
[SZ] Account readiness migration to Affinity
[SZ] Migrate Prospect stages
[MK] Implementation of Dues batch
[MK] New receipts for Dues
[AG] Enhancements to KPI reports
[AG] New dashboard for Joel Smith
[AG] New reports for Alumni
[AG] Updates to Probability scoring
[CZ] User goals and KPI dash
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 |
At least one deliverable for each team e.g. ASR, PD, Dev | 5 |
Identification of priority items for the AQ release. | 2 |
configured dues module successfully without AQ help | 2 |
complex flows on my own, without Trevor and Griffin this time ;) | 2 |
Introduction of Effort to the Sprint Planning. | 1 |
the identification of who is working on what on the slide | 1 |
Collaborative effort brought clarity to the requirements. -Anshu | 1 |
Sending the champions what was going to be worked on during the sprint | 1 |
T-shirt sizing estimate ..kudos | 0 |
One page stand up file - very clear to have all sprint focus items on one page. | 0 |
What can be improved? | |
Point | Votes |
Commence Sprint with a finite no. of tickets that is actually achievable in the timeframe. | 2 |
Review sprint timeframe - how many days is actually in the sprint? This could be extended to give the team more time to deliver. | 1 |
just include items in sprint that are going to be worked on. add things to the sprint if work runs out | 1 |
More emphasis on factoring 'Effort' during Sprint Planning | 0 |
Not adding tickets during the Sprint (PS: Test cases were added half-way through Sprint) | 0 |
Action Items | |
Point | Votes |
a plan to communicate back to business owners - show and tell? -> Use 5 mins on the team meetings (MG, ASR, Dev) to communicate changes | 1 |
Plan for deployment into production from UAT | 1 |
Increase Sprint to 3 weeks to allow for time to complete delivery incl. testing and deployment + BAU activities | 0 |
