From a workflow to a flow that works

From a workflow to a flow that works

Présentation donnée à Paris.rb sur les best practices en dévelopement et comment les mettre en place progressivement dans votre équipe.

9ea0ab2c0ee3df9115982c9b2c7585ba?s=128

Martin Van Aken

June 03, 2014
Tweet

Transcript

  1. From a workflow to a flow that works “They are

    so big and I’m so small”
  2. About us @toch @martinvanaken Co-founders @8th_color Blog: blog.8thcolor.com PullReview http://pullreview.com

    Ask for a demo!
  3. About.us

  4. You have 20 minutes to find whether I’m the talented

    one or the funny one
  5. None
  6. None
  7. Best Practices

  8. None
  9. Sprint Plannings

  10. None
  11. Sprint Plannings Unit Tests

  12. None
  13. Sprint Plannings Unit Tests Feature Branches

  14. None
  15. Sprint Plannings Unit Tests Feature Branches Code Reviews

  16. None
  17. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

  18. None
  19. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups
  20. None
  21. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews
  22. None
  23. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing
  24. None
  25. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions
  26. None
  27. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives
  28. None
  29. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives One Step Deploy
  30. None
  31. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives One Step Deploy Test Environments
  32. None
  33. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives One Step Deploy Test Environments Sanity Tests
  34. None
  35. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives One Step Deploy Test Environments Sanity Tests Pair Programming
  36. None
  37. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives One Step Deploy Test Environments Sanity Tests Pair Programming Error Reporter
  38. None
  39. Sprint Plannings Unit Tests Feature Branches Code Reviews Continuous Integration

    Daily Standups Automated Code Reviews Usability Testing Design Sessions Retrospectives One Step Deploy Test Environments Sanity Tests Pair Programming Team Chat Error Reporter
  40. It can be done

  41. Facebook does it

  42. Facebook’s 500+ engineers manage a 1.5 GB application and can

    all push code to their 1B+ users
  43. Atlassian does it

  44. Atlassian manages a portfolio of application and grew to more

    than 250 employees before even needing team leaders
  45. Microsoft does it

  46. Microsoft scores 12/12 on the Joel Test

  47. Me?

  48. Sometimes I’ve trouble just delivering my little functionality to my

    client
  49. Relax. Breath.

  50. You cannot arrive there in one day

  51. None of those teams did arrive there in one day

  52. But...

  53. You can get started

  54. None
  55. Scrum is a good place to start

  56. Nobody expect the Agile Inquisition

  57. Scrum is a good place to start Planning → Development

    → Retrospective
  58. What went well during the sprint? What could be improved

    in the next sprint?
  59. Starter Kit

  60. @8th color (3 senior developers)

  61. • Sprints ◦ Planning ◦ Retrospective ◦ Daily Standup

  62. • Sprints ◦ Planning ◦ Retrospective ◦ Daily Standup •

    Issues ◦ Unit Tests
  63. • Sprints ◦ Planning ◦ Retrospective ◦ Daily Standup •

    Issues ◦ Unit Tests ◦ Feature Branches ◦ Code Reviews
  64. • Sprints ◦ Planning ◦ Retrospective ◦ Daily Standup •

    Issues ◦ Unit Tests ◦ Feature Branches ◦ Code Reviews
  65. • Sprints ◦ Planning ◦ Retrospective • Issues ◦ Unit

    Tests ◦ Feature Branches ◦ Code Reviews • Automation ◦ CI (branches)
  66. • Sprints ◦ Planning ◦ Retrospective • Issues ◦ Unit

    Tests ◦ Feature Branches ◦ Code Reviews • Automation ◦ CI (branches) ◦ Automated CRs
  67. • Sprints ◦ Planning ◦ Retrospective • Issues ◦ Unit

    Tests ◦ Feature Branches ◦ Code Reviews • Automation ◦ CI (branches) ◦ Automated CRs • Environments ◦ Staging ◦ Deploy Pipeline
  68. • Sprints ◦ Planning ◦ Retrospective • Issues ◦ Unit

    Tests ◦ Feature Branches ◦ Code Reviews • Automation ◦ CI (branches) ◦ Automated CRs • Environments ◦ Staging ◦ Deploy Pipeline ◦ Sanity Test
  69. • Sprints ◦ Planning ◦ Retrospective ◦ Team Chat •

    Issues ◦ Unit Tests ◦ Feature Branches ◦ Code Reviews • Automation ◦ CI (branches) ◦ Automated CRs • Environments ◦ Staging ◦ Deploy Pipeline ◦ Sanity Test
  70. @consulting gig (10 developers of various skills)

  71. • Sprints ◦ Planning ◦ Retrospective ◦ Daily Standup •

    Issues ◦ Priorities ◦ Unit Tests ◦ Code Reviews ◦ Manual Test • Automation ◦ CI ◦ Automated CRs • Environments ◦ Staging ◦ Test ◦ Deploy Pipeline
  72. Keys

  73. None
  74. None
  75. None
  76. None
  77. None
  78. None
  79. None
  80. None