Controversial but useful practices

No estimates

• inaccurate anyway
• waste time
• lets just do what is most important

One participant mentioned that they did "no estimates" but it based on strong trust relationship with PO. Trust built with lots of effort over time.

Mentioned bad reasons for estimates: Estimates used as a stick to "hit" people with. Leads to bad behaviour

Return to office

Mentioned tools to support remote work:

• Tuple.app "the best remote pair programming app on macOS and Windows"
• gather.town "People + knowledge. All in one place."

Trunk based development

For this session defined as single main branch, no feature branches, no PR's, no review, no pre-integration server-side build

Requirements to make it work or at least support practices:

• blameless trust relationship, swarming
• Good solid automated test
• Pair programming