Appraising Agile. Copyright 2013 Broadsword Solutions Corporation

Transcription

1 Appraising Agile 0

2 1

3 2

4 3

5 Agile. You keep using that word. I do not think it means what you think it means. 4

6 Agile is not less disciplined than what we call Waterfall, stop it 5

7 6

8 Agile projects don t Create artifacts They do, so stop it 7

9 8

10 Agile teams don t use Process because it s useless They do, so stop it 9

11 10

12 Agile projects are A poor choice for appraisals They are perfect, stop. 11

13 12

14 Are you really agile? 13

15 14

16 Aspirational 15

17 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 & Interactions Working Software Customer Collaboration Responding to Change Processes & Tools Comprehensive Documentation Contract Negotiation Following a Plan * Manifesto for Agile Development copyright 2001 Ron Jeffries, Jeff Sutherland, Ken Schwaber, Alistair Cockburn, and others 16

18 REQM SP1.4 (alternative wording) Maintain bi-directional traceability between values and related methods, techniques, and behaviors Values Methods Methods Techniques/Behaviors Techniques/Behaviors 17

19 PPQA SP1.1 (alternative wording) Objectively evaluate behaviors (aka processes ) to ensure alignment with values, methods, and techniques Values Methods Methods Techniques/Behaviors Techniques/Behaviors This leads to the inescapable conclusion that Process is merely. 18

20 X Be Agile Waterfall Stand-ups, Retrospective BPUF XP 19

21 20

22 WAAAHGILE 21

23 Techniques Value-Based Risk / Issues: Agile Incrementally deal with issues and risk Values include Fail fast, iterative and incremental, collaboration, focus on people, continuously improve. Scrum Methods include Scrum, XP, Kanban, Spiral, Crystal, RUP, etc Daily Standup Techniques including Planning Poker, Daily Standup, Retrospectives, Sprint Demo, Story-time 22

24 COLLABORATIVE SYSTEM FOR GETTING WORK DONE Recursive, not linear, workflow 23

25 Appraisal Team Perspective 24

26 Sprint Planning Product owner Team Scrum Master Planning Poker Epics-User Story-Tasks Priority 25

27 Planning Poker Scrum Team Diverse Skills/Experiences User Story Based Multiple rounds Collaborative 26

28 Backlog Grooming (Story Time) Product owner Team Scrum Master Priority Update Tasks 27

29 User Stories Stories should also have: A definition of done Story points Priority Sprint Assignment (I think) Anything that delivers a service should be in a user story INCLUDING Refactoring and bug fixes 28

30 User Story Criteria 29

31 Daily Standup Team Scrum Master Issues Accomplishments Risks Blocks 30

32 Sprint Demo (Sprint Review) Customers Product owner Team Scrum Master Lessons Defects Change Requests 31

33 Test-Driven Development (TDD) Team IAll User Stories CAN be: Validation Verification 32

34 Pair Programming CAN be: Verification Validation One Coder One Navigator Should switch off 33

35 Retrospectives Team, Product Owner, Scrum Master, must record results to be effective 34

36 35

37 Information Radiators 36

38 37

39 David Lee Roth Agile Genius? A story about a Rock Star, one very groovy M&M, and Just Enough Information. 38

40 Everything can be anything A lot of things can be nothing 39

41 40

42 41

43 Planning 42

44 PP SP1.1: Establish a work breakdown structure Release Plan + Product Backlog + Epics and User Stories w/story points + Sprint Plan Work Breakdown Structure (and much more) 43

45 Daily Standup Game 44

46 Agile projects are armed with Just Enough Not Too Much Process to be great 45