# data[].attributes.headline
Feel free to add actions/items/concerns of things we should change!

# data[].attributes.subject
Feel free to add actions/items/concerns of things we should change!

# data[].attributes.headline
Coming to PI with Dependencies Discussed with Respective Teams. At least high level so teams are prepared while starting the PI. 

# data[].attributes.subject
Coming to PI with Dependencies Discussed with Respective Teams. At least high level so teams are prepared while starting the PI. 

# data[].attributes.headline
Anne, keep up the great work in  our PI sessions :-)

# data[].attributes.subject
Anne, keep up the great work in  our PI sessions :-)

# data[].attributes.headline
Share major accomplishments over past Qtr before we share PI board for upcoming Qtr

# data[].attributes.subject
Share major accomplishments over past Qtr before we share PI board for upcoming Qtr

# data[].attributes.headline
Having dependencies on other teams without clear understanding of the feature being delivered

# data[].attributes.subject
Having dependencies on other teams without clear understanding of the feature being delivered

# data[].attributes.headline
Coffee warmer or microwave to heat up coffee 

# data[].attributes.subject
Coffee warmer or microwave to heat up coffee 

# data[].attributes.headline
Addressing telecommunication issues  day before PI

# data[].attributes.subject
Addressing telecommunication issues  day before PI

# data[].attributes.headline
Mid PI meeting across teams to share backlog and key features for upcoming PI

# data[].attributes.subject
Mid PI meeting across teams to share backlog and key features for upcoming PI

# data[].attributes.body
Better clarity on key repositories and it’s business cases and KPIs associated.

# data[].attributes.body
More camaraderie between teams / sense of “we” so that the sum of all becames more powerful/effective

# data[].attributes.body
at least first hour on day 2 and 3 for teams to discuss changes with the IDC (like we had time on day 2). its frustrating to have to modify the boards to their final state without their input.

# data[].attributes.body
letting all the idc presenters go first. it complicates the ordering, but it makes sure they get to represent themselves clearly

# data[].attributes.headline
Waiting until PI planning to expose outbound dependencies

# data[].attributes.subject
Waiting until PI planning to expose outbound dependencies

# data[].attributes.body
Always the highlight of my quarter :)

# data[].attributes.headline
Anne should continue being a miracle worker #blessed

# data[].attributes.subject
Anne should continue being a miracle worker #blessed

# data[].attributes.body
At times due to constraints IT is unable to pick a business requirements which could be P1. Can we have a small session with business during these three days of PI and then convince them now itself and if needed even get Ivan involved. I understand this may lead us into another mess but still can we do this.

# data[].attributes.headline
Put User Stories with *hard dates* at the top of the section/ boards

# data[].attributes.subject
Put User Stories with *hard dates* at the top of the section/ boards

# data[].attributes.body
In the Features - Committed section, teams should place the user stories with hard dates at the top of the section

# data[].attributes.body
We are EDA org. We all (all job grades, not just development teams) need to have basic foundational knowledge on how analytical systems are designed and implemented.

# data[].attributes.body
Make a directive to have boards using same rules and formats.  Many boards used excel and others used ppt.

# data[].attributes.body
Let us all try to be on-time.

# data[].attributes.headline
Presenters going into too much detail about every feature especially on features with no dependencies. Slows down the process.

# data[].attributes.subject
Presenters going into too much detail about every feature especially on features with no dependencies. Slows down the process.

# data[].attributes.headline
Entire teams left room.  Everyone must stay in the room unless they have a P1 issue.

# data[].attributes.subject
Entire teams left room.  Everyone must stay in the room unless they have a P1 issue.

# data[].attributes.body
Need to start the planning for next PI starts immediately after the current PI is complete. This improves our planning process.

# data[].attributes.body
Makesure teams have pre-pi planning

# data[].attributes.body
All teams should be aligned

# data[].attributes.body
Associate all features to the committed repositories list.

# data[].attributes.headline
Bringing up risks only during PI Planning

# data[].attributes.subject
Bringing up risks only during PI Planning