Background
The Sprint objectives covered the following -
Reporting
Opportunities
Gift Administration
Community Giving
Change Management
Statistics at the end of Sprint
Cumulative Flow Diagram
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 |
Continued support from Trevor and Griffiin with configuring user stories. | 4 |
Skill and knowledge of team increasing and able to tackle more complex requirements | 2 |
More complex User Stories and tasks are completed in this Sprint which takes a little longer time. | 1 |
We've got a new CRM name | 1 |
Issues/ Blockers are surfaced as soon as they occur and the teams jump in to help | 0 |
Good collaboration between teams | 0 |
Tremendous support from Trevor and great tool knowledge. An absolute rescue!. | 0 |
What can be improved? | |
Point | Votes |
Complete data conversion testing so that the team can focus on the Sprint goal | 3 |
High level measure of the completion status of Data Conversion Testing | 1 |
Minimise outside distractions in order to complete Sprint goals | 1 |
Perceived performance not as high as previous sprint | 1 |
Consider the amount of tickets and the tech people - there perhaps we're a lot tricky tickets which meant this sprint was a little slower. | 0 |
Action items
Action Items | |
Point | Votes |
Change the name of the CRM - JARVIS ? | 0 |
Expedite Data conversion testing. Have a separate retrospective for Data conversion testing. | 0 |
Plan/ re-prioritise User stories for Sprint 4 | 0 |
Share Production deployment notes in SharePoint. - Yeng | 0 |
