# data[].attributes.body
Let's pull Dimasounet

# data[].attributes.body
Circle2, ECS...

# data[].attributes.body
(well for Nour it doesn't matter but... ;p)

# data[].attributes.body
(was cool ;)

# data[].attributes.headline
GE: lot of noise logs (if there are) ... Now too much logs = No logz

# data[].attributes.subject
GE: lot of noise logs (if there are) ... Now too much logs = No logz

# data[].attributes.body
Design System Building

# data[].attributes.body
Logz

# data[].attributes.headline
GE: add technical backlog and technical stories

# data[].attributes.subject
GE: add technical backlog and technical stories

# data[].attributes.body
2 new majors release of Cucumber that changes all steps format, 1 new major release of material UI...

# data[].attributes.body
Dropping legacy/unused/dead code

# data[].attributes.body
being able to determine traffic and anomalies

# data[].attributes.body
Warning from business side of events that can cause spikes in traffic

# data[].attributes.body
Adding new tasks inside the stories once planned

# data[].attributes.body
Measurement of return of investment of features. Eg, working hours on mobile.

# data[].attributes.body
UI Element Checking on Implemented features

# data[].attributes.headline
GE: New Backend Engs confirmed - starting in two weeks

# data[].attributes.subject
GE: New Backend Engs confirmed - starting in two weeks

# data[].attributes.body
Explain properly stories

# data[].attributes.body
Data contract. Try not to have complex responses as seen in the working hours feature that was quite hard to implement on the mobile apps

# data[].attributes.body
Defn of ready of stories. Feature toggles defined, end points ready and designs attached prior to sprint start.

# data[].attributes.body
Try get back to continuous deployment

# data[].attributes.body
Ireland Football Team

# data[].attributes.body
Add "so that..." to story defn to better understand value