jQueryTO 2013 - Creating a Development Culture

2,833 views

Published on

From jQueryTO, held in Toronto March 2-3 2013, my talk on creating a stronger developer process and culture within a mixed team

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,833
On SlideShare
0
From Embeds
0
Number of Embeds
1,114
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

jQueryTO 2013 - Creating a Development Culture

  1. 1. / Creating a Development Culture
  2. 2. MonikaPiotrowiczFront End Developer,Jet Cooper@monsika 2
  3. 3. We design and build products for web, mobile andtablet devices 3
  4. 4. People we work withWe’ve had an opportunity to work alongside leadingCanadian startups, brands, and organizations 4
  5. 5. TodayWhat we’re doing today
  6. 6. ProcessA process exists to support creativity, not resist it 6
  7. 7. Disclaimers1. This is only our approach2. This is difficult3. Will never be perfect, just better for now 7
  8. 8. Good conference, right?But what happens Monday? 8
  9. 9. Why does this happen?Don’t go stop chasing Waterfalls 9
  10. 10. Design Development 10
  11. 11. Discovery ProductionDesign Development 11
  12. 12. Discovery ProductionDesign Development 12
  13. 13. != short order cooksWe’re problem solvers too, dammit! 13
  14. 14. ChangesWe need to keep up with them 14
  15. 15. 15
  16. 16. IdeasWe need a way to share them 16
  17. 17. (we didn’t pose for this, I swear) 17
  18. 18. DesignersWe want to work with them 18
  19. 19. Image Credit: Cassie McDaniel 19
  20. 20. Time for a changeInside and outside of projects 20
  21. 21. Devs inside projectsChanging the way we build together
  22. 22. A new approachKilling the “stagger” 22
  23. 23. Discovery ProductionDesign Development 23
  24. 24. Discovery ProductionDesign Development 24
  25. 25. 25
  26. 26. So uh, what now?Two new opportunities 26
  27. 27. 1. Your new best friendSurprise, it’s the designer! 27
  28. 28. Levellingthe playing fieldA more collaborative approach to design 28
  29. 29. 2. Research & PrototypeThe chance to actually learn about and implement thenew things that interest you 29
  30. 30. Your sandboxThe freedom to focus on one problem at a time 30
  31. 31. Form and functionPrototypes can be as bare bones or complex as we want 31
  32. 32. 32
  33. 33. 5333
  34. 34. Your future selfwill thank youThe earlier an assumption is challenged, the easier itwill be to fix 34
  35. 35. 35
  36. 36. Drive the designYour code is your chance to create a concept 36
  37. 37. 37
  38. 38. Share & iterateDesign informs developmentDevelopment informs design 38
  39. 39. Design FED Iteration 39
  40. 40. Devs in the companyOrganization-wide activities
  41. 41. Demo DaysCross-studio learning 41
  42. 42. Developer meetingsKeep up to date with what the other developers havebeen up to 42
  43. 43. Recess!!!Self-directed research, prototyping, and internal sideprojects.Bring lessons back to process 43
  44. 44. Lessons LearnedIt’s a lot to implement, but a strong developer culturecan bring a lot of benefits
  45. 45. What we gain1. We make more informed decisions2. Time is reduced and quality increases3. Happy developers, yay! 45
  46. 46. Ok so what?How can you get the ball rolling for your team?
  47. 47. Talk to your designersYour ally, because no one wants to design in the dark 47
  48. 48. Become an AdvocateTalk about the benefits of a strong developer team,Don’t just vent, have meaningful discussions 48
  49. 49. Take the first stepEven if it’s on your own time, the results will speak forthemselves 49
  50. 50. Fix the processLet’s create a stronger stance collectively
  51. 51. Thanks!@monsikajetcooper.com
  52. 52. Questions+ Answers (Possibly)

×