People:

  • Teamwork & Spirit & Communication are keys
  • Daily standup getting shorter
  • Commitment to stick to estimates
  • Knowledge and technical stuff sharing (avoiding Super Heroes)
  • Feeling responsible
  • 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
  • Provide an agenda for each meeting
  • Keep every meetings structured and time-boxed
  • Take and shoot notes of your discussions/meetings
  • Kickoff the topic before diving into coding
  • Follow the coding style and automate the code checks
  • Constructive code review by feedback
  • Comment your code (et oui!!!)
  • Care about backward-compatibility
  • Don’t do premature code reuse/optimization
  • Check your test coverage and don’t merge code without validate tests
  • Split artifact into small commit (less than 400 commits)
  • If you’re stuck — don’t dig to long, ask for help after 2 hrs max