# data[].attributes.headline
Better user stories and defined acceptance criteria

# data[].attributes.subject
Better user stories and defined acceptance criteria

# data[].attributes.body
DoD and DoR

# data[].attributes.headline
pre-sprint planning sync between Sandra, Nick, Lucas, Jeremy?

# data[].attributes.subject
pre-sprint planning sync between Sandra, Nick, Lucas, Jeremy?

# data[].attributes.body
Goal is : No Production UAT)
Do:
Dev -> Test -> UAT -> Prod
Not:
Dev -> Test -> Prod -> UAT

# data[].attributes.headline
Having design work signed off ahead of the sprint.. Allow enough time for design review/UAT etc

# data[].attributes.subject
Having design work signed off ahead of the sprint.. Allow enough time for design review/UAT etc

# data[].attributes.headline
Under 10% of #tech_feedback is being escalated to tech in real-time

# data[].attributes.subject
Under 10% of #tech_feedback is being escalated to tech in real-time

# data[].attributes.headline
Do not push directly to master (even if I am code owner)

# data[].attributes.subject
Do not push directly to master (even if I am code owner)

# data[].attributes.headline
1. Sandra stepping in as product manager

# data[].attributes.subject
1. Sandra stepping in as product manager

# data[].attributes.body
Taking the reigns and running with her first full tech project

actions: Keep doing it!

# data[].attributes.headline
2. Road Map / Planning / Tracking Requirement Changes

# data[].attributes.subject
2. Road Map / Planning / Tracking Requirement Changes

# data[].attributes.body
It might be similar to what we want to improve, but it seems there is no road map, so things are a bit messy.

action:
- SDLC Documents
- Project Documents
- Design Documents

We don't really have a proper plan for this type of projects where requirement change really fast

# data[].attributes.body
What is this role?

Who are they?
What are the differences with a Product Manager?
What are their responsibilities?
actions:

- TBA after project planning actions above action #2.

# data[].attributes.body
Proudly taking ownership of what you built. You build it, you test it, you deploy it, you support it, you maintain it.

actions:

- Individual testing (Unit/Automation/Manual)
- Q/A specific person?
- Staging environment

# data[].attributes.body
Silvia yesterday after using AEX-HQ and EEE yesterday... "how good is this!"

Me today "how cool is this"

# data[].attributes.body
Demos are more concise and there is better sizing prep happening prior to the meeting

I like that we're taking detail off-line and sizing separately so if something isn't relevant to everyone it's not wasting peoples time

# data[].attributes.headline
I find that doing a run-through on new cards prior to starting is working well to ensure that nothing gets missed and you minimise areas of assumption 

# data[].attributes.subject
I find that doing a run-through on new cards prior to starting is working well to ensure that nothing gets missed and you minimise areas of assumption 

# data[].attributes.body
Media component done and dusted.
The initial design for EEE (Jason's proposed) new templates done

# data[].attributes.body
Instead of Slack. From mkt to tech. And Tech to mkt.

# data[].attributes.headline
Auth project review and sign off process

# data[].attributes.subject
Auth project review and sign off process

# data[].attributes.headline
Cleaning up location data. Creating location standardisation

# data[].attributes.subject
Cleaning up location data. Creating location standardisation

# data[].attributes.headline
Product team has doubled and we've recut the processes to suit

# data[].attributes.subject
Product team has doubled and we've recut the processes to suit

# data[].attributes.headline
Stop types got defined on routes and now support a heap of different experience types (including self-guided = new)

# data[].attributes.subject
Stop types got defined on routes and now support a heap of different experience types (including self-guided = new)

# data[].attributes.headline
PSP can do invoicing process... I thought this would be months off but solution'ing got it down to something that can add MASSIVE value quickly

# data[].attributes.subject
PSP can do invoicing process... I thought this would be months off but solution'ing got it down to something that can add MASSIVE value quickly

# data[].attributes.headline
Communicate more on what is ready to integrate among components

# data[].attributes.subject
Communicate more on what is ready to integrate among components

# data[].attributes.body
Leave the mindset behind that we can read minds.

Do not micro mange things

Be more flexible, open

Teach but learn too

Solve the PR

# data[].attributes.headline
Further condense demoing at the start of sprint planning

# data[].attributes.subject
Further condense demoing at the start of sprint planning

# data[].attributes.body
When demoing, could things that are in production be demoed by the product manager? To further emphasise the win that it's had on actual operations?

# data[].attributes.body
Our team needs to build better processes,  (now that we have more than one person NB + LA)
*What do we expect from each of us
*When do we meet
*What do we prepare for sprint planning

# data[].attributes.body
To ensure all cards are still relevant in Jira and there are no double-ups/things that are no longer relevant

# data[].attributes.headline
Changing the Jira notifications so we don't miss important comments etc

# data[].attributes.subject
Changing the Jira notifications so we don't miss important comments etc

# data[].attributes.headline
Add 5 min to the end of sprint planning to make sure that the cards are in the right order

# data[].attributes.subject
Add 5 min to the end of sprint planning to make sure that the cards are in the right order

# data[].attributes.headline
Adjusting roadmap timeframes AFTER the epic planning/sizing has been done to ensure it's still relevant

# data[].attributes.subject
Adjusting roadmap timeframes AFTER the epic planning/sizing has been done to ensure it's still relevant

# data[].attributes.headline
Coordinating deployments across the team

# data[].attributes.subject
Coordinating deployments across the team

# data[].attributes.headline
Have Ray be part of the sizing work at the start of an epic to ensure all back end touch-points are covered (PSP example)

# data[].attributes.subject
Have Ray be part of the sizing work at the start of an epic to ensure all back end touch-points are covered (PSP example)

# data[].attributes.headline
Should design requests be in Jira instead? So there is transparency around all of Jason's projects across different projects

# data[].attributes.subject
Should design requests be in Jira instead? So there is transparency around all of Jason's projects across different projects

# data[].attributes.headline
More definition in the CRO part of the roadmap

# data[].attributes.subject
More definition in the CRO part of the roadmap

# data[].attributes.headline
Checklist visibility for tech testing.. how do product owners know what is covered. Understand who is responsible for what tests before a deployment

# data[].attributes.subject
Checklist visibility for tech testing.. how do product owners know what is covered. Understand who is responsible for what tests before a deployment

# data[].attributes.headline
Starting sprints with stories that have incomplete info

# data[].attributes.subject
Starting sprints with stories that have incomplete info

# data[].attributes.headline
Having Jira cards in the sprint that we know will not be fully possible. Should be split

# data[].attributes.subject
Having Jira cards in the sprint that we know will not be fully possible. Should be split

# data[].attributes.body
A few cards have been sent to done, but the job wasn’t 100% finished (plus in some cases we even closed the sprint before the job was done)

# data[].attributes.headline
Comms model on reporting actions came too late

# data[].attributes.subject
Comms model on reporting actions came too late