Successfully reported this slideshow.

Intro to Agile

4

Share

Upcoming SlideShare
Scrum & Agile - imobilemagic
Scrum & Agile - imobilemagic
Loading in …3
×
1 of 23
1 of 23

Intro to Agile

4

Share

Download to read offline

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?

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?

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Intro to Agile

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

×