# data[].attributes.body
Being in person and seeing folks in person was really valuable. It's always fun to see people in general, but for something as big as UP, the in-between-meeting times seemed just as important as the planned sessions. I had so many informal one on one chats between sessions where we shared what we were working on, how it fit into the bigger UP picture, and what was or wasn't clear to us. Those types of quick alignment checks are so helpful. It was also nice to have dedicated time to focus on this for an extended period.

# data[].attributes.body
The big picture overview was really helpful. I really appreciated the level setting from leadership (John and Ann Mei) at the beginning of the meeting so we had a good sense of where we were trying to go, both in the short and long term.

# data[].attributes.body
Data Division wasn't really in the workflow (including whole departments like Insights, Data services, Data Science), which made it difficult to figure out what breakouts to go to, what dependencies required us, how to plan our time moving forward, and how to flag that we needed to be involved in something.

# data[].attributes.body
Our virtual colleagues didn't have zoom links until the last minute, and then they didn't seem to work, making it less inclusive for folks who couldn't be there in person.

# data[].attributes.body
As a scrum master, when I make/receive new m4 tix in jira, I must put it into an Epic. I want an easy way to find m4 Epics. Until now, I was using Epic Link field's type-ahead feature. Thanks.

# data[].attributes.headline
Next PI plannings, work w/n current sprint schedule

# data[].attributes.subject
Next PI plannings, work w/n current sprint schedule

# data[].attributes.body
...so that teams won't have to reschedule scrum events. With 23.3.1 starting on 6/15, every event except standup had to shift 1 week. I hope this a 1-time thing. Thanks.

# data[].attributes.body
More of us need at least view access for Kendis, 'UX' team name should be changed to 'Design and UXR', we need to better articulate future priorities several quarters into the future (I know this is a goal of the PM team).

# data[].attributes.headline
Jonathan Zuk - More post-Breakout Session Check-ins / Report outs

# data[].attributes.subject
Jonathan Zuk - More post-Breakout Session Check-ins / Report outs

# data[].attributes.body
I think other mentioned having shorter blocks of time and more time for epics/stories to marinate. I really appreciated the draft plan review where each team reported out on their work at the end of the day on Wednesday, maybe these could be more frequent to ensure all the teams are on the same page and have time to reflect on breakout session work.

# data[].attributes.headline
Devin Harvath - Incorporating UXR is a WIP

# data[].attributes.subject
Devin Harvath - Incorporating UXR is a WIP

# data[].attributes.body
At times UX research felt like an afterthought: design and UX research were grouped together into a single team called 'UX' that doesn't technically exist and that most people seemed to understand as design, UXR didn't have independent access to Kendis, and priorities beyond Q3 were not well defined.

# data[].attributes.headline
Devin Harvath - Left with a positive feeling

# data[].attributes.subject
Devin Harvath - Left with a positive feeling

# data[].attributes.body
By the end of the week it felt like a breakthrough to be working together in a coordinated process, acknowledging that we can continue to improve.

# data[].attributes.body
Let's work to get upcoming quarterly plannings on the calendar (and vet across teams) a year in advance.

# data[].attributes.headline
Jonathan Zuk - Composition of Breakout Sessions

# data[].attributes.subject
Jonathan Zuk - Composition of Breakout Sessions

# data[].attributes.body
Initially, it was challenging for those of us outside of the Technology division to know which breakout session(s) to attend.

# data[].attributes.body
Great to see everyone in person and such collaboration across teams and boards - a big step towards everyone moving in the same direction as we converge on the work! The activities were well planned and provided opportunities for folks to connect with others.

# data[].attributes.body
Appreciated Steven's re-envisioning of the cross team program planning as well as the detailed scrum schedule.

# data[].attributes.body
Observation that future quarters depend on some of the work this quarter, yet those dependencies are not shown in Kendis (because the future work isn't represented). So there are actually more dependencies than what is currently represented in Kendis.

# data[].attributes.headline
Jonathan Zuk - Bus/Prod/Arch Vision and Context 

# data[].attributes.subject
Jonathan Zuk - Bus/Prod/Arch Vision and Context 

# data[].attributes.body
The framing presentations on Tuesday morning were really helpful for guiding the work during the breakout sessions. Many of us have seen similar presentations during town halls and manager meetings, but it was helpful to be reminded about why Candid is developing the Unified Platform.

# data[].attributes.body
Look for opportunities to spread the Epic & Story writing work for an upcoming quarter across more staff, so one or two PMs are not on the hook for everything.

# data[].attributes.headline
Virginia Holmstrom - Comprehensive planning

# data[].attributes.subject
Virginia Holmstrom - Comprehensive planning

# data[].attributes.body
Need more comprehensive thinking about planning for all teams and work earlier in the process, instead of lines in the sand between UP/non-UP work

# data[].attributes.body
Combining team Jira boards under one overarching project is a step forward for transparency into all work.

# data[].attributes.body
I'll echo several others that the social activities planned during the week were well planned. Scheduling them mostly at the beginning of the week seems to have made it easier for many to feel comfortable sharing openly during the breakout sessions. It was great to see so many people in the NY office.

# data[].attributes.headline
Virginia Holmstrom - Scrum Master Capacity

# data[].attributes.subject
Virginia Holmstrom - Scrum Master Capacity

# data[].attributes.body
Many Scrum Masters, most of which wear multiple hats, were left scrambling to migrate Jira backlogs and rebuild team boards so they could schedule their work in Kendis with the rest of Candid.

# data[].attributes.body
I really appreciated seeing everyone in NYC. It was great to connect and I appreciate all of the activities that where setup.

# data[].attributes.body
Product vision, once it starts with a roadmap, then needs to zoom in on the upcoming quarter and discuss those priorities and requirements in detail. This is product's opportunity to present what priorities really matter in the next quarter and why.

# data[].attributes.body
Confusion over definition of Q3.

# data[].attributes.headline
Virginia Holmstrom - In person collaboration

# data[].attributes.subject
Virginia Holmstrom - In person collaboration

# data[].attributes.body
Enjoyed the opportunity to discuss architecture and dependency plans with other technical teams in person.

# data[].attributes.headline
Ben Negron - Priority List could of been clearer

# data[].attributes.subject
Ben Negron - Priority List could of been clearer

# data[].attributes.body
I like that we have a feature priority list. It was just confusing to follow. I recommend keep it simple and to the point.

# data[].attributes.headline
Ben Negron - Receive the planned epics ahead of PI planning from products

# data[].attributes.subject
Ben Negron - Receive the planned epics ahead of PI planning from products

# data[].attributes.body
It would be great to receive the planned epics, final prioritized list, and mockups a sprint before PI planning. This gives us an opportunity to develop a discussion plan for our team.

# data[].attributes.body
All the meetings and trips to the Liberty Island and Billiards etc. It's a wonderful event!

# data[].attributes.body
I thought it went great and condensed multiple weeks of communications into a few days. It wasn't perfect but the start of most great adventures aren't. I think it's a format that we will continue to improve on over the coming quarters iterations.

# data[].attributes.headline
Karolina - remote setting would work well

# data[].attributes.subject
Karolina - remote setting would work well

# data[].attributes.body
I'd prefer to do the planning in a remote setting throughout the entire week (maybe 3 hrs per day) instead of two packed days. Folks were worn out towards the end of the day and not focused on the actual planning.

# data[].attributes.body
The UI/UX team is not able to plan for further design work beyond search (after sprint #3) b/c next priorities are not clearly defined.

# data[].attributes.body
Generally, the UI/UX planning for the next 3 sprints went well. It was great to see folks in person.

# data[].attributes.body
Some people were not invited to breakout sessions, initially.

# data[].attributes.body
I appreciated the scrum schedule.xlsx and Kendis training calls & videos that Steven et al provided in the weeks leading up to PI so that we could review them in advance. I've viewed the xls file many times in the last month for various needs. Thank you!

# data[].attributes.body
- The new framework was extremely well presented and easy to understand
- Interdependencies between groups were solidified, visualized, and prioritized.
- Challenges/risks were addressed (i.e. visits from other teams and risk identification/mgmt review)
-Scope was approached in a more comprehensive way

# data[].attributes.headline
We could extend the planning by one day, allowing more time for iteration on team meetings and planning review.

# data[].attributes.subject
We could extend the planning by one day, allowing more time for iteration on team meetings and planning review.

# data[].attributes.headline
Collaboration between teams. We were able to invite or join one another physically when needed to plan better and weigh approaches and options.

# data[].attributes.subject
Collaboration between teams. We were able to invite or join one another physically when needed to plan better and weigh approaches and options.

# data[].attributes.body
Positive environment, particularly from members of the team

# data[].attributes.body
Food was good, but maybe order a bit more food next time

# data[].attributes.body
the schedule a couple of times last minute which was a little confusing

# data[].attributes.headline
Chris McGlade: Product kickoff sessions 

# data[].attributes.subject
Chris McGlade: Product kickoff sessions 

# data[].attributes.body
First product kick off meeting could have been more direct and succinct. I felt there was a lot of extraneous information and I left without having a clear sense of the goal. Also, the business value numbers didn't make sense to me. It would have been easier to just rank the priorities.

# data[].attributes.headline
Alison Jannette - Not enough time was given to prep for the meeting amongst PMs

# data[].attributes.subject
Alison Jannette - Not enough time was given to prep for the meeting amongst PMs

# data[].attributes.headline
Alison Jannette - Architectural Decisions and guidance

# data[].attributes.subject
Alison Jannette - Architectural Decisions and guidance

# data[].attributes.body
we walked away with a better understanding of the architecture decisions that needed to be made like:

AB 488 data is going to be loaded into CDS

Notification emails for usage alerts are being investigated if they can be sent from marketing cloud

we started the design of a provisioning API for subscriptions to the external APIs

# data[].attributes.headline
Alison Jannette - Data services team was not invited

# data[].attributes.subject
Alison Jannette - Data services team was not invited

# data[].attributes.body
data services has dependencies to other teams, especially regarding global data, which was identified and discuss by the PM, Finn Smith with the CDS team to discuss the dependency

# data[].attributes.headline
For the first time doing this...surprisingly well done

# data[].attributes.subject
For the first time doing this...surprisingly well done

# data[].attributes.body
Noting that this was the first time doing this, new tech (Kendis), so many teams involved....the event went very well overall all things considered

# data[].attributes.headline
Not enough info was provided as to Unified Platform requirements

# data[].attributes.subject
Not enough info was provided as to Unified Platform requirements

# data[].attributes.body
The Kendis epics led back to the Jira Epics, but the acceptance criteria on them was incomplete (lack of mock-ups, required fields, dependencies)

# data[].attributes.headline
Unified Platform SME should be in with teams

# data[].attributes.subject
Unified Platform SME should be in with teams

# data[].attributes.body
Having UP SMEs in with the planning teams to instantly clarify and provide info would speed up the planning process immensely

# data[].attributes.body
I felt they put us in breakout rooms without much direction

# data[].attributes.headline
David Barr - 3rd parties in breakout rooms

# data[].attributes.subject
David Barr - 3rd parties in breakout rooms

# data[].attributes.body
We had to switch to our team zoom meeting instead of the breakout room for planning because we were unable, it seemed, to invite contractors.

# data[].attributes.body
The remote experience was pretty solid, and I suspect that is due to the work done to set the video conferencing infrastructure up ahead of time.

# data[].attributes.body
SAFe Training to be scheduled for the teams for understanding the SAFe concepts

# data[].attributes.headline
Steven Salgado - Could not switch between zoom breakout rooms.

# data[].attributes.subject
Steven Salgado - Could not switch between zoom breakout rooms.

# data[].attributes.headline
Harsha Vardhan-All Risks identification occurred sooner

# data[].attributes.subject
Harsha Vardhan-All Risks identification occurred sooner

# data[].attributes.body
Risks were identified sooner and mitigation plan were in place as well by the end of the session.

# data[].attributes.headline
Steven Salgado - Dependencies were shown on one screen

# data[].attributes.subject
Steven Salgado - Dependencies were shown on one screen

# data[].attributes.headline
Remote attendees stranded during breakouts

# data[].attributes.subject
Remote attendees stranded during breakouts

# data[].attributes.body
We had some teammates who were stuck in main room for many minutes bc for some reason they weren't assigned to our breakout. It looks like Zoom has option for viewers to choose their own breakouts; we might test it in-session and as backup, assign folks. https://support.zoom.us/hc/en-us/articles/115005769646
Also, during zoom breakouts, it's good practice for someone to keep an eye on main room for questions, strandees, etc. I had to physically go to main room to assign folks; thankfully host laptop was always open.