# data[].attributes.headline
Kudos to Stephen for making extra mile on improving system performance and stabilization

# data[].attributes.subject
Kudos to Stephen for making extra mile on improving system performance and stabilization

# data[].attributes.headline
Engineering alignment around implementation with CX eng team was missing

# data[].attributes.subject
Engineering alignment around implementation with CX eng team was missing

# data[].attributes.body
Implementation details on EIDs appending wasnt resolved with Jon

# data[].attributes.headline
Support from Mark Henry on Reverse proxy

# data[].attributes.subject
Support from Mark Henry on Reverse proxy

# data[].attributes.headline
No resource commitment from CX team in Q4 resulting in changes in q1

# data[].attributes.subject
No resource commitment from CX team in Q4 resulting in changes in q1

# data[].attributes.headline
CX team changed the requirement set around templates last minute

# data[].attributes.subject
CX team changed the requirement set around templates last minute

# data[].attributes.body
New campaigns were added after October and no one notified

# data[].attributes.body
Launch got pushed back again based on missed business requirements. Some ideas for avoiding this in the future:
1) Create a requirements checklist (similar to the arch review template) and make sure we have answers to all questions before allocating cycles.
2) Clear definition of roles and responsibilities when it comes to requirements gathering. What are the responsibilities of the PM, dev manager, engineers, etc.?

# data[].attributes.headline
Better workflow on confirming the templates

# data[].attributes.subject
Better workflow on confirming the templates

# data[].attributes.body
I can talk about it more during our meeting. From a tester point of view. Template is the format of the input for CCP, and that's something should be defined before development.

I'm also seeing this happening with WeChat also.

Related with this point. We need more Robb. During this sprint, Robb is almost like the source of truth, therefore like one point failure

# data[].attributes.body
Props to everyone for the huge amount of tasks completed this sprint to get CCP off the ground and performing well!

# data[].attributes.body
How do we make the backlog refinement process better?  How do we limit meetings for everyone and make the meetings everyone needs to be in more focused (stand-ups, refinement, planning, design meetings, etc)

Some ideas after talking to a few of you this week:
1) Split the team into separate Scrum teams - perhaps by grouping the epics? Or having team members, joining other teams for PCS, Outbound Platform (AWS), etc.
2)  Refinement: Have the SM pre-allocate stories to 1-2 people to "pre-refine" the stories to make sure they basically make sense
3) What does our PO need to "make stories more clear" ?