# data[].attributes.body
Some form of blocking state on stories. New column? Status on story?

# data[].attributes.body
Meetings with Seb / Ferran / Stephen to review designs before sprint starts

# data[].attributes.body
It's nice !

# data[].attributes.headline
GE: Onboarding Rafa with real stories :)

# data[].attributes.subject
GE: Onboarding Rafa with real stories :)

# data[].attributes.body
When there is 2 scenarios in a story, it should be 2 stories
I mean for example a scenario could include each case of errors but for example when there is additional popup or confirm screen it should be a new story = we have to find a good compromise.
Big story = bad estimation = bad velocity = bugs = unreadable PR = ... (add what you want)

# data[].attributes.headline
IG: Bad specified/detailed stories and worse estimated

# data[].attributes.subject
IG: Bad specified/detailed stories and worse estimated

# data[].attributes.body
Specially backend ones on Invitations

# data[].attributes.body
Multiteam is a good opportunity to affect MRR

# data[].attributes.headline
GE: Multi team is good for fix and improve our platform. 

# data[].attributes.subject
GE: Multi team is good for fix and improve our platform. 

# data[].attributes.headline
IG: Really so difficult to do a REST POST vs GraphQL POST

# data[].attributes.subject
IG: Really so difficult to do a REST POST vs GraphQL POST

# data[].attributes.body
I mean migration to circleci2, release more often...