# data[].attributes.headline
Setting better expectations for UX needed for Planning 

# data[].attributes.subject
Setting better expectations for UX needed for Planning 

# data[].attributes.body
Theres a lot of requests for "final" UX before planning. The design team still needs time to do the work so we want to set a better expectation for what we can provide to aid in planning. High level wires and working/whiteboard sessions are some of the ways we can help scope work. Would love any feedback on how we can collaborate on this better.

# data[].attributes.headline
Give teams time to have define/design analysis - cake analogy.

# data[].attributes.subject
Give teams time to have define/design analysis - cake analogy.

# data[].attributes.headline
Business Strategy for PI3, PI4 and future 2022

# data[].attributes.subject
Business Strategy for PI3, PI4 and future 2022

# data[].attributes.body
good to see all teams working towards same objectives

# data[].attributes.headline
E2E Feature walkthrough during pre-planning 

# data[].attributes.subject
E2E Feature walkthrough during pre-planning 

# data[].attributes.body
This helped in tshirt sizing

# data[].attributes.body
although sync meetings are necessary, it seems like there were too many side meetings not allowing us to spend time with the teams

# data[].attributes.headline
Directors and PMs setting above and below the line features

# data[].attributes.subject
Directors and PMs setting above and below the line features

# data[].attributes.body
Before planning teams are aware which features to focus on

# data[].attributes.body
Allowed POs more time to plan with the team.

# data[].attributes.headline
Business communication on when is PI - more requirements late in planning

# data[].attributes.subject
Business communication on when is PI - more requirements late in planning

# data[].attributes.headline
Limited number of xtrain/xteam syncs to allow focus time for team

# data[].attributes.subject
Limited number of xtrain/xteam syncs to allow focus time for team

# data[].attributes.headline
Surprise Maven transition from start of PI3 handoff to yesterday handoff 

# data[].attributes.subject
Surprise Maven transition from start of PI3 handoff to yesterday handoff 

# data[].attributes.headline
We are getting really good at remote planning

# data[].attributes.subject
We are getting really good at remote planning

# data[].attributes.headline
Lots of other trains dropping agreed upon PI2 items

# data[].attributes.subject
Lots of other trains dropping agreed upon PI2 items

# data[].attributes.body
could have avoided the confusion in PI planning week if we had better plan to onboard new Mavens and more focus in pre-planning

# data[].attributes.headline
Late tech debt identification for app teams

# data[].attributes.subject
Late tech debt identification for app teams

# data[].attributes.headline
Delivery timelines finalized prior to planning

# data[].attributes.subject
Delivery timelines finalized prior to planning

# data[].attributes.body
Planning ran well this week. No major hiccups

# data[].attributes.body
Confusion & late discussions on Cross-train app dependencies

# data[].attributes.body
Very focused teams with clear goals while planning

# data[].attributes.body
Pre-planning made the planning easier and let us  focus on open items and close them during planning week. pre planning was super helpful.

# data[].attributes.body
All of the extra effort during pre-planning helped make sure when we broke down stories and pointed as a team that we were able to fit most/all of the asks.

# data[].attributes.body
hearing that chelsey is leaving us :(