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

Skip to end of banner
Go to start of banner

Sprint 13 [Apple Pie]

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Background

Sprint 13 achievement are listed as -

  • Update permissions for the 'Active' flag on addresses and Phone numbers.

  • Enhancement to Campaign code creation.

  • Data conversion (report on progress)

    • 7 of 15 tables completed (Pledges, Entity, etc.)

    • Addresses and emails data conversion testing completed

  • Data conversion

    • 15 tables completed (Opportunities, Relationship management team, Wealth assets, etc.)

    • Outstanding (Tasks, Opportunity stages)

    • Created fields for Pledge reminder

  • Loaded Activity tasks related to Planned Giving/ Bequest (2018 to 2021)

  • Primary degree data fix

  • SITS migration to Tribal cloud (Test B environment) - Test integration with Jarvis

  • Data conversion (Volunteer, Position, Category, Campaign, Campaign members, Education and Area of study)

  • Enhancements to Donor receipts (Salutation)

  • Enhancements to iModules integration (Batch items)

  • User goals and KPIs loaded for 2021

  • Most reports converted from Advance to Jarvis

Sprint 13 was limited to 9 business days due to Advancement Services Team day (03/03). Additionally, there were no ICT integrations resources as they were re-directed to Curriculum Timetable (CT) and Workday projects.

Despite the time above constraints, the team closed out 93 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

Consistent dedication to working through data conversion tickets/bugs

4

Introduction of Sprint names

1

Summary of testing objects with their pass/fail status.

0

What can be improved?

Point

Votes

focus on customer's experience and expectations in Jarvis

2

consider grooming user stories as part of spring planning

2

Tech team to work on 2 -3 tickets at one time

1

Close out tasks that are 'In Test' or 'In Progress'

1

Action Items

Point

Votes

Develop a cadence on deployment for Integration and Configuration. Bug fixes can be deployed on Demand.

1

Apex coding may be a blocker. Look at alternatives to help TAP business users manage different tasks

1

Addresses/ emails with foreign characters need to be fixed - To be done by SAM in May

0

determine up front what will or won't be achieved at sprint planning knowing that tech team will work on 2-3 tickets during the sprint

0

Update Jira Service Desk portal with references to Jarvis (instead of Advance)

0

Update Acceptance Criteria to When/ Why/ Who to provide better context

0

 

  • No labels