Finding Our Agile Feet

Transcript

1. FINDING OUR AGILE FEET MAX WOOLF // SUBSTRAKT
2. ME Max Woolf
7. WHY DO I CARE?
8. WHY AM I HERE?
11. HOW WE WERE PART 1
13. IT’LL MAKE US AND OUR CLIENTS HAPPIER, HONEST. Me PT.1 HOW WE WERE
14. HOW CAN WE BE SURE WE’RE GETTING SOMETHING FOR OUR MONEY? Mrs. Client 1 PT.1 HOW WE WERE
15. PT.1 HOW WE WERE REELLEARNING ▸ Idea ▸ Specification ▸ Costed ▸ Designed ▸ Developed ▸ Released ▸ Phase 2… rinse and repeat. CLIENT FIRST SEES WORKING THING
16. PT.1 HOW WE WERE REELLEARNING ▸ Idea ▸ Specification ▸ Costed ▸ Designed ▸ Developed ▸ Released ▸ Phase 2… rinse and repeat. CLIENT FIRST SEES WORKING THING
17. PT.1 HOW WE WERE REELLEARNING ▸ Idea ▸ Specification ▸ Costed ▸ Designed ▸ Developed ▸ Released ▸ Phase 2… rinse and repeat. WHAT HAPPENS NOW?!
18. BUT HEY, THERE’S ALWAYS PHASE TWO, RIGHT? JEFF CRAM PT.1 HOW WE WERE http://www.cmsmyth.com/2010/06/the-proverbial-phase-two/
19. (ALMOST)
20. BUT HEY, THERE’S ALWAYS PHASE TWO, RIGHT? JEFF CRAM PT.1 HOW WE WERE http://www.cmsmyth.com/2010/06/the-proverbial-phase-two/
24. INTERLUDE
25. AGILE IS NOT A NOUN
30. I THINK WE NEED TO DO AGILE ON THIS PROJECT The manager of a failed project INTERLUDE
32. HOW WE ARE NOW PART 2
33. REELLEARNING REELLEARNING REELMUSIC MY TRAINING SITE UNIVERSITY TRAINING SITE GARDENING TUTORIAL VIDEOS DIY TRAINING VIDEOS
34. CODEBASE V10 (LATEST) SITE 1 V9 SITE 3 V8 SITE 2 V10 SITE 4 V7 (WITH A SECURITY PATCH) PLAN A MULTIPLE CODE FORKS
35. CODEBASE V10 (LATEST) SITE 1 SITE 3 SITE 2 SITE 4 PLAN B PRODUCTISE
36. ENTER: AGILE
37. PT.2 HOW WE ARE NOW THINGS WE WANTED TO DO ▸ Iteration, not incrementation ▸ Prioritisation, not specification ▸ Real-time access to development servers ▸ Code quality ▸ Code reviews ▸ Static analysis ▸ Continuous deployment ▸ TDD
39. AUTHENTICATION VIDEO UPLOADING VIDEO PLAYBACK PLAYLISTS REPORTING DRUPAL INTEGRATION INCREMENTAL USER CAN VIEW VIDEO SIGN UP SUBSCRIBE VIEW ITERATION 1 USER CAN CREATE PLAYLIST SIGN UP (V3) SUBSCRIBE (V3) CREATE PLAYLIST ITERATION 2 USER CAN FAVOURITE VIDEO SIGN UP (V2) SUBSCRIBE (V2) FAVOURITE Client feedback occurs at the end “50% DONE” ITERATIVE Client feedback
 occurs throughout CONSTANT IMPROVEMENT ADD VIDEO TO PLAYLIST
40. The user must be able to…
 The admin must be able to…
 The buttons must be green…
 The user must send an email when…
 The gremlins must not be fed after midnight…
 The background should be…
 A user should have access to…
 An administrate must have access to… … = Done SPECIFICATION
42. DEMO EARLY DEMO OFTEN
43. CODE QUALITY https://max.woolf.io/pay-your-debt/
44. PT.2 HOW WE ARE NOW ▸ Technical debt is the result of short term decision making ▸ Quick win vs. Long-term maintainability ▸ Not always conscious
45. 0 75 150 225 300 W/O TECHNICAL DEBT W/ TECHNICAL DEBT 200 100 70 100 FEATURE 2 FEATURE 1 FEATURE 1 FEATURE 2
46. PT.2 HOW WE ARE NOW CODE REVIEWS ▸ Applies to everyone ▸ One other pair of eyes ▸ NO exceptions ▸ No room for ego
47. SWALLOW YOUR PRIDE
48. PT.2 HOW WE ARE NOW CONDUCTING CODE REVIEWS ▸ Be honest, but kind. ▸ Ask questions, don’t give orders. ▸ Say ‘we’, not ‘you’. ▸ Assume everyone is intelligent. ▸ Let computers review too.
49. BE HONEST, BUT KIND
50. ASK QUESTIONS, DON’T GIVE ORDERS
51. DON’T DO THIS, IT’S RUDE.
52. HELL, YES
53. SAY “WE”, NOT “YOU”.
54. “YOU”
55. “WE”
56. ASSUME EVERYONE IS INTELLIGENT
57. NO!
58. LET COMPUTERS REVIEW TOO
59. TEST-DRIVEN DEVELOPMENT
60. IDEA CODE TEST
61. IDEA CODE
62. IDEA TEST PASSES TEST FAILS “Add one to a number” If input = 4
 expect output to be 5 def addOne(input)
 return input + 1
 end
63. CODE QUALITY CONTINUOUS DEPLOYMENT
64. LIVE ENVIRONMENT FEATURE FEATURE FEATURE FEATURE UAT ENVIRONMENT 6 MONTHS WORK
65. RELEASE EARLY, RELEASE OFTEN IS A PHILOSOPHY THAT EMPHASIZES THE IMPORTANCE OF EARLY AND FREQUENT RELEASES IN CREATING A TIGHT FEEDBACK LOOP Wikipedia PT.2 HOW WE ARE NOW https://en.wikipedia.org/wiki/Release_early,_release_often
66. EVERYTHING’S COMING UP SUBSTRAKT
67. HAPPY CLIENTS
68. PT.2 HOW WE ARE NOW HAPPY CLIENTS ▸ See something working ▸ Constantly feeding in to the development process ▸ Feel like they’re part of the process ▸ No longer a cash in, app out transaction
69. HAPPY DEVELOPERS
70. FINDING OUR AGILE FEET ▸ Iterate, don’t increment. ▸ Prioritise, don’t specify. ▸ Avoid technical debt. ▸ Code review. ▸ Deploy often. ▸ Make clients happy!
71. THANK YOU! @MAXEHMOOKAU MAX@SUBSTRAKT.COM ANY QUESTIONS?