# data[].attributes.body
Ensure that testing stories will be available before planning meetings

# data[].attributes.body
Taking OKR into account in our priorities

# data[].attributes.body
Our long hard journey to CD in ZPP

# data[].attributes.body
Continuously talk to consumers to understand their requirements

# data[].attributes.body
Working on our own & not double checking with consumers on their requirements

# data[].attributes.body
Define when retro link should be sent, so everyone has enough time to put their topics on the board

# data[].attributes.body
PO to ensure whole team is involved if initiative is big/ affect direction of product architecture

# data[].attributes.body
Doing "POCs" for things we want to understand - not just theoretical analysis

# data[].attributes.body
Including OKR topics in the planning/sprints.

# data[].attributes.body
Team to tell PO if any clarification is needed if it affects direction or decision of implementation

# data[].attributes.body
More end to end view of what needs to be done

# data[].attributes.body
Team not working in silo and is interested in topics we have in the team

# data[].attributes.body
Question to team: When is a good time for them to come in for discussion and implementation with other teams so that team don't have pressure to finish things fast/ in-time for other teams (as they have dependencies on us too)

# data[].attributes.body
Keep on having stand up at 10:10

# data[].attributes.body
Leaving thing lying around in review step

# data[].attributes.body
Do not forget to "vote" for stories, especially when one of us is missing/on vacations/etc. Or find another way of Stories reviews, as it is not super convenient to remind all the time ;)

# data[].attributes.body
Writing analysis results understandable only in the context of current time and current team