# data[].attributes.headline
UX team will have internal discussion on runway work. We will circle back on next steps in iteration 1

# data[].attributes.subject
UX team will have internal discussion on runway work. We will circle back on next steps in iteration 1

# data[].attributes.headline
Coordinate with A11y team on how to incorporate A11y design considerations in to Development cycle.

# data[].attributes.subject
Coordinate with A11y team on how to incorporate A11y design considerations in to Development cycle.

# data[].attributes.headline
Need to have Rally training provided to XDO team members

# data[].attributes.subject
Need to have Rally training provided to XDO team members

# data[].attributes.headline
Nitin to find out more about setting expectations in PI planning

# data[].attributes.subject
Nitin to find out more about setting expectations in PI planning

# data[].attributes.headline
Large Initiatives: Need to talk about Cross Train leadership

# data[].attributes.subject
Large Initiatives: Need to talk about Cross Train leadership

# data[].attributes.body
Need to better understand how UX is thinking about runway plans to inform stakeholder management

# data[].attributes.body
This PI, we experienced a lot of pressure to take on work – which resulted in much of our pre-PI planning being spent defining and sizing features we weren't able to commit to.

# data[].attributes.headline
Opportunity to improve A11Y process for web

# data[].attributes.subject
Opportunity to improve A11Y process for web

# data[].attributes.body
Collaborate on process, prioritization, and ticket definition

# data[].attributes.body
I continue to see us successfully deliver our plans remotely. We have the ability to dig into the details where needed and easily pull in eng, ux, stakeholders at a moments notice. I am curious how successfully we would be getting back into in-person planning

# data[].attributes.body
Individuals that work across multiple teams were very responsive and accommodating in making themselves available for questions and jumping in when needed.

# data[].attributes.headline
Room to Improve Feature Ticket Comms to Shared Services Team

# data[].attributes.subject
Room to Improve Feature Ticket Comms to Shared Services Team

# data[].attributes.body
Opportunity to better support shared services – a11y and copy – so they have all the rally feature ticket numbers available via email per team. Would really help streamline the process and keep us buttoned up right at the beginning of PI kickoff!

# data[].attributes.body
Opportunity to improve web PI planning prep activities. I fell that we groomed more items than we had capacity for and under-groomed some high priority features.

# data[].attributes.body
As we have multiple new resources in team, it would be better to set the expectation of what need to be focused during PI planning. May help.

# data[].attributes.body
Even though they were prior to PI Planning week they were an integral part to PI Planning. I'm not one to love more meetings – but think we should consider keeping this going and starting earlier in the process. Maybe in the beginning stages though we consider it as a living Miro board (or Rally dashboard) with assigned Action Items rather than scheduled meetings.

# data[].attributes.body
We need more guidance from ATO to support and setup Program Boards for large xtrain initiatives. Additionally, challenging to carve out an hour a day during PI planning

# data[].attributes.body
We have come so far on calling out security items. Big shout out to our Security Mavens for keeping on top of this!