Distributed People and Processes
People:

People:
- Teamwork & Spirit & Communication are keys
- Daily standup getting shorter
- Commitment to stick to estimates
- Knowledge and technical stuff sharing (avoiding Super Heroes)
- Feeling owner
- Support from the team for the newcomers
- Ask for help as soon as possible
- Pair programming and reviewing to get better understanding
- Be a trustworthy team member
- Tell when you go offline so that team understands if you’re online
- Sharing vision and plans
Processes:
- Introducing a new technology into the stack should be validated by product needs first
- Include all team members in decisions
- Keep every meetings structured and time-boxed
- Keep and shoot notes of your discussions/meetings
- Kickoff the project before diving into coding
- Follow the coding style and automate the code checks
- Feedback for constructive code review
- Comment your code (yes sir!!!)
- Care about backward-compatibility
- Check your test coverage and don’t merge code without tests validation
- Split artefact into small commit (less than 500 commits for previous experiences)
- If you’re stuck — don’t dig to long, ask for help after 2 hrs maximum