# data[].attributes.body
should avoid long periods of time without upgrading dependencies

# data[].attributes.body
New standup format is taking quite a long time. Not sure it is useful to show random code on the screen to show "proud code". Sometimes we delve very deep into some topic, maybe standup facilitator should enforce a time limit for each person or we can agree to put longer topics after everyone has had a turn.

# data[].attributes.body
task itself

# data[].attributes.headline
Sorry about OTP thingy - I expected if adding is ok, I can do full path with charging in next day.

# data[].attributes.subject
Sorry about OTP thingy - I expected if adding is ok, I can do full path with charging in next day.

# data[].attributes.body
3, 9

# data[].attributes.body
3 & 10

# data[].attributes.body
flexibility

# data[].attributes.body
office day

# data[].attributes.body
1, 3

# data[].attributes.body
fail fast

# data[].attributes.body
agreements can change, as life and circumstances change- we also can change rapidly.

# data[].attributes.body
🤸 way to adjust to changing requirements

# data[].attributes.body
bringing value to customer earlier, shorter feedback loop

# data[].attributes.headline
Select 1 or 2 of those where you can see an opportunity to improve next iteration 

# data[].attributes.subject
Select 1 or 2 of those where you can see an opportunity to improve next iteration 

# data[].attributes.headline
What made you happy during this sprint? 

# data[].attributes.subject
What made you happy during this sprint? 

# data[].attributes.body
Bring out positive things that helped moving towards our sprint goal?

# data[].attributes.body
You can express it with a word or 2 or a pic or an emoticon or.... your choice