# data[].attributes.body
- discussion culture from the "PR culture" meeting
- PR review / task / PR review /... workflow
- excellent velocity

# data[].attributes.body
gtm architecture

# data[].attributes.body
More focus on bugfixes.

# data[].attributes.body
Team spirit and mutual responsibility

# data[].attributes.body
Regarding calls: keep calls on point, try to stick to the basics (question/answer/explanation) and keep to a minimum the volume of new information when presenting something

# data[].attributes.body
- Meeting timings

# data[].attributes.body
allowing questions to flow instead of shutting it down

# data[].attributes.body
Meeting topic patterns. What should be discussed at which level in sprint meetings and what can be left out

# data[].attributes.body
Low quality standard of internal tools.

# data[].attributes.body
CI tools development was a side activity in the past, if we need new tools we need to plan in time for creating them and remove the old ones

# data[].attributes.body
agreements carried out after talks i.e. Pull requests culture, communication.

# data[].attributes.body
meetings lacks motivation factor, aka boring

# data[].attributes.body
- Noise in the office

# data[].attributes.body
more healthy discussions, rather than arguing indefinitely

# data[].attributes.body
a review is a first of all a presentation not a deep dive into technical details
and "what if" discussions going in circles and they should be cut short by the
moderator at some point

# data[].attributes.body
more involvement of UI within our tech investigation and refinements

# data[].attributes.body
sticking to our UI guidelines and rules

# data[].attributes.body
clean and sure refinement, more careful planning

# data[].attributes.body
I want to see MDM ci config work

# data[].attributes.body
- let's not get rid of "newest way to implement smth (apple recommended)" just to not "upset" our grumpy old codebase :)

# data[].attributes.body
Motivation (Passbook fix, Jenkins script fix, Architecture team, Tracking Stream)

# data[].attributes.body
Evaluation tasks should be discussed technically in a dev+qa round(meeting/slack channel) before presenting it in the review