Your SlideShare is downloading. ×
0
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Intro to Agile
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Intro to Agile

794

Published on

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 …

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?

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
794
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
14
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. AGILE @ADFORMby Jelena Fiodorova
  • 2. MEProgram Development ManagerWorked as Scrum Master for 3 Scrum teams (CSM)Previously worked as Project Manager (PMP)Started as a Software Developer (MCPD: Windowsdeveloper, MCTS: SQL Server) @jfiodorova
  • 3. ADFORM Founded11 YEARS in DKOffices in 12 196 countries Employees
  • 4. ADFORMSYSTEM
  • 5. Challenges
  • 6. 1 billion TRANSACTIONS / DAY 24/7 SLA 5 GEO REGIONS 140K REQUESTS / S 120 ms RESPONSE TIME
  • 7. <100% precise requirements Changing reality ERRORSMISCOMMUNICATION
  • 8. What is Agile?
  • 9. AGILE AUP TDD PRACTICIESMETHODS XP Pair Programing Scrum CI Lean Refactoring Kanban Stand-ups
  • 10. METHODS 30+ 12 10 7 3 0 AUP XP SCRUM LEAN KANBAN J*DI1. Inception 1. Coding Standards 1. Product owner 1. Eliminate waste 1. Visualize workflow2. Elaboration 2. Collective Ownership 2. Scrum master 2. Amplify learning 2. Limit Work in progress3. Construction 3. Continuous Integration 3. Team 3. Decide as late as possible 3. Measure flow4. Transition 4. On-Site Customer 4. Product backlog 4. Deliver as fast as possible5. Model 5. Pair Programming 5. Sprint backlog 5. Empower the team6. Implementation 6. Planning Game 6. Sprint burn down 6. Build integrity in7. Test 7. Refactoring 7. Sprint planning 7. See the whole8. Deployment 8. Short Releases 8. Daily scrum9. Configuration 9. Simple Design 9. Sprint reviews Management 10. Sustainable Pace 10. print retrospective10. Project Management 11. System Metaphor11. Environment 12. Test-Driven Development12. Active Stakeholder Participation13. Apply Modeling Standards14. Apply Patterns Gently15. Apply the Right Artifact(s)16. Collective Ownership17. Create Several Models in Parallel18. Create Simple Content19. Depict Models Simply20. Discard Temporary Models21. Display Models Publicly22. Formalize Contract Models23. Iterate to Another Artifact24. Model in Small Increments25. Model With Others Prescriptive | Adoptive26. Prove it With Code27. Reuse Existing Resources28. Single Source Information29. Update Only When it Hurts30. Use the Simplest Tools
  • 11. Customers Scrum Master BacklogSCRUM Stand-up grooming Product Owner Team Sprint 2 weeks Review Team’s commitment 0 Changes Planning Feature Sprint Backlog release Product Backlog Retro
  • 12. KANBANKanban board
  • 13. Agile Journey ofADFORM
  • 14. First there were challenges Then there were Agile enthusiastsWe 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 ScrumTHE BEGINNING
  • 15. Scaled to 10 teamsSome use Kanban , others - Scrum THE MOMENTUM Retrospectives of retrospectivesSustainable pace Frequent releases
  • 16. SCRUM
  • 17. KANBAN
  • 18. Pull scheduling KANBANSCRUM Limit WIP Transparency Release early and often Self-organizing teams Velocity based planning
  • 19. Product creation Manufacturing KANBANSCRUM 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. Lessons learned
  • 21. Technical sprints Separate lanes on Kanban board Ways of conductingRollout 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. THE FUTURE100% ‘vertical’ teamsCommunities of interestsNo testersNo interdependencies1 board – many teams
  • 23. Thank you

×