# data[].attributes.body
Well done to Jamie, Nicki, Claire and Andrew on getting bookings to mvp standard.

# data[].attributes.body
Issue with reporting, the VPN was down for 4 days.  Looks like an issue with Windows Update being installed on our broker server.
Resolved on day 4.

# data[].attributes.body
Mailhog is used on Dev/Test/Pre-prod environment to capture emails.  It has a limited amount of space and once it reaches capacity it clears everything out.
For major upgrades: prior to beginning UAT, we should clear out mailhog so there's less chance of our tests being deleted.

# data[].attributes.body
Think we split the work really well between the team to get through the items really quickly

# data[].attributes.headline
Open the Retro board at the start of a new sprint

# data[].attributes.subject
Open the Retro board at the start of a new sprint

# data[].attributes.body
Open a retro board from the start of a sprint, rather than closer to the end.  This means we can add cards as things happen, sometimes it can be difficult to remember (especially if it was at the start of a sprint)

# data[].attributes.body
Focus on 1.7 upgrade and bookings mvp

# data[].attributes.body
Round it really useful to capture the JIRA tickets raised as a result of testing issues found in release 1.7 testing

# data[].attributes.body
Well done to Andrew on configuring the Book and Pay product on our Test environment. This gives us a platform to test future upgrades and services.

# data[].attributes.headline
Weekly meeting to discuss new Jira tickets

# data[].attributes.subject
Weekly meeting to discuss new Jira tickets

# data[].attributes.body
The team can be split across different daily stand-ups.  New Jira tickets are sometimes missed by other members who can provide updates/rationale.

# data[].attributes.headline
Agreeing what' mvp and creating separate planner items

# data[].attributes.subject
Agreeing what' mvp and creating separate planner items

# data[].attributes.body
It's taken over 6 weeks since Goss forked the 1.7 upgrade but we've finally managed to UAT and sign-off the test server.

Big well done to everyone involved, especially for their patience!

# data[].attributes.body
Jamie demo'd registrations bookings from both staff/customer pov.
MVP is almost complete

# data[].attributes.body
Since go-live in the last sprint, we've now got over 2047 customer sign-ups!

# data[].attributes.body
This failed for a couple of hours again yesterday.  Other than that, it's been working fine during the last sprint.
The good news is that Goss might have located the issue.

# data[].attributes.body
We've tweaked the developer sessions to include a mini stand-up. We're going though planner cards and posting updates.

# data[].attributes.body
Behind the scenes certificate was due for renewal. Goss and Improvement Services liaised to ensure a seamless transition.

# data[].attributes.headline
Planner item requirements scope increase

# data[].attributes.subject
Planner item requirements scope increase

# data[].attributes.body
Tickets scored at initial stage.  Checklist items are then being added which are causing scope creep.
MVP needs to be identified and any additional requirements captured as separate backlog items.
Checklist items added should be relevant to the overall card title

# data[].attributes.body
Find planner difficult when trying to retrieve completed requests e.g. locating a decision in a card.

# data[].attributes.body
Use planner labels to tag tasks with a priority e.g. MVP items.  This will make it easier for developers to identify the next set of priorities in the backlog.

# data[].attributes.body
Well done to Priya and Andrew for getting the changes to Taxi live, despite all the network issues.

# data[].attributes.body
Goss QA'd and signed-off the 1.7 bookings fork on TST (ERCCEX-1165).
Unfortunately, it still contained bugs, one of which we'd already flagged on JIRA!

Goss did fix the build for us the very next day but it highlights ongoing flaws with their release and QA procedures, as raised at the weekly call.

# data[].attributes.body
Initial reports are that the ERC network issue is resolved for CSOs who are noticing a speed improvement with Goss.

# data[].attributes.body
Some of the team were unable to access the various Goss sites on Direct Access, even after the wider network issues were resolved.
This impacted the teams ability to carry out sprint tasks when WFH.

# data[].attributes.body
SW & CP
It's too difficult to locat key decisions, especially if they're locked away in archived planner cards.
We need a single decisions log to track any major product decisions.

# data[].attributes.body
Fast turnaround from Goss, the build was deployed to PRP within a couple of days of ERC signing off TST.

Team UAT'd Registrars Slot Bookings and didn't find any issues!

# data[].attributes.body
It was good to get back into the office, even for just one day, to meet people in person again!

# data[].attributes.body
To get more engagement from the team in the retrospective. I'd like to change this to the beginning of the planning session on a Wednesday morning when we plan to be in the project collaboration room in HQ

# data[].attributes.body
Goss: ERCCEX-1143 / ERCCEX-1041.
Improvement Service: SR1151112 / SR1153820

Goss fixed the issue by restarting their API server.  However, I'm still trying to get to the bottom of why logging in to Goss, via mygov.scot, is periodically failing for customers.

Goss found an error in their logs "Unable to unmarshall metadata".  The Improvement Service are unable to replicate this error.

Call scheduled for Friday.

# data[].attributes.body
Priya and Julie worked well together in order to work around the network access issues to ensure updates were made to our live site

# data[].attributes.body
I want to make sure that the folder structure in Sharepoint and Teams works for us. I'd like to make a channel dedicated to sprint planning and reviews to easily document what is expected and agreed at each ceremony. Would this work and are there other channels that need changed, archived, created?

# data[].attributes.headline
CSO happy with fast turn arounds of improvements

# data[].attributes.subject
CSO happy with fast turn arounds of improvements

# data[].attributes.body
CSO expressing happiness at small improvements that will make a difference to their day to day and promote further engagement from them