Back To Agile Manifesto

A personal opinion post on whether Scrum or Kanban provide value or whether we should go back to the pure manifesto

Transcript

1. Yusuf Aytaş Back To Agile Manifesto Infrastructure & DevOps
2. About Me • Working for TripAdvisor • Was working for Amazon, AWS. • Worked for couple of different startups. • Applying agile practices for over 7 years. • Here to tell about my agile experience • Disclaimer: These are my own ideas! Any views or opinions on this presentation are personal and belong solely to me and do not represent those of people, institutions or organizations that I may or may not be associated.
3. Agenda • Introduction • The Drawbacks • Manifesto • An Alternative • Finale
4. Google Trends https://trends.google.com/trends/explore?q=scrum,agile https://trends.google.com/trends/explore?geo=DE&q=scrum,agile
5. Mean Tweets - Agile Edition https://twitter.com/cgosimon/status/1039362143001305089
6. Mean Tweets(cont’d) https://twitter.com/tottinge/status/1031585181373788163
7. Mean Tweets(cont’d) https://twitter.com/mattbarcomb/status/913502126285967360
8. Survey Results https://www.surveymonkey.com/results/SM-ZWN762M6L/
9. Survey Results(cont’d) https://www.surveymonkey.com/results/SM-ZWN762M6L/
10. Survey Results(cont’d) https://www.surveymonkey.com/results/SM-ZWN762M6L/
11. Terminology Estimates Sprint Backlog Standup Planning Burndown Velocity Retrospective
12. Problems • Hinders developer contribution to the product • Kills innovation by squeezing engineer’s time • Time boxing creates technical dept • Management centric, everything is managed • Assumes every engineer work the same way • Creates bureaucracy
13. Problems (Cont’d) • Brings unnecessary complexity • Prevents ownership(product owner) • Ignores dependencies • Rejects catastrophes • Only works in theory • No clear benefit for a good team
14. Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan http://agilemanifesto.org/
15. Agile Principles • Highest priority is to satisfy the customer • Deliver working software frequently • Reflect on how to become more effective • Simplicity • Self-organizing teams http://agilemanifesto.org/principles.html
16. Minimum Viable Agile • Borrowed from the concept MVP • Just enough practices to get things right • Less ceremonies • DevOps practices • Focus on delivering value • Small Teams https://www.slideshare.net/troytuttle/minimal-viable-agile
17. How to Apply – Task Board https://www.yusufaytas.com/scrum-kanban-agile/
18. How to Apply - Task Priority Customers • Customer#1: 2 • Customer#2: 3 • Customer#3: 90 Tasks: • Task#1: takes 2 days • Task#2 takes 3 days Customer#3 wants Task#2 Customer#1 and Customer#2 want Task#1 Priority for Task#1 = (2+3)/2 = 2.5 Priority for Task#2 = 90/3 = 30 https://www.yusufaytas.com/scrum-kanban-agile/
19. How to Apply - DevOps • Deployable software • Add tests: unit, integration, smoke, and etc. • Automate as much as possible: – DBA – SecOps • Create patterns to reuse
20. Finale • Agile frameworks might fail to impress • We often forget about agile manifesto • MVA – Agile with less overhead • Questions? https://www.dropbox.com/s/kg9rgdz6sj3jqas/code.talks.pptx