# data[].attributes.body
It took a long time to resolve access issues, so we had to make do with Trello for much of the PI, then switch over midway through.

# data[].attributes.headline
Communication with Shared Services had some bumps

# data[].attributes.subject
Communication with Shared Services had some bumps

# data[].attributes.body
Much of this was due to confusion over the use of Trello vs. VSTS. Met with Debbie Jacobson to iron out process. It looks like Shared Services may also be structured differently during the next PI (Kanban team).

# data[].attributes.body
Juggling new platforms of communication is still a concern.

# data[].attributes.body
Challenges with communication for virtual participation --especially during the feature selection process

# data[].attributes.body
This iteration felt like tasks transitioned from one team member to the next much more smoothly than in previous iterations.

# data[].attributes.body
During the first PI, teams did not have advance information about the features, and the initial pull during PI planning was a free-for-all. Extensive Pre-Planning taking place during this PI should help ensure that the teams have a better idea of what features to pull for the next PI.

# data[].attributes.body
some teams had separate IAs for each asset, as we used to. Some teams didn't. Not only does this create an issue of where to log time, but other issues as well (using IAs on storyboards, using IAs for historical reference on how an asset was created, communicating with shared services, etc.)

# data[].attributes.headline
I think this team in general worked well together.  

# data[].attributes.subject
I think this team in general worked well together.  

# data[].attributes.headline
not having Multimedia content to work on.

# data[].attributes.subject
not having Multimedia content to work on.

# data[].attributes.headline
Communication between team members to solve problems quickly

# data[].attributes.subject
Communication between team members to solve problems quickly

# data[].attributes.body
Knowing where the team stands on a task and assigning to yourself/when/where to pass. Hopefully will improve with deeper understanding of VSTS

# data[].attributes.body
Each successive iteration, team got better at working together and figuring out how to achieve iteration goals.

# data[].attributes.body
communication on VSTS cards - noting things as we used to in IAs so the asset still has a creation history.

# data[].attributes.body
Demos are an encouraging way for teams to "show off" what they have accomplished in each iteration, and have that work recognized.

# data[].attributes.body
Team needs refresher training on the platform. This will take place during I&P.

# data[].attributes.body
Everything we have worked on has been a breeze to review. Everything looks great.

# data[].attributes.body
Knowing how we will track time -- will it continue to be in tickets, use of calendar for pto, etc.

# data[].attributes.body
We have a draft; finalize for the next PI, then refine over time.

# data[].attributes.headline
Continue Cross-Training and Pull a Mix of Features so that whole team is able to stay fully occupied

# data[].attributes.subject
Continue Cross-Training and Pull a Mix of Features so that whole team is able to stay fully occupied

# data[].attributes.body
Things are still scattered as far as SP, tickets, trello, vsts

# data[].attributes.body
Murky acceptance criteria, stemming from little information during feature pulls, made it unclear which team was responsible for certain tasks (QA, etc)