# data[].attributes.body
Working across scrum teams within TNT; being brought into (eg) CLM/ SRM at early stage

# data[].attributes.body
Strong and active efforts of team leadership to build the team, bring team together.

# data[].attributes.body
Was difficult to find value in PI Planning if you were not there

# data[].attributes.headline
getting the opportunity to attend the PI Event in person last week. It's much easier to follow along and have a sense for what is going on when you are in the room.

# data[].attributes.subject
getting the opportunity to attend the PI Event in person last week. It's much easier to follow along and have a sense for what is going on when you are in the room.

# data[].attributes.body
the better division of responsibilities

# data[].attributes.body
As a team we improved the cross ART coordination on the iteration Demos

# data[].attributes.headline
The increased cross collaboration across ARTS.

# data[].attributes.subject
The increased cross collaboration across ARTS.

# data[].attributes.headline
Disorganized for those not attending in person - I was not sure what meetings were going on and was unsure how to further engage with those onsite being remote

# data[].attributes.subject
Disorganized for those not attending in person - I was not sure what meetings were going on and was unsure how to further engage with those onsite being remote

# data[].attributes.body
At times felt like too many meetings w/o clarity on who should be there, the value they add, what we should come out of meeting with. Want continued focus on who should be where and when

# data[].attributes.headline
Learning/hearing about what others have done or are doing

# data[].attributes.subject
Learning/hearing about what others have done or are doing

# data[].attributes.headline
very hard to connect with other team mates who are not present in person

# data[].attributes.subject
very hard to connect with other team mates who are not present in person

# data[].attributes.headline
Lack of well defined product/sprint backlog from ARTs

# data[].attributes.subject
Lack of well defined product/sprint backlog from ARTs

# data[].attributes.body
Working together in Bellevue during STL PI

# data[].attributes.body
We should be adapting to a changing environment but decisions were being slowly filtered down, rather than being made as an executive decision point; this reduced teams' effectiveness at pivoting

# data[].attributes.headline
PI Planning - it was difficult to collaborate with those in different locations and I did not know when I was supposed to be dialed into which session. 

# data[].attributes.subject
PI Planning - it was difficult to collaborate with those in different locations and I did not know when I was supposed to be dialed into which session. 

# data[].attributes.body
... mostly :-) Amy and Amber and Sara and others -- trying HARD to make this SAFe stuff work in a really hard environment.

# data[].attributes.headline
Working with my team members and with other teams

# data[].attributes.subject
Working with my team members and with other teams

# data[].attributes.headline
Training improvements led to more classes available for ERP

# data[].attributes.subject
Training improvements led to more classes available for ERP

# data[].attributes.headline
Increased teaming and collaboration across TCM teams

# data[].attributes.subject
Increased teaming and collaboration across TCM teams

# data[].attributes.body
Improved adherence to processes

# data[].attributes.body
Big improvements on internal collaboration within the TCM team made it easier to work towards common goals and quickly gather feedback from teammates.

# data[].attributes.headline
Impediments we raised were solved by other team members and by leadership

# data[].attributes.subject
Impediments we raised were solved by other team members and by leadership

# data[].attributes.headline
Incorporating each team's creative side (e.g. theme song, photo booth pics, etc

# data[].attributes.subject
Incorporating each team's creative side (e.g. theme song, photo booth pics, etc

# data[].attributes.headline
Willingness of team members to "dive in" and figure things out - many times without a clear path of "how to get it done"

# data[].attributes.subject
Willingness of team members to "dive in" and figure things out - many times without a clear path of "how to get it done"

# data[].attributes.body
As a new team member who joined partially through the PI, I feel like I understand my tasks and can execute them appropriately. Ramp up time was thorough and expedited. Thanks to Amy and the Bellevue team. :)

# data[].attributes.body
We work in a distributed manner for most of the year, so having an opportunity to get together allowed connections to be made that would otherwise be slow to form (if at all)

# data[].attributes.headline
We had our Objectives solid, we had our Features a bit more complete with Acceptance Criteria

# data[].attributes.subject
We had our Objectives solid, we had our Features a bit more complete with Acceptance Criteria

# data[].attributes.body
Working with ARTs directly during PI planning

# data[].attributes.headline
RTMs and coaches were available to answer questions

# data[].attributes.subject
RTMs and coaches were available to answer questions

# data[].attributes.headline
Not knowing how we were impacted by MVP, this brings more work and a new way of thinking to be implementation ready

# data[].attributes.subject
Not knowing how we were impacted by MVP, this brings more work and a new way of thinking to be implementation ready

# data[].attributes.headline
Getting involved in new opportunities on a regular basis. 

# data[].attributes.subject
Getting involved in new opportunities on a regular basis. 

# data[].attributes.headline
Lack of clearly defined product/sprint backlog

# data[].attributes.subject
Lack of clearly defined product/sprint backlog

# data[].attributes.body
- Speed dating usage is misleading

# data[].attributes.headline
The Hashtags, theme song and photo booth

# data[].attributes.subject
The Hashtags, theme song and photo booth

# data[].attributes.headline
Fun activities were added to PI Planning

# data[].attributes.subject
Fun activities were added to PI Planning

# data[].attributes.body
Agenda needs to be promulgated beyond those attending in person; a way of sharing a plan for speed-dates etc would allow distribution of effort and de-confliction of meetings

# data[].attributes.headline
That TNT was mentioned quite often at report outs

# data[].attributes.subject
That TNT was mentioned quite often at report outs

# data[].attributes.headline
SAFe coaching as part of our "daily" rhythm

# data[].attributes.subject
SAFe coaching as part of our "daily" rhythm

# data[].attributes.headline
As a person that never attend the PI directly, this PI 19.2 is the best because I can hear and see what had happened in the big room via WebEx (even the 2nd day has little bit sound system error).

# data[].attributes.subject
As a person that never attend the PI directly, this PI 19.2 is the best because I can hear and see what had happened in the big room via WebEx (even the 2nd day has little bit sound system error).

# data[].attributes.headline
Disorganization around ERP-centric SAFe training

# data[].attributes.subject
Disorganization around ERP-centric SAFe training

# data[].attributes.body
We determined in ERP LACE that we were going to have ERP-centric SAFe classes, then took too long (and still working on it) getting those classes set up to the point where people can register. The result was delays in getting people the training they needed.

# data[].attributes.body
Not being onsite with my team members made real-time collaboration challenging. We made it work, but in-person is definitely preferable.

# data[].attributes.headline
Felt disconnected in Bellevue. Challenging to follow along via webex 

# data[].attributes.subject
Felt disconnected in Bellevue. Challenging to follow along via webex 

# data[].attributes.headline
Lack of communication from PMO and leadership on attendees, flights, hotels, and what to do to prepare for the event.

# data[].attributes.subject
Lack of communication from PMO and leadership on attendees, flights, hotels, and what to do to prepare for the event.

# data[].attributes.body
Although many are important - believe it is critical we tie ad hoc requests back to PI priorities and inject into the backlog appropriately. Probably a bit too much happening outside of TFS and our 'formal' channels

# data[].attributes.headline
TNT was not able to be together in one room for PI Planning

# data[].attributes.subject
TNT was not able to be together in one room for PI Planning

# data[].attributes.body
Lack of integration with ART backlog

# data[].attributes.headline
Many agile ceremonies taking place that did not seem to directly connect with the actual work we are doing. 

# data[].attributes.subject
Many agile ceremonies taking place that did not seem to directly connect with the actual work we are doing. 

# data[].attributes.headline
Having to add all the user stories to TFS was a little tedious 

# data[].attributes.subject
Having to add all the user stories to TFS was a little tedious 

# data[].attributes.headline
Having Inspect & Adapt right after PI Planning drives a lot of feedback about the planning event rather than the whole PI

# data[].attributes.subject
Having Inspect & Adapt right after PI Planning drives a lot of feedback about the planning event rather than the whole PI

# data[].attributes.headline
We needed to schedule a lot of training classes but rooms were hard to find.

# data[].attributes.subject
We needed to schedule a lot of training classes but rooms were hard to find.

# data[].attributes.headline
That I was not able to focus on RTE role and help prepare the team prior to PI Planning

# data[].attributes.subject
That I was not able to focus on RTE role and help prepare the team prior to PI Planning

# data[].attributes.headline
Felt like we had a lot of daily meetings that repeated the same information just to an additional person or two. Repeating the same stuff several times each day so that everyone is kept in the look is not a good use of time. One status meeting a day is plenty. 

# data[].attributes.subject
Felt like we had a lot of daily meetings that repeated the same information just to an additional person or two. Repeating the same stuff several times each day so that everyone is kept in the look is not a good use of time. One status meeting a day is plenty. 

# data[].attributes.headline
TNT team members in Bellevue are spread across two buildings.

# data[].attributes.subject
TNT team members in Bellevue are spread across two buildings.

# data[].attributes.headline
Room booked in Bellevue was double booked and we had to find alternatives each day of PI planning

# data[].attributes.subject
Room booked in Bellevue was double booked and we had to find alternatives each day of PI planning

# data[].attributes.body
Awesome that I was able to attend SAFe training.

# data[].attributes.headline
SAFe-prescribed meetings often times are used for status reporting rather than for their intended purpose.

# data[].attributes.subject
SAFe-prescribed meetings often times are used for status reporting rather than for their intended purpose.

# data[].attributes.headline
How speed dating was coordinated from those leading the PI Planning and then how we were supposed to do that and do team planning at the same time

# data[].attributes.subject
How speed dating was coordinated from those leading the PI Planning and then how we were supposed to do that and do team planning at the same time

# data[].attributes.headline
the feeling of never having enough time...

# data[].attributes.subject
the feeling of never having enough time...

# data[].attributes.body
Not having any of the POs or PM with the TCM team during PI Planning made it much more difficult to break down the Features into good user stories

# data[].attributes.headline
Being remote during MVP1 announcements led to confusion on how to proceed forward with entry of User Stories as we weren't aware of how much MVP1 would impact our available time to work other User Stories.

# data[].attributes.subject
Being remote during MVP1 announcements led to confusion on how to proceed forward with entry of User Stories as we weren't aware of how much MVP1 would impact our available time to work other User Stories.

# data[].attributes.headline
Needed more time for Team planning for Features and User Stories

# data[].attributes.subject
Needed more time for Team planning for Features and User Stories

# data[].attributes.headline
That individuals entered most user stories and dependencies in TFS

# data[].attributes.subject
That individuals entered most user stories and dependencies in TFS

# data[].attributes.headline
POs too busy with other things; not enough face-to-face with the teams.

# data[].attributes.subject
POs too busy with other things; not enough face-to-face with the teams.

# data[].attributes.headline
Support from SAFe coaches during 19.1 and at 19.2 event

# data[].attributes.subject
Support from SAFe coaches during 19.1 and at 19.2 event

# data[].attributes.headline
if need to attend outside the PI location, have the technical issues solved (Connection, audio) and dedicated room for each scrum team/ART team will be the best.

# data[].attributes.subject
if need to attend outside the PI location, have the technical issues solved (Connection, audio) and dedicated room for each scrum team/ART team will be the best.

# data[].attributes.body
What's TCM product vision? Can our POs articulate them?

# data[].attributes.body
Just before this PI, the 2CES LACE sent out training on capacity panning. It was not in time, BUT, there IS time for TCM and ERP LACE to push this training and behavior across the ERP teams.

# data[].attributes.headline
there was clearer guidance on where people should be dialed into to present during the PI planning event. 

# data[].attributes.subject
there was clearer guidance on where people should be dialed into to present during the PI planning event. 

# data[].attributes.headline
Each ART could have its own PI Planning event

# data[].attributes.subject
Each ART could have its own PI Planning event

# data[].attributes.headline
Structured webex schedule during PI planning 

# data[].attributes.subject
Structured webex schedule during PI planning 

# data[].attributes.body
For TNT teams; other ARTS; and how they all tie together

# data[].attributes.headline
Value "mapping" to priorities and communication to both SLT, as well as TNT ART

# data[].attributes.subject
Value "mapping" to priorities and communication to both SLT, as well as TNT ART

# data[].attributes.headline
If the agile ceremonies were more efficient or reduced to accommodate the type of work we do. 

# data[].attributes.subject
If the agile ceremonies were more efficient or reduced to accommodate the type of work we do. 

# data[].attributes.body
Accountability of the ARTs to the user stories they plannd w

# data[].attributes.body
Accountability of the AR

# data[].attributes.body
In

# data[].attributes.body
Execution of the work with the ARTs  been planned out in their user stories

# data[].attributes.body
Integrated work with the ARTs  been planned out in their user stories

# data[].attributes.body
Each

# data[].attributes.headline
PI Planning attendee decisions and travel authorization earlier

# data[].attributes.subject
PI Planning attendee decisions and travel authorization earlier

# data[].attributes.body
Have the each team together in one location for PI Planning: PO/SM/SIs/Boeing - may have to split up the sub teams to two locations to control costs, but allow each scrum team to be face to face.

# data[].attributes.headline
More use of TFS to show dependencies and accomplisments 

# data[].attributes.subject
More use of TFS to show dependencies and accomplisments 

# data[].attributes.headline
Improved "flow down" of updates (e.g., out of Solution Planning) to team

# data[].attributes.subject
Improved "flow down" of updates (e.g., out of Solution Planning) to team

# data[].attributes.headline
At the next PI Planning event, for those not in the main room, I personally would prefer not to be in a side conference room for 8 - 10 hours waiting to know what is going on while attempting to write user stories that I don't know if they will even be relevant. I would find it more beneficial to write my stories after the event in the days finishing out 19.2.6 when the priorities are clear. 

# data[].attributes.subject
At the next PI Planning event, for those not in the main room, I personally would prefer not to be in a side conference room for 8 - 10 hours waiting to know what is going on while attempting to write user stories that I don't know if they will even be relevant. I would find it more beneficial to write my stories after the event in the days finishing out 19.2.6 when the priorities are clear. 

# data[].attributes.headline
Better communicating and demos of our capabilities and the successes of the team

# data[].attributes.subject
Better communicating and demos of our capabilities and the successes of the team