WORK SMART, NOT HARD. Molly

Transcription

1 WORK SMART, NOT HARD Molly

2 February 11-13,

3 3

4 This is not being agile 3

5 This is not being agile This is Agile 3

6 Agile Fever is a condition that robs otherwise rational people of their common sense in regard to adoption and application of Agile based processes for developing software. Alex Bell, Death by Agile Fever 4

7 In 22 years, we ve developed a lot of strong opinions 5

8 6

9 1 iphone application 3 months of development 9 developers 7

10 0 iteration planning meetings 0 story estimates abnormal user stories manual functional tests 8

11 9

12 Analyze Build Test 10

13 2003 Design Analyze Build Test 10

14 Design Analyze Build Test Deploy Test

15 Design Analyze Build Test Deploy Test

16 Design Analyze Build Test Deploy Test

17 Regardless of what we discover, 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. 11

18 Regardless of what we discover, 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. Start Doing Keep Doing Stop Doing Less Of More Of 11

19 Regardless of what we discover, 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. Start Doing Keep Doing Stop Doing 11

20 KEEP DOING 12

21 Responding to change over following a plan 13

22 RESPONDING TO CHANGE Responding to change over having a plan start keep stop 14

23 RESPONDING TO CHANGE Responding to change over having a plan start keep stop 14

24 RESPONDING TO CHANGE It s become easier to Responding to change over having a plan start keep stop 15

25 RESPONDING TO CHANGE start keep stop 16

26 RESPONDING TO CHANGE: OSS start keep stop 17

27 BUILDING WORKING SOFTWARE You understand what change to respond to faster, when in production Sometimes that change will be to move away from a technology - such as services in a PaaS start keep stop 18

28 BUILDING WORKING SOFTWARE You understand what change to respond to faster, when in production Sometimes that change will be to move away from a technology - such as services in a PaaS keep start stop Replaceability as a first class ility Brandon Byars 18

29 MICROSERVICES start keep stop 19

30 MICROSERVICES keep start stop Microservices architectures are the first new architectural pattern since continuous delivery was coined 19

31 OBLIGATORY WARNING LABEL start keep stop 20

32 START DOING 21

33 Responding to change over following a plan 22

34 HAVE A PLAN start keep stop 23

35 HAVE A PLAN [THAT CAN CHANGE] start keep stop 23

36 HAVE A PLAN Non-Negotiable High Priority Low Priority N/A Security Usability Configurability Integratability Privacy Accessibility Portability Data Protection Personalization Help App Reporting Reuse Availability Scalability (User guides) Documentation Maintainability Recoverability Archiving Continuity (DR) Data Integrity Interoperability Upgradability Auditability Compatibility Authorization Performance Localization Reliability / Safety Mult. Env. Support Installability Authentication Supportability Operational Robustness Extensibility keep start stop (example) Capture & implement cross functional requirements 24

37 HAVE A PLAN CIS Benchmark Tests Build what you can into your pipeline start keep stop 25

38 Customer collaboration over contract negotiation 26

39 CUSTOMER COLLABORATION start keep stop 27

40 CUSTOMER COLLABORATION Co-product owners start keep stop 27

41 CUSTOMER COLLABORATION Co-product owners Technical & Functionality start keep stop 27

42 CUSTOMER COLLABORATION Co-product owners Technical & Functionality Helps prioritize a production ready product start keep stop 27

43 CUSTOMER COLLABORATION Co-product owners Technical & Functionality Helps prioritize a production ready product Redefine the customer in customer collaboration start keep stop 27

44 CUSTOMER COLLABORATION Prefer BASE to ACID as your system becomes more distributed start keep stop 28

45 CUSTOMER COLLABORATION A few minutes later Prefer BASE to ACID as your system becomes more distributed start keep stop 28

46 Working software over comprehensive documentation 29

47 Build the right thing and build the thing right 30

48 MEASURE: USING DATA How your users are using the application matters Tools can help you digest the information and give the right people access to this data It can help you measure against your success criteria start keep stop 31

49 MEASURE: USING DATA start keep stop 32

50 MEASURE: USING DATA The most common question here is: When will X be complete? start keep stop 32

51 MEASURE: USING [THE RIGHT] DATA Order Search Track Return start keep stop 33

52 MEASURE: USING [THE RIGHT] DATA Orders Placed start keep stop v1.0 v1.02 v1.13 v2.0 Release 34

53 STOP DOING 35

54 Working software over comprehensive documentation 36

55 WORKING SOFTWARE == FUNCTIONALITY ONLY urgency functionality cross functional requirements, technical debt, etc. importance start keep stop 37

56 Responding to change over following a plan 38

57 SLOW ABILITY TO RESPOND What does your testing pyramid look like? Some practices that have become known as Agile are slowing down response times start keep stop 39

58 SLOW ABILITY TO RESPOND start keep stop 40

59 SLOW ABILITY TO RESPOND start keep stop 41

60 The consequences of Agile Fever have contributed to misapplication, misuse, and misunderstanding of Agile based software development processes with costly impact. Alex Bell, Death by Agile Fever 42

61 Individuals and Interactions over processes and tools 43

62 1 iphone application 3 months of development 9 developers 44

63 many conversations about user experience hundreds of unit and integration tests small team of people in the same space clear visibility into value created 45

64 We are uncovering better ways of developing software by 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. 46

65 Individuals and Interactions over processes and tools 47

66 Working software in production over comprehensive documentation 48

67 Complete customer collaboration over contract negotiation 49

68 Respond & measure change over following a plan 50

69 Respond & measure change while following a plan 50

70 BEING AGILE Over Agile 51

71 THANKS Molly