Agility? What for? And how? > Warm-up Session Agile Tour Vienna 2014

Transcription

1 Agility? What for? And how? > Warm-up Session Agile Tour Vienna 2014

2 Agenda Agile Software Development: reasons & goals Scrum in a nutshell Kanban in a nutshell Agility: prerequisites, limits and corporate culture CSS GmbH November

3 The Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more , Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas CSS GmbH November

4 The Cone of Uncertainty (also: Funnel Curve) At the start of the project, uncertainty concerning requirements is 16 times higher than at the end of the project (Boehm). After 30% of the project duration have elapsed, this uncertainty is reduced from 16 times to 1.5 times (Boehm). CSS GmbH November

5 The classical project management approach B was specified and sold in the beginning B was 100% implemented as planned Source: Mitch Lacey 2011 But C would have been the solution which the client really needed CSS GmbH November

6 And now here is the agile approach B has been planned. And it has been specified how to deal with changes. Here they found out that B should look more like C... So they decided to go for C! The B - detour has been skipped. Source: Mitch Lacey 2011 CSS GmbH November

7 What do you read? IUMRING TQ GQNGIUSIQNS Source: Mike Rother CSS GmbH November

8 IUMRING TQ GQNGIUSIQNS Our brain automatically fills in blanks, instead of saying to us Sorry, I don t know yet Source: Mike Rother

9 Don t forget about uncertainty! Sometimes we have to look at things we don t want to see But it s better to have thunderstorms during a project than having a hurricane in the end An agile, iterative approach forces everybody to check continuously if we are on the right way - even the client CSS GmbH November

10 Scrum in a nutshell How does Scrum implement agile principles? 13

11 The only thing Scrum can gurantee is, that latest after 30 days the shit will appear from underneath the carpet. I help people build software in 30 days or less. Tell us the most important stuff you have, and we ll give you as much of that as we can at the end of 30 days. Ken Schwaber 14

12 2 Lists 1 Goal 3 Core Roles 4 Core Meetings Working Software Product Backlog Product Owner Sprint Planning Sprint Backlog Scrum Master Daily Scrum Scrum Team [Consultants] Sprint Review / Demo Meeting Retrospective Daily Scrum daily Sprint Planning Sprint (1)/2/3/4 Weeks Sprint Review/Demo Client Product Backlog Sprint Backlog Sprint Retrospective Working Software CSS GmbH November 2014 Source: Mike Cohn, modified

13 Kanban in a nutshell To which extend does Kanban go with Agile? 25

14 Source: David J. Anderson Source: The Agile Pirat 27

15 Dr. W. Edwards Deming You don t have to change, survival is optional 28

16 Kanban briefly defined It s the Start with what you do know Method Stop starting, start finishing Visualize Limit Work in Process Manage Flow Source: David J. Anderson CSS GmbH November Principles & 6 Core Practices Evolutionary Change 29

17 Kanban Agendas Survivability Service-orientation Sustainability Resilience/anti-fragility Evolutionary capability Fitness criteria metrics Workflow Service level expectations Relief from overburdening Lead the business Decide with confidence Engage with people 30

18 Agile prerequisites & limits and an Agile Corporate Culture 36

19 Organization with combined team-structure Product Owner 1 Product Owner 2 Chief Product Owner Product Backlog Feature Team A Feature Team B Feature Team C Feature Team D Product Owner Team Component Team X Product Owner 3 Component Team Y CSS GmbH November

20 It s all about people! Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. The best architectures, requirements, and designs emerge from selforganizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. (4 th, 5 th, 6 th, 11 th & 10 th Principle of Agile Software; CSS GmbH November

21 Agility is all about Values and Principles Shifting from a plan-driven to a value-driven project management Shifting from a formerly task- and work-package oriented approach to focusing on how to reach our goals (= the client s goals!) Shifting the focus from just writing about features to discussing and understanding functionality Source: Pawel Brodzinski Team-work and discussions help us to understand the client s needs and build the perfect solution CSS GmbH Juni

22 Great! Super! Fantastic! Let s work agile forever! CSS GmbH November 2014

23 CONTACT Dipl.-Ing.(FH) Sven Schweiger CSS Computer-Systems-Support GmbH Landstraßer Hauptstraße 167, 1030 Wien Phone Internet: Dipl.-Ing. Mike Leber Agile Experts e.u. Joseph-Lister-Gasse 31C/9, 1130 Wien Phone Internet: Fotos: Gert Krautbauer / Sven Schweiger / München / Wien