# data[].attributes.headline
Still very messy and ad-hoc on both ends

# data[].attributes.subject
Still very messy and ad-hoc on both ends

# data[].attributes.headline
still pending a proposal / decision on the strategic UI framework

# data[].attributes.subject
still pending a proposal / decision on the strategic UI framework

# data[].attributes.headline
Need to get more frequent Product Owner Meetings and Workshops to improve cadence

# data[].attributes.subject
Need to get more frequent Product Owner Meetings and Workshops to improve cadence

# data[].attributes.headline
Access to other floors. If you look at how many hours/days have been lost and multiply it by an average daily rate, it's a large chunk of change.

# data[].attributes.subject
Access to other floors. If you look at how many hours/days have been lost and multiply it by an average daily rate, it's a large chunk of change.

# data[].attributes.headline
We should try and use test data which is as close to insights as possible

# data[].attributes.subject
We should try and use test data which is as close to insights as possible

# data[].attributes.headline
Need to sort out the whole JIRA thing and the process to drive it forward

# data[].attributes.subject
Need to sort out the whole JIRA thing and the process to drive it forward

# data[].attributes.headline
Look at merits of focusing on finishing one piece well before moving focus to other components

# data[].attributes.subject
Look at merits of focusing on finishing one piece well before moving focus to other components

# data[].attributes.headline
Need to focus more on finishing the insight features rather than trying to introduce new stuff

# data[].attributes.subject
Need to focus more on finishing the insight features rather than trying to introduce new stuff

# data[].attributes.headline
The product backlog needs to grow, so tech's have the appropriate amount of time to estimate and create tasks

# data[].attributes.subject
The product backlog needs to grow, so tech's have the appropriate amount of time to estimate and create tasks

# data[].attributes.headline
too many things going on both within and beyond 1K

# data[].attributes.subject
too many things going on both within and beyond 1K

# data[].attributes.headline
Requirements are still a little all over the place

# data[].attributes.subject
Requirements are still a little all over the place

# data[].attributes.headline
need to decide on a process and start moving forward

# data[].attributes.subject
need to decide on a process and start moving forward

# data[].attributes.headline
GIC PO's need to align a bit better. Heathers view often differs to PO's.

# data[].attributes.subject
GIC PO's need to align a bit better. Heathers view often differs to PO's.

# data[].attributes.headline
More regularly recurring meetings with PO's when component is under active design/development would be good

# data[].attributes.subject
More regularly recurring meetings with PO's when component is under active design/development would be good

# data[].attributes.headline
It does seem we need to stop changing process at some point

# data[].attributes.subject
It does seem we need to stop changing process at some point

# data[].attributes.headline
Should we do UX, or just a little color & usability? (Do we need workshops on what UX actually is and why it's important?)

# data[].attributes.subject
Should we do UX, or just a little color & usability? (Do we need workshops on what UX actually is and why it's important?)

# data[].attributes.headline
Retro comments need to be more specific and we need to discuss them in further detail

# data[].attributes.subject
Retro comments need to be more specific and we need to discuss them in further detail

# data[].attributes.body
Then

# data[].attributes.body
Need to be clear on the deliverables of the ui and ux for each sprint .

# data[].attributes.headline
Is the prep time and effort for sprint demo planned in?? How to make it more streamline to be more efficient . Also the overall status of spill over and what are completed should be part of sprint demo updates 

# data[].attributes.subject
Is the prep time and effort for sprint demo planned in?? How to make it more streamline to be more efficient . Also the overall status of spill over and what are completed should be part of sprint demo updates 