# data[].attributes.body
An item in the release list had impact on another page that wasn't checked by dev or test until the release

# data[].attributes.body
We had really old branches that weren't considered high priority for release so have been hanging round for an age checking of that work had fallen through the cracks

# data[].attributes.body
Chat Teams vs Slack
Call Teams vs Slack

If Teams, collate teams\chat channels

# data[].attributes.body
These are time consuming but they showed errors, missing steps for the release and in general they make the release faster. Very useful especially if new APIs are involved

# data[].attributes.body
These distracted a lot of people from the actual release features.
If needed they need to be factored in sooner

# data[].attributes.body
Helps to flag issues early but also enables discussion / collaboration around parts of the Design that might be really difficult to implement. - DO

# data[].attributes.body
I liked having the quick go/no-go meetings leading up to the end of the release, as you get an idea of the state of each area and it helps to keep everyone visible to bugs/health of things - If the time is available for them! - DMC

# data[].attributes.body
Ensure everyone has looked at the spec so we know exactly what's going into the release to avoid things being added last minute past a deadline that may add additional work during busy periods - DMC

# data[].attributes.headline
List of items included for the release with links to stories/epics 

# data[].attributes.subject
List of items included for the release with links to stories/epics 

# data[].attributes.body
Having a simple list, with links to stories & epics etc, of what will be included in the release would be very beneficial, as it would be easier to know what was going to be included in the release and to make sure we’re testing every item – DMC

# data[].attributes.body
Ensure all Figma files are correctly arranged and labelled, to make it easier to find current designs
DW

# data[].attributes.headline
Agree a standard process for importing MIS data

# data[].attributes.subject
Agree a standard process for importing MIS data

# data[].attributes.body
Set up as a new epic in Jira - Paul suggestion. Can set up as stories for getting the data in? Is possible to automate this process. Currently Paul owning this process, but would make sense for Data team to own in the longer term, as is done through PAT. Possibly Ryan to own this?

# data[].attributes.body
Get together with key stakeholders to agree next steps / direction with MIS, once the September release is out of the way. (KA)

# data[].attributes.body
Need test cases to test the access to MIS works in all possible scenarios?