Scrum und Craftsmanship
1 like516 views
This document summarizes a presentation on software craftsmanship and Scrum. The presentation discusses challenges with technical debt and code quality. It shows examples of messy code and emphasizes clean code practices. It also addresses challenges that can occur near the end of a sprint and how to visualize work. The presentation promotes practices like feedback loops, continuous improvement, code reviews, coding dojos and certifications to strengthen skills and culture.
Scrum und Craftsmanship
- 1. Software Craftsmanship und Scrum oder Auf der Suche nach dem Qualitäter* XP-Days Germany 2011 Stefan Roock stefan.roock@it-agile.de Twitter: @StefanRoock *Danke an Arne Roock für den Untertitel Donnerstag, 17. November 11
- 2. Kennen Sie das? public float runde(float wert) { // irgendjemand müsste hier mal aufräumen wert = wert * 100; float d = wert - (int) wert; if (d == 0.0f) { return wert / 100; } else if (d > 0) { return (wert - d) / 100; } else if (d < 0) { return (wert + d) / 100; } return 0; // kann eigentlich nicht passieren } Donnerstag, 17. November 11
- 3. Und das? Donnerstag, 17. November 11
- 4. Und das? S.O.L.I.D. Donnerstag, 17. November 11
- 5. Hilft es? Donnerstag, 17. November 11
- 6. Kurz vor Sprintende ToDo Doing Done Donnerstag, 17. November 11
- 7. Gerade noch geschafft ToDo Doing Done Donnerstag, 17. November 11
- 8. Donnerstag, 17. November 11
- 9. Technische Schuld Donnerstag, 17. November 11
- 10. Velocity: Velocity: z.B. 20 z.B. 15 Storypoints Storypoints Donnerstag, 17. November 11
- 11. Mit einem Wort: Katastrophe Donnerstag, 17. November 11
- 12. Dann lasst uns das mal visualisieren. ToDo Doing Done ToDo Doing Done Wir sind fertig. Eigentlich müsste man mal ... Und jetzt? Donnerstag, 17. November 11
- 13. Culture Eats Strategy for Breakfast Donnerstag, 17. November 11
- 15. Manifesto for Software Craftsmanship Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships That is, in pursuit of the items on the left we have found the items on the right to be indispensable. http://manifesto.softwarecraftsmanship.org Donnerstag, 17. November 11
- 16. Clean Code Donnerstag, 17. November 11
- 17. ADAPT creating Awareness increasing Desire developing Ability Promoting successes Transferring the implications of X to the rest of the organization Donnerstag, 17. November 11
- 18. Weinbergs Strategie Donnerstag, 17. November 11
- 19. Feedbackschleifen? 1. Wartungsteams 2. Team je Projekt 3. Fluktuationen im Team 4. Übergaben und Vorgaben (z.B. Architekten machen die Architektur) 5. ... Donnerstag, 17. November 11
- 20. „I have been hailed as one of the leading exponents of these so-called design methods. I am very sorry that this has happened, and want to state, publicly, that I reject the whole idea of design methods as a subject of study, since I think it is absurd to separate the study of designing from the practice of design. In fact, people who study design methods without also practicing design are almost always frustrated designers who have no sap in them, who have lost, or never had, the urge to shape things. Such a person will never be able to say anything sensible about 'how' to shape things either." Christopher Alexander: „Notes on the Synthesis of Form“, 1971 preface. Donnerstag, 17. November 11
- 21. Single Piece Flow im Sprint WiP-Limit: 1 Story Doing Done Donnerstag, 17. November 11
- 22. Quattro Stagioni 09:00 11:00 14:00 Arlo Belshee: „Promiscuous Pairing & Beginners Mind“ 16:00 Donnerstag, 17. November 11
- 23. Coding Dojos und Code Katas Donnerstag, 17. November 11
- 24. Certified Scrum Developer http://www.it-agile.de/csd.html Pichler, Roock (Hrsg.): „Agile Entwicklungspraktiken mit Scrum“ Donnerstag, 17. November 11
- 25. Danke für die Aufmerksamkeit Donnerstag, 17. November 11