# data[].attributes.headline
Strange situation with Small Client Stories (up-to-date or not?)

# data[].attributes.subject
Strange situation with Small Client Stories (up-to-date or not?)

# data[].attributes.body
Stories in the backlog should be refined before PIPE to define if they are still actual.

# data[].attributes.body
We have features & OKRs. Isn't enough?

# data[].attributes.headline
UA: Good facilities & timing & foods & drinks & provision :)

# data[].attributes.subject
UA: Good facilities & timing & foods & drinks & provision :)

# data[].attributes.body
if it has been agreed with PM/PPM that some features can be postponed/removed/not pulled - they should be removed from the backlog for better/more transparency

# data[].attributes.body
The purpose of getting together at a PIPE event is to make the most optimal plans... so teams should expect that some re-planning may occur... that should be seen as a natural thing and not a negative thing...

# data[].attributes.headline
Virtual pipe makes things more complicated... 

# data[].attributes.subject
Virtual pipe makes things more complicated... 

# data[].attributes.body
It's difficult to get easy access to the right people and get them all together... especially in a pipe like this with many big features that required many teams.. then it's easier with everyone at the same location for easy access to the right people -> faster resolve issues...

# data[].attributes.body
Refinement happens way to late.. it should be ongoing - not last minute in the last 2 weeks... it partly ruins the IP sprint for many (despite IP is for Innovation AND PLANNING) - as many/some are stuck in too meetings ....)

# data[].attributes.body
- Many(too) big features
- Many not in 'backlog' column

# data[].attributes.body
Sorry to see teams forgot doc stories on features - but they will probably appear latest early the week after the PIPE.

# data[].attributes.body
So nice to see doc stories added to features! <3

# data[].attributes.headline
Change of feature prioritazion on day 2 of the PIPE.

# data[].attributes.subject
Change of feature prioritazion on day 2 of the PIPE.

# data[].attributes.body
Virtual PIPE only works well for teams that does not need to talk to any other teams or the leadership team. For the rest of us it can be a struggle when teams or people are in a different country.

# data[].attributes.body
Maybe the refinement process should include that each feature is discussed with at least 3 teams. This should ensure that all teams have something from top 10 to pull and we can possibly avoid re-planning.

# data[].attributes.headline
PIPE starts from feature Refinement. We need to improve refinement as a process. Teams should share their analysis before PIPE. It is important for “grouped” features or projects especially for must-pulled ones.

# data[].attributes.subject
PIPE starts from feature Refinement. We need to improve refinement as a process. Teams should share their analysis before PIPE. It is important for “grouped” features or projects especially for must-pulled ones.

# data[].attributes.headline
A lot of time wasted on features that were deprioritized on day 2.

# data[].attributes.subject
A lot of time wasted on features that were deprioritized on day 2.

# data[].attributes.headline
No feature that must be pulled should be more than swag 2.

# data[].attributes.subject
No feature that must be pulled should be more than swag 2.

# data[].attributes.headline
Far too many big features in the backlog. It makes it very difficult to fit a plan together, and forces a team to commit themselves fully to one big project. It is also easier for complications to hide in big features.

# data[].attributes.subject
Far too many big features in the backlog. It makes it very difficult to fit a plan together, and forces a team to commit themselves fully to one big project. It is also easier for complications to hide in big features.

# data[].attributes.headline
Talking in person is much more effective than over a video conference link

# data[].attributes.subject
Talking in person is much more effective than over a video conference link

# data[].attributes.headline
PI Objectives don't seem to be used or have any purpose, so why spend time on it?

# data[].attributes.subject
PI Objectives don't seem to be used or have any purpose, so why spend time on it?

# data[].attributes.headline
Virtual painful for cross-functional features

# data[].attributes.subject
Virtual painful for cross-functional features

# data[].attributes.body
Lost a lot of time where face to face the issues could have been easily resolved. Also hard when teams are hidden away on other floors and in random rooms

# data[].attributes.body
E

# data[].attributes.headline
Healthy food instead of sweets on the Pipe

# data[].attributes.subject
Healthy food instead of sweets on the Pipe

# data[].attributes.body
c

# data[].attributes.headline
"Pull don't push" completely doesn't work for some teams ;(

# data[].attributes.subject
"Pull don't push" completely doesn't work for some teams ;(

# data[].attributes.body
Dev support while on PIPE is not optimal. I would prefer that if really necessary that somebody is on support, then it would be handled differently.

# data[].attributes.body
MHT: Big screen in Ground Course 3 (and the other ground course room as well I think) also make jabber crash.

# data[].attributes.headline
Nice to sit in separate rooms (not atrium). Avoids noise and distractions.

# data[].attributes.subject
Nice to sit in separate rooms (not atrium). Avoids noise and distractions.

# data[].attributes.headline
ENY: SoS with both SMs and PMs goes well.

# data[].attributes.subject
ENY: SoS with both SMs and PMs goes well.

# data[].attributes.headline
ENY: It was great to see Machu Picchu team in CPH in a virtual PIPE

# data[].attributes.subject
ENY: It was great to see Machu Picchu team in CPH in a virtual PIPE

# data[].attributes.headline
ENY: The system that is used for operating the big screen in Ground Course 3 is suboptimal. Cursor movements in laptop and big screen are not in sync.

# data[].attributes.subject
ENY: The system that is used for operating the big screen in Ground Course 3 is suboptimal. Cursor movements in laptop and big screen are not in sync.

# data[].attributes.headline
ENY (using the feedback from Frank): I know that we came to this state by improving over addressing input from retrospectives about noise/temperature etc. and I know that equipment (screens) is limited and I know that at least one team had to have continuous video connection, but in CPH the atrium could be filled with more teams instead of using 3 additional rooms. Only 4 teams in atrium and limited interaction between them gives the impression of a collection of teams working on virtually separate backlog rather than an ART which is a team of teams.

# data[].attributes.subject
ENY (using the feedback from Frank): I know that we came to this state by improving over addressing input from retrospectives about noise/temperature etc. and I know that equipment (screens) is limited and I know that at least one team had to have continuous video connection, but in CPH the atrium could be filled with more teams instead of using 3 additional rooms. Only 4 teams in atrium and limited interaction between them gives the impression of a collection of teams working on virtually separate backlog rather than an ART which is a team of teams.

# data[].attributes.headline
ENY: Perhaps PIPE days can start at 10:00 so that the teams are done with batch jobs (or autotest issues in general) and "really" ready for planning.

# data[].attributes.subject
ENY: Perhaps PIPE days can start at 10:00 so that the teams are done with batch jobs (or autotest issues in general) and "really" ready for planning.

# data[].attributes.headline
ENY: As a team, we are not happy about the fact that our team members have to work on auto test in the morning, which lasts even after the train starts planning. 

# data[].attributes.subject
ENY: As a team, we are not happy about the fact that our team members have to work on auto test in the morning, which lasts even after the train starts planning. 