Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Background

Sprint 26 was a short 2 week sprint to accommodate for the End of year shutdown.

Sprint 26 achievement are listed as -

  • Log4j vulnerability [TAP applications] -

    • Reached out to vendor to confirm if risk is managed

    • Applied remediation to vulnerable systems

  • TAP Roadmap 2022 complete

  • Creation of 2 Donor Relations Dashboard

    • Main dashboard to show performance of the team

    • Specify dashboard for leadership to track DR progress

  • Accolade - Created ‘Notable Alumni’ against Contact [UAT]

    • Data not loaded in UAT as discussions underway as to the definition of ‘Notable Alumni’

  • New cases type ‘Duplicate Account/ Contact’ assigned to Gift Admin team [UAT]

  • Telephone number validation rule - GI team to be bypass validation [UAT]

    • To be reviewed before loading to Prod

  • Affiliations - Needs clean-up before migrating to Jarvis. Possibly no need to migrate

  • Campaign restructure reviewed

  • Swift Digital integration - Clicks, opens, unsubscribes - POC testing in progress

  • Updated on the Conditional pledges ‘Campaign counting’. Only count payments.

  • NAB TransAct file - updates to the Contact ID [UAT]

  • Analysis on Duplicate Accounts for review

  • Alternate ID - Standard user shouldn't have access to update this field [UAT]

  • Knowledge Transfer from ICT integration team complete

  • SITS integration enhancements [UAT] -

    • Award Short Description to Education - New ticket to load historical data

    • Enhancements to Invalid address - Exceeded 256 characters creates errors.

  • Security checks and enhancements

  • Web to Case [UAT]

    • Match based on name and email address

Statistics at the end of Sprint

Image RemovedImage Added

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

Changes in resources (CSM and ICT integrations) and handover in progress. Relatively short sprint and yet lots of tickets completed.

0

What can be improved?

Point

Votes

Can we start focusing on the percentage of uncompleted tickets from each sprint and see how that trends up and down? This will help us anticipate how many tickets might hang around

0

How can we change our sprint planning so that we can actually complete every ticket in a sprint? Do we need to start to decomposing out tickets more effectively?

0

For the data gap, Could we have the review by the business units first? as I found a few of the work I done got cancelled after review.

0

Action Items

Point

Votes

Give me my burndown chart Brad!

0

Breakdown tickets to smaller workable pieces per sprint. Create sub-tasks on a parent ticket

0