Trophy Winning Teams - Drupal Con 2015

"Players don't win you trophies, teams win trophies". A team works better when they work together, no matter whether the goal is winning the World Cup or creating amazing websites.

Any development team, whether large or small needs to ensure that it works together as a cohesive unit in order to produce the best possible output. This can mean ensuring there's consistency in the code being written. Ensuring everyone stays up-to-date with the fast-moving pace of the web industry. As well as the ability for any project to be worked on by one or more team members at a time and have the ability to be handed over if a developer takes time off.

In this talk I'll take a look at how as a development team we can work better together, taking a look at some examples from great sporting teams. Covering everything from coding style guides, team training techniques, and code reviews, all the way through to Dutch Total Football; I'll cover a breadth of areas your team can use to improve their teamwork skills and create better cohesion and a great team atmosphere.

Transcript

1. @onishiweb Trophy winning teams Adam Onishi DrupalCon Europe September 2015
2. @onishiweb Teams
3. @onishiweb – Jose Mourinho “Players don't win you trophies, teams win trophies.” Teams
4. @onishiweb Sporting teams
5. @onishiweb Planning Sports
6. @onishiweb The “play” Sports
7. @onishiweb Sports Sports @onishiweb
8. @onishiweb Teamwork Sports
9. @onishiweb Maul! @onishiweb
10. @onishiweb Everyone is equal Sports
11. @onishiweb Sports @onishiweb
12. @onishiweb Adaptability Sports
13. @onishiweb Sports @onishiweb
14. @onishiweb Communication Sports
15. @onishiweb Sports @onishiweb
16. @onishiweb Development teams Sports
17. @onishiweb @onishiweb Sports
18. @onishiweb Baseline
19. @onishiweb Boilerplate Planning
20. @onishiweb Planning https://github.com/wearearchitect/Frontend-Boilerplate
21. @onishiweb assets/ |- scss/ | |- settings/ | |- tools/ | |- […] |- images/ |- javascript/ | |- src/ | |- vendor/ Planning
22. @onishiweb Gulp! Planning
23. @onishiweb Pattern library Planning
24. @onishiweb Planning @onishiweb
25. @onishiweb Planning https://github.com/madebymany/css-patterns
26. @onishiweb Coding Consistently
27. @onishiweb – Mark Otto (@mdo) “Code should look as if it's been written by one person, no matter how many people have worked on it” Consistency
28. @onishiweb Code style guides Consistency
29. @onishiweb Consistency http://codeguide.co/
30. @onishiweb Consistency http://sass-guidelin.es/
31. @onishiweb Consistency https://github.com/onishiweb/code-style
32. @onishiweb – Mark Otto (@mdo) “Enforce these, or your own, agreed upon guidelines at all times. Small or large, call out what's incorrect.” Consistency
33. @onishiweb Consistency @onishiweb
34. @onishiweb Consistency @onishiweb
35. @onishiweb The Rules https://github.com/wearearchitect/Frontend-Rules Consistency
36. @onishiweb Where possible all of these rules should be followed to the letter. But, all rules are open to discussion and review. Obviously there are also times where a rule must be broken, but you should be able to explain why it was necessary and what benefit it gave you. Rule 1: Obey the rules Consistency
37. @onishiweb Consistency None of these rules are personal, there is no agenda in the rules; it's all about the code. The rules are here to help us write good code and work together as a team. It's about learning as well, front end development is continually evolving with new techniques and new tools becoming available all the time, the rules will keep evolving with these best practices and be updated over time. Rule 4: It's all about the bike code.
38. @onishiweb Consistency Most front end developers are familiar with JavaScript and jQuery, but there are now more frameworks than you can shake a stick at! Whether it's Angular, Meteor, Backbone, Ember, Coffeescript, or Node.js there's always something new to learn. Rule 12: The correct number of JavaScript libraries to know is n+1
39. @onishiweb Consistency
40. @onishiweb Mistakes Consistency
41. @onishiweb @onishiweb Consistency
42. @onishiweb ”The Rules” Consistency
43. @onishiweb • Be consistent. • Don't rewrite existing code to follow this guide. • Don't violate a guideline without a good reason. • A reason is good when you can convince a teammate. https://playbook.thoughtbot.com/#style-guide Thoughtbot’s Playbook Consistency
44. @onishiweb Enforcing Consistency
45. @onishiweb Linting Consistency
46. @onishiweb Code reviews Consistency
47. @onishiweb @onishiweb Consistency
48. @onishiweb C0de reviews Consistency
49. @onishiweb Reading good code Consistency https://www.youtube.com/watch?v=mW_xKGUKLpk
50. @onishiweb Pull Requests Consistency
51. @onishiweb Consistency
52. @onishiweb Consistency
53. @onishiweb Nothing Personal Consistency
54. @onishiweb @onishiweb Consistency
55. @onishiweb Code review etiquette Consistency
56. @onishiweb Documentation
57. @onishiweb General Documentation
58. @onishiweb Contextual Documentation
59. @onishiweb For Reference Documentation
60. @onishiweb Onboarding Documentation
61. @onishiweb Teamwork
62. @onishiweb Smaller teams Teamwork
63. @onishiweb Mentorship Teamwork
64. @onishiweb Responsibility Teamwork
65. @onishiweb Buddy System Teamwork
66. @onishiweb Learning Teamwork
67. @onishiweb Sharing knowledge Teamwork
68. @onishiweb Developer déjeuner Teamwork
69. @onishiweb Group code reviews Teamwork
70. @onishiweb Teamwork @onishiweb
71. @onishiweb Conferences & Meet ups Teamwork
72. @onishiweb Extra time!
73. @onishiweb Great dev teams Extra time
74. @onishiweb • Planning • Teamwork • Equality • Adaptability • Communication Extra time
75. @onishiweb Extra time @onishiweb
76. @onishiweb Adam Onishi DrupalCon Europe September 2015 Gracias