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 5 - 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 Current »

Background

The Sprint objectives covered the following -

  • Reporting

  • Opportunities

  • Gift Administration

  • Community Giving

  • Change Management

Statistics at the end of Sprint

Sprint 5 included Data Conversion bugs that took precedence and priority over Sprint 5 User Stories. These numbers were not reflected in the Sprint 5 - Overall status. It has been added below to reflect the deliverables for Sprint 5.

Cumulative Flow Diagram

CFD for Sprint 5 - 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

Great push on data conversion defect testing

5

Report types are getting more sophisticated and enable us to deliver more tailored data / insights

1

Recognition from the Steering Committee, expressing gratitude & admiration for project team's  high performance within tight timeframe & bgt

1

Griffin being so responsive with data conversion tickets to ensure a quick turnaround

0

developers show a lot of flexibility in developing user stories. do whatever it takes to complete

0

Team working very well with good collaboration.

0

Decisions are getting made regarding business needs.

0

What can be improved?

Point

Votes

Bit of Sprint fatigue and nervousness as we near Go-Live. Look at ways to boost morale and confidence.

3

Data conversion tickets took precedence over sprint tickets - increased clarity over Sprint planning and load of conversion tickets vs config

2

Better mapping / notification of configuration decisions that may impact other streams

0

Action items

Action Items

Point

Votes

Let's to talk about the big picture [end to end] to ensure continuous improvement

1

Can we have a session on Data conversion review what could be accept and what is not?

0

  • No labels