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 24 [Lollipop]

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 24 achievement are listed as -

  • Affinaquest

  • Giving Summaries (Account/ Contact)- Postponed to next year

  • Planning Giving Leads Dashboard in UAT - Meeting with Stakeholders before deploying to Prod

  • Volunteer Recruitment report template for ASR

  • Telephone data clean up - uploaded to Prod

  • Campaign updates (ASR) - (still in UAT)

    • New campaign record types

    • Rationalise fields when creating a new Appeal

    • Rationalise fields when creating a new Event Invitation

    • Campaign data remapped

    • Impacts to iModules (not tested, but don’t anticipate issues)

  • Probability score

  • Prospect queue troubleshooting

  • Service Portal in UAT to replace Jira Service Desk (still in UAT)

    • Login (currently limited to Jarvis users, SSO can be enabled later)

    • How can we help? - Ask a question

    • How to guides?

    • Create a case

      • Reporting and Data Visualisation

      • Data services

      • Systems and Integrations

    • Live Chat

  • New object - Knowledge sets (still in UAT)

    • Troubleshooting

    • FAQ

    • Procedure

  • Donor status is updated to 'Donor' based on donation made to the Campaign

    • Gift/ Pledge - If there is an update to Campaign Appeal, the Campaign Appeal status is updated to ‘Donated’.

  • Log a call (still in UAT)

  • Data Import Wizard - User guide created and users provided access (still in UAT)

    • Bulk upload Account and Contact details

  • Task for the PG team for a Bequest Intention (still in UAT)

    • Batch item record has a ‘New Task’

    • ‘Convert to GIW Opportunity’ from the Task which fields pre-populated from task

  • Automation on ‘Do not Solicit’ flag from Contact to Account.

    • For 1 contact, Account flag is updated to ‘DNS’

    • For 2 or more contact, if 1 contact is ‘DNS’, then an Alert is created on the Account

  • Email to Case automation (Development in progress)

  • AQ release 19.1 - Communication Channels (Development in progress)

  • ASR Strategy (2020 to 2025) Dashboard (still in UAT, waiting approval from Alain)

  • Additional reports created for VP - Advancement

  • Census 2021 data analysis based on 2012 census

  • CG Donor Retention report - Can be handed over to CG

  • Updates to the Swift Digital integration - Biographical updates. Following fields are now integrated to Jarvis -

    • SAM preferences

    • Industry

    • Occupation

    • Start date

  • Receipt record - Clean-up of Jarvis pages with button

  • COA - Active flag designation - Update to flow

  • Gift/ Pledge of updating COA on the Designation

  • Opportunity - Lead source and Amount are added automatically when field is blank

  • Duplicate Accounts - Clean up of 400 accounts, 200 Accounts outstanding

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

So many new feature leading to novel business improvements. Good to move away from the usual Data conversion tickets.

4

Some incredible automationsssss - Kudos Swathi, Yeng, Liz, Monica

2

backlog refinement meetings were much better

1

Collaboration with the CG and ASR Team.

1

Using labels to understand which tickets are part of a bigger piece of work which needs to be looked at in one go

1

Backlog refinement and sprint planning was very realistic and we got to achievable levels of tickets

0

a number of developments were well thought through, aligned with stakeholders and automated processes

0

Reasonable planning and forecasting of tickets that can be worked on till the end of the year

0

Cross functional collaboration for ticket development between DRS, CGT and GA - win win win

0

Quickly assessed the unexpected blockers and aligned the sprint to have more achievable tasks

0

What can be improved?

Point

Votes

Use the descriptions rather than ticket numbers in stand ups

3

Speed up the User testing for developer to be productive

0

Working out how we structure tickets that we know will go over multiple sprints. How can we flag that this is a bigger body of work more easily

0

Keep business informed if system functionality is going to be deactivated

0

Action Items

Point

Votes

Any new custom fields added - System administrator should be given Permission in order to complete the back-up.

0

 

  • No labels