Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Agile Software Engineering Techniques: The Missing Link in Large-Scale Lean Product Development

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige

Hier ansehen

1 von 21 Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Ähnlich wie Agile Software Engineering Techniques: The Missing Link in Large-Scale Lean Product Development (20)

Anzeige

Weitere von Tobias Schimmer (19)

Agile Software Engineering Techniques: The Missing Link in Large-Scale Lean Product Development

  1. 1. Agile Software Engineering Techniques: The Missing Link in Large Scale Lean Product Development Alexander Scheerer, Christoph Schmidt, Dr. Tobias Hildenbrand Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 1
  2. 2. Agenda  Introduction: Lean and agile development at SAP  How do teams adopt Agile Software Engineering Techniques (ASET)  The Research Process  Adoption Patterns  Combining ASET in a lean and scrum context  Outlook: Combining Design and Development  Summary and Conclusion Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 2
  3. 3. Introduction: Why lean and agile development at SAP? Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 3
  4. 4. The previous development process resembled a stage-gate approach Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 4
  5. 5. The current process follows a Lean Product Development Flow approach How to efficiently deliver innovative enterprise software to customers? Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 5
  6. 6. How do Scrum teams adopt Agile Software Engineering Techniques (ASET)? Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 6
  7. 7. ASET as the missing link to effectively implement lean development principles in large scale software companies Pair programming, Specific test-driven development, agile techniques continuous integration, ASET (Beck 2001) refactoring Teams with Scrum master, Agile method Scrum product owner, developers and as process framework an associated manager for (Schwaber & Beedle 2001) people development Lean Principles Eliminate waste, build quality in, Lean principles learn constantly, deliver fast, (Poppendieck 2003) engage everyone, Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz keep getting better 7
  8. 8. Research Process Case Study Team Team 1 week 3 weeks 1 2 Training Coaching Team Team 3 4 Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 8
  9. 9. A great majority of the respondents generally confirmed that they enjoyed the practices Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 9
  10. 10. Two groups of adopters emerged within our study: High vs. Low Adopters Low Adopters High Adopters Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 10
  11. 11. Heterogeneous Adoption Patterns Variations in Pair Programming Adoption Intensity People Process • Continuous value generation • Broader knowledge base • Fast feedback • Quality awareness Advantages • Avoidance of trivial errors • Collaboration • Intra-team discussion culture • Team cohesion • Inter-personal conflicts • Stressful Disadvantages • Lower development speed • Synchronization of work schedules Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 12
  12. 12. Heterogeneous Adoption Patterns Variations in Test-driven Development Adoption Intensity People Process • Increased focus on current task • Increase of self-confidence • Large test framework Advantages through continuous • Maintainability increase feedback • Increase of structuredness • Interrupts free flow • Effort for user interface tasks Disadvantages of thoughts disproportionately higher • Painful transition Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 14
  13. 13. Outlook: Combining Design and Development Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 16
  14. 14. Innovation = Desirability + Feasibility + Viability Successful Business Model Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 17
  15. 15. An Analytic Approach Doesn‘t Work for Enterprise Software Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 18
  16. 16. Development Teams Need to Think Like Designers Sometimes… Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 19
  17. 17. However, Design Thinking is No Rocket Science! Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 20
  18. 18. Combining Design and Development: Lean and Design Thinking Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 21
  19. 19. What are the 3 Things to Remember? Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 22
  20. 20. Summary and Conclusion 1) Agile Software Engineering techniques help teams to build enterprise solutions efficiently 2) In a large-scale Lean implementation ASET brings agile practices into daily business 3) Design Thinking helps teams to find problems worth solving and create innovative solutions Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 23
  21. 21. Thank You Feel free to approach us today or any after:  Alexander Scheerer – scheerer@uni-mannheim.de  Christoph Schmidt – christoph.schmidt@uni-mannheim.de  Dr. Tobias Hildenbrand – tobias.hildenbrand@sap.com Scheerer, Schmidt, Heinzl, Hildenbrand, Voelz 24

×