layout: true name: inverse class: center, middle, inverse .footnote[ \#agileindy16 ### [@schmonz](https://twitter.com/schmonz) ] --- template: inverse # Shoestring Agility in a Velcro Organization ## Amitai Schlair ### AgileIndy 2016/04/12 ??? Press 'C' to clone and 'P' to show these presenter notes in the clone! --- ## 1. Keeping my job ??? - Graduated, music, 2009, needed a job, got hired - what it was like, what _I_ was like - `proid disable`, broke production - what I said to Bill --- #### 1. Keeping my job ## 2. A last-minute feature ??? - challenges: problem domain, legacy code, out of practice, complex environment, no tests - advantages: brilliant architecture (knc, SSP), Roland and Bill were still around - motivations: fear (don't screw up), value (create a client for GUI users) - "the SSP 2 port", tiny mechanical changes, code review, new functional tests, migration plan - so what!?! - delivered `additional_environments` on the same day - what Bill said --- #### 1. Keeping my job #### 2. A last-minute feature ## 3. Deadline pressure ??? - first non-Unix platform: mainframe (for GUI users) - explicit (hardcoded) and implicit (invisible) assumptions about Unix platform - deadline: 1.5 weeks - work from home, strategic napping, status update every night at midnight - came in on Thursday to pair-test the new rules with Robert - one small runtime problem in prod, obvious when it happened, fixed on the fly - better than we deserved - one could-have-been-huge problem in prod, months later, that was not huge - they loved it and made me product manager --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure ## 4. Continual delivery ??? - monthly releases, we were confident, ops wasn't really - the Loic story - paired to deliver his code --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure #### 4. Continual delivery ## 5. Fail-safe ??? - 3+ years of monthly releases - only one time we had to roll back - we knew it was extra likely, so we prepared extra well - how did that even happen? why couldn't we test well beforehand? --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure #### 4. Continual delivery #### 5. Fail-safe ## 6. A big project ??? - the Sybase story - maybe impossible; not impossible - Scrum, points, velocity; no sprints - upstream team got in our way; fixed - delivered with minutes to spare --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure #### 4. Continual delivery #### 5. Fail-safe #### 6. A big project ## 7. Win-win ??? - the Dan and Murray story - they hit their deadline too --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure #### 4. Continual delivery #### 5. Fail-safe #### 6. A big project #### 7. Win-win ## 8. No secret ??? - monthly whatever's ready looks like not discipline - deadlines being hit looks like discipline - how were we doing it with so little budget, no QA? - discipline and skill - disappointing answer?!?! - Babbage quote --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure #### 4. Continual delivery #### 5. Fail-safe #### 6. A big project #### 7. Win-win #### 8. No secret ## 9. Thwarted ??? - wanted to try BDD - got it all going - was gonna borrow a tester - new management, blocked --- #### 1. Keeping my job #### 2. A last-minute feature #### 3. Deadline pressure #### 4. Continual delivery #### 5. Fail-safe #### 6. A big project #### 7. Win-win #### 8. No secret #### 9. Thwarted ## 10. Testing acceptance ??? - people who don't know software development don't know how to see cost and risk - don't know how to see that that matters, a lot - we made half a humane workplace - I changed careers --- template: inverse # Shoestring Agility in a Velcro Organization ## Amitai Schlair ### AgileIndy 2016/04/12 ## [schmonz.com](https://schmonz.com) ## [ai3m.co](http://ai3m.co)