Intro to Agile

Let's talk about Agile not because it is popular, new and amazing, but because it is a software development methodology that just works. What are the basics of Agile? How does it work? What issues you may face while adopting Agile?

Transcript

1. AGILE @ADFORM by Jelena Fiodorova
2. ME Program Development Manager Worked as Scrum Master for 3 Scrum teams (CSM) Previously worked as Project Manager (PMP) Started as a Software Developer (MCPD: Windows developer, MCTS: SQL Server) @jfiodorova
3. ADFORM 196 Employees Offices in 12 countries YEARS 11 Founded in DK
4. ADFORM SYSTEM
5. Challenges
6. 1 billion REQUESTS / S RESPONSE TIME 120 ms 140K TRANSACTIONS / DAY SLA 24/7 GEO REGIONS 5
7. ERRORS MISCOMMUNICATION <100% precise requirements Changing reality
8. What is Agile?
9. AUP XP Scrum Lean Kanban AGILE TDD Pair Programing CI Refactoring Stand-ups PRACTICIES METHODS
10. METHODS LEAN KANBAN SCRUM XP J*DI 1. Inception 2. Elaboration 3. Construction 4. Transition 5. Model 6. Implementation 7. Test 8. Deployment 9. Configuration Management 10. Project Management 11. Environment 12. Active Stakeholder Participation 13. Apply Modeling Standards 14. Apply Patterns Gently 15. Apply the Right Artifact(s) 16. Collective Ownership 17. Create Several Models in Parallel 18. Create Simple Content 19. Depict Models Simply 20. Discard Temporary Models 21. Display Models Publicly 22. Formalize Contract Models 23. Iterate to Another Artifact 24. Model in Small Increments 25. Model With Others 26. Prove it With Code 27. Reuse Existing Resources 28. Single Source Information 29. Update Only When it Hurts 30. Use the Simplest Tools 1. Product owner 2. Scrum master 3. Team 4. Product backlog 5. Sprint backlog 6. Sprint burn down 7. Sprint planning 8. Daily scrum 9. Sprint reviews 10. print retrospective 1. Eliminate waste 2. Amplify learning 3. Decide as late as possible 4. Deliver as fast as possible 5. Empower the team 6. Build integrity in 7. See the whole 1. Visualize workflow 2. Limit Work in progress 3. Measure flow 1. Coding Standards 2. Collective Ownership 3. Continuous Integration 4. On-Site Customer 5. Pair Programming 6. Planning Game 7. Refactoring 8. Short Releases 9. Simple Design 10. Sustainable Pace 11. System Metaphor 12. Test-Driven Development AUP 12 10 7 3 0 30+ Prescriptive | Adoptive
11. SCRUM Customers Product Backlog Team’s commitment Planning Sprint Backlog Backlog grooming 0 Changes Sprint 2 weeks Review Stand-up Feature release Scrum Master Team Product Owner Retro
12. KANBAN Kanban board
13. Agile Journey of ADFORM
14. THE BEGINNING Then there were Agile enthusiasts We set up the vision Then arranged Scrum trainings Divided the ADFORM System into several small products Dedicated teams to products First there were challenges Established Pilot team …and got busy with Scrum
15. THE MOMENTUM Scaled to 10 teams Some use , others - Kanban Scrum Retrospectives of retrospectives Sustainable pace Frequent releases
16. SCRUM
17. KANBAN
18. SCRUM KANBAN Pull scheduling Limit WIP Transparency Release early and often Self-organizing teams Velocity based planning
19. SCRUM KANBAN vs Product creation Rhythm Frozen backlog 1 backlog : 1 team Any size tasks Board restarts Manufacturing Flow Event-driven 1 board : n teams Similar sized tasks Persistent board
20. Lessons learned
21. Ways of conducting Retro of Retro: 1. Overview of teams retro 2. Knowledge sharing 3. Lectures 4. Cross-teams discussions 5. Workshops 6. Open space discussions Rollout planning Technical sprints Temporary teams Technical backlog Feature teams Separate lanes on Kanban board
22. THE FUTURE 100% ‘vertical’ teams Communities of interests No testers No interdependencies 1 board – many teams
23. Thank you