• Attendees / Apologies
• Upcoming Availability

Phase 3 Overview

• Backlog
• Notes

Renewal / Cancellation Workflow

• Business goal of the deliverable functionality is to inform the decision to renew or cancel
• What is the information needed to make the decision? (typically cost and usage, rather than content)
• What is the point in the agreement lifecycle at which the decision is to be made?
• How is the user notified at the appropriate time?
• What decision record is kept?
• Some aspects of comparison may be part of renewal workflow
• Also, what are the consequences of cancellation?

Package comparison

• same package over time (snapshot comparison?)
• across different packages
• across different packages across agreements

Track/manage changes

• what has moved in or out of this package?

• Delivery of sprint backlog is on track
• Critical path for testing ahead of Q2 release deadline is ERM-245 (tenant bootstrap improvements), but this is not a concern at the moment.
• Owen has capacity for QA on Friday

• ERM-265 (JSON export) to take priority
• ERM-215 (KBART export) to be removed from sprint
• ERM-185/ERM-185 (file uploads) to take priority over date/time bugs (ERM-189/ERM-262)

• Sheffield Developer Gathering
  • 15-19 Jul 
  • schedule link 
• Next dev call is combined Sprint 64 & 65 Retrospective: 
  • add details link