# data[].attributes.body
Better dailys

# data[].attributes.body
No skip test during release.
e.g. We want to just run `mvn release:prepare release:perform` and done.

# data[].attributes.body
Some standards on the new components missing. E.g. private members, what is allowed in torq etc, " or '

# data[].attributes.headline
We should clear any misunderstandings as soon as possible

# data[].attributes.subject
We should clear any misunderstandings as soon as possible

# data[].attributes.body
I think we should all be on the same page with what we are doing, why are doing it this way.

# data[].attributes.headline
Resolving issues as "duplicates" when it is not true

# data[].attributes.subject
Resolving issues as "duplicates" when it is not true

# data[].attributes.body
work even one step more on clean defined user stories

# data[].attributes.body
Capacity planning a bit "shaky"

# data[].attributes.body
If there are no clear "Steps to reproduce" and samples, update the status with "Needs more information"

# data[].attributes.body
We are in a state where we don't know exactly what needs to be done and things just pop up

# data[].attributes.body
Jürgen: Standards/Linting between new and "old" components => create story for investigation and fixing

# data[].attributes.body
All: https://www.youtube.com/watch?v=u4ZoJKF_VuA

# data[].attributes.body
Planning: we try to create subtasks for bigger stories (5 & 8 points)

# data[].attributes.body
Jürgen&Oscar: investigate last sprints about velocity, blockers, etc.