From Adoption to Transition

Size: px

Start display at page:

Download "From Adoption to Transition"

Juliana Moody
6 years ago
Views:

1 From Adoption to Transition Gino Marckx Director Agile Practice, Thoughtcorp Agile+

cba Resident on Earth - http://www.flickr.

2 cba Resident on Earth - Once upon a time...

3 Let s try this new thing called Agile!

cba RambergMediaImages - http://www.flickr.

4 cba RambergMediaImages - cb Richard Smith -

5 Faster Better Cheaper cba RambergMediaImages - cb Richard Smith -

6 1. Support Agile Manifesto

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.

7 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 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice.

8 Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 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

9 cb Matt Hutchinson -

10 1. Support Agile Manifesto 2. Hire Agile Champion

11 cba paddynapper -

12 1. Support Agile Manifesto 2. Hire Agile Champion 3. Train Team Members

Retrospectives cb Dana Beveridge - http://www.flickr.

13 Daily Standups Test Driven Development Continuous Integration Pair Programming Self-Organizing Team Product Iterations Backlog Planning Game Sprint Review Retrospectives cb Dana Beveridge - cb Jonathan Rubio -

14 Certified Train Team Members cba Andrew Schwegler -

15 1. Support Agile Manifesto 2. Hire Agile Champion 3. Train Team Members 4. Be Agile

16 cba RambergMediaImages - cb Richard Smith -

17 Yes, but...

Specifications Initial Estimate and Schedule Active Stakeholder

20 Practices Tried and Abandoned Top 8 (out of 30) Pair Programming Burndown Tracking Potentially Shippable Software Daily Standups Executable Specifications Initial Estimate and Schedule Active Stakeholder Participation Retrospectives Copyright 2009 Scott W. Ambler -

21 Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need,

22 1. Support Agile Manifesto 2. Hire Agile Coach 3. Train Team Members 4. Be Agile

23 Agile Transition Adoption

24 1. Support Agile Manifesto 2. Hire Agile Champion 3. Train Team Members 4. Be Agile

25 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 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice.

26 Requirements Product Vision / Vision Statement Product Backlog User Stories Use Cases Usage Scenarios Personas Planning Poker Requirement Prioritization User Stories By Jurgen Appelo - Design Architectural Spikes / Spike Solutions Domain Driven Design Emergent Design / Evolutionary Design CRC Cards Design by Contract System Metaphor Construction Coding Style / Coding Guidelines / Coding Standard Test Driven Development Behavior Driven Development Pair-Programming / Pairing Refactoring Collective Code Ownership Daily Builds / Automated Builds / Ten-Minute Builds Continuous Integration Code Reviews / Peer Reviews Software Metrics / Code Metrics & Analysis Source Control / Version Control Issue Tracking / Bug Tracking Configuration Management Frequent Delivery / Frequent Releases Testing Unit Testing Smoke Testing / Build Verification Test Integration Testing System Testing Exploratory Testing Test Automation Storytesting / Acceptance Criteria / Acceptance Testing Process Timeboxing / Fixed Sprints / Fixed Iteration Length Release Planning Iteration Planning / Planning Game / Sprint Planning Sprint Backlog Task Board Definition of Done / Done Done Daily Stand-up Meeting / Daily Scrum Velocity Sprint Review / Iteration Demo Value Stream Mapping Root Cause Analysis / 5 Whys Burn Down Charts / Burn Up Charts Big Visible Charts / Information Radiators Retrospective / Reflection Workshop Organization Small Team Cross-Functional Team Self-Organizing Team / Scrum Team Colocated Team / Sitting Together / Common Workspace On-Site Customer / Product Owner Scrum Master Sustainable Pace Move People Around Scrum of Scrums Emergent Design/Evolutionary Design Collective Code Ownership Test Automation Retrospective Self-Organizing Team

27 User Stories Emergent Design/ Evolutionary Design Self-Organizing Team Retrospectives Test Automation Collective Code Ownership

28 A Small Piece of Functionality from the End-user s Perspective

29 Card Conversation Confirmation

30 Invitation to a Conversation Alistair Cockburn

31 Conversation User Stories Emergent Design/ Evolutionary Design Self-Organizing Team Retrospectives Test Automation Collective Code Ownership

32 Design for the Current Solution, Not for Future Requirements

33 Keep It Simple and Stupid

34 You Ain t Gonna Need It

35 Conversation User Stories Commit to Team Results Emergent Design/ Evolutionary Design Self-Organizing Team Retrospectives Test Automation Collective Code Ownership

36 No Silos

37 Everyone Can Contribute to Any Part of the Project

38 Conversation User Stories Commit to Team Results Emergent Design/ Evolutionary Design Self-Organizing Team Retrospectives Test Automation Shared Ownership Collective Code Ownership

39 Testing Programming

40 cba Damien Pollet -

41 Conversation User Stories Commit to Team Results Emergent Design/ Evolutionary Design Self-Organizing Team Retrospectives Shared Ownership Collective Code Ownership Collaboration Test Automation

42 Inspect and Learn from the Past cb Dana Beveridge -

43 Regardless of what we discover today, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand. Norm Kerth

44 Conversation User Stories Commit to Team Results Emergent Design/ Evolutionary Design Self-Organizing Team Trust Retrospectives Shared Ownership Collective Code Ownership Collaboration Test Automation

45 Self-organizing = Motivated

46 Copyright by RSA Animate -

47 Conversation User Stories Commit to Team Results Emergent Design/ Evolutionary Design Motivation Self-Organizing Team Trust Retrospectives Shared Ownership Collective Code Ownership Collaboration Test Automation

48 User Stories Emergent Design/ Evolutionary Design Collective Code Ownership Test Automation Retrospectives Self-Organizing Team Conversation Commit to Team Results Shared Ownership Collaboration Trust Motivation Team Dynamics

49 team Pronunciation: /tiːm/ noun [treated as singular or plural] a group of players forming one side in a competitive game or sport:the village cricket team his team played well [as modifier] :team members two or more people working together:a team of researchers two or more animals, especially horses, in harness together to pull a vehicle:the abbey s wagon and a team of horses are gone verb 1 [no object] (team up) come together as a team to achieve a common goal:he teamed up with the band to produce the disc 2 [with object] (usually team something with) match or coordinate a garment with (another):a pinstripe suit teamed with a crisp white shirt 3 [with object] harness (animals, especially horses) together to pull a vehicle:the horses are teamed in pairs Oxford Dictionaries

50 It s About How We Work Together to Achieve a Common Goal

51 cba James DiBianco -

53 I want my idea to be chosen That is a bad idea I don t understand it Will it help me? What do they mean by that?

54 Signal Noise

55 cb Michiel Jelijs -

56 Some Tips...

57 Decision Making

58 1. Find out what you agree on 2. Resolve the differences cb Sarah -

59 Emotional Context

60 cbde Gino Marckx - Native Child and Family Services of Toronto 14th Annual Community Pow Wow

61 Feedback

62 cba Nick McPhee -

63 So...

64 Agile is Not About Processes and Techniques

65 It s About How We Work Together to Achieve a Common Goal It s About How You Work Together to Achieve a Common Goal cb Vestman -

66 Thank You! Gino Marckx Director Agile Practice, Thoughtcorp Agile+

Agile Development Methods: Philosophy and Practice. CSCE 315 Programming Studio, Fall 2017 Tanzir Ahmed

Agile Development Methods: Philosophy and Practice CSCE 315 Programming Studio, Fall 2017 Tanzir Ahmed History of Agile Methods Particularly in 1990s, some developers reacted against traditional heavyweight