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 6 - Configurations Retrospective

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

The Sprint objectives covered the following -

  • Reporting

  • Opportunities

  • Gift Administration

  • Community Giving

  • Change Management

Statistics at the end of Sprint

Sprint 6 included Data Conversion bugs and UAT support that took precedence and priority over Sprint 6 User Stories. These numbers were not reflected in the Sprint 6 - Overall status. It has been added below for reference (Note: These are the overall stats at the end of the Sprint).

Cumulative Flow Diagram

CFD for Sprint 6 - User Stories

CFD for Data Conversion testing - Bugs

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

On-site team day with UAT Testers and Champions was a good day for collaboration. Lots of productive discussions with quick resolution time.

3

UAT refresh went well thanks to all collaboration works from the team and with our senior tech AQ

1

Team continues to work with high intensity to complete MVP user stories in time for go-live

1

Good team collaboration and communication with AQ, ICT, Advancement services team

1

UAT testers gained speed and asking great questions

0

Core delivery team doing well to juggle between data conversion testing, Sprint 6 tickets and UAT test support

0

The channel for testers to post questions/issues was a good idea and great collaboration from the team with everyone jumping to help answer and resolve issues

0

What can be improved?

Point

Votes

Data conversion testing and bug fixes consuming significant time, affecting configuration output

2

We still have BAU data extract come through that will taken up our times

0

Mention any object config changes in the standups so if we see any unusual errors we can try and identify the potential cause quickly

0

For the next refresh go better we need to make sure all change objects are registered in deployment registered

0

Action Items

Point

Votes

@Jules - Organise a meeting to draft a plan for Production Data conversion testing. (e.g. Integrity scripts, testing scripts)

0

Keep deployment registry updated

0

Config changes should be mentioned in daily stand-up meetings

0

  • No labels