Scrum and Kanban 101

Transcription

1 Scrum and Kanban 101

2

3 What are your expectations

4 What are the differences between Agile and Traditional?

5 What do you know about Agile

6 Two approaches to control any process: Defined Empirical Plan Act Do Check

7 Defined or empirical? Software development Car production 7

8 Spectrum of process complexity Research Software development Production

9 Two approaches to optimization: Sub-optimization System optimization

10 Spectrum of process complexity Research Software development Production

11 Two approaches to management: Command and control Self-management

12 Spectrum of process complexity Research Software development Production

13 Paper Airplane Factory

14 Authors Flavio Steffens de Castro, author of Rafael Prikladnicki, professor from PUCRS and agile coach and trainer

15 Basic rules Split into teams Go! We will build paper airplanes Iterations and re-planning of 2 min each Line production concept The plane starts in an edge and ends in the other The engineering of production is a team decision Teams are not allow to stock sheets for production The product (airplanes) MUST conform with the scope defined If a product doesn t pass the final quality review, it will not be accepted in the iteration Products that are unfinished can be used in the next iteration to be complete Every team will represent a factory (with logo) 1 2

16 The beginning The Air Force is planning to buy some new airplanes The agent of the Air Force (me) contacted your factories to check for your proposals I want to know how many airplanes you can deliver in TWO minutes Since I am very impatient, you have ONE minute to discuss and inform the number of airplanes you produce in a TWO minute iteration Start!

17 Proposal analysis The Air Force liked the estimates and will open a competition You will have TWO minutes to produce a prototype. The scope is: Must have 12 windows Must have a fly cabin Must have the logotype of your company on both wings Must fly across table (~2 meters) The prototype will be shown to the group. Start!

18 What the Air Force really wants

19 Instructions

20 Preparations The winner : Deliver more airplanes Deliver the quantity as promised 4 iterations of 2 minutes to produce the planes 2 minutes at the end of each iteration to check and act about your production line, to increase productivity. You will give the estimates in the beginning of each iteration.

21 Roles Client (me) Gives the scope and approves each produced airplane Team leader The leader can t build the airplanes. The leader should care the team, help to check/act the process, remove impediments and get the material. Team Produce the airplanes and check/act the process. Select a Team leader!

22 Iterations Act/check time (2 minutes): Number of planned to finish planes Agree/improve work process Start! Work time (2 minutes): Number of planned to make planes Produce the planes Start! Show time Count planes (done) Repeat

23 And the winner is..

24 Retrospectives Did you get what the client wanted in the beginning? Did the prototype help? Why? Did the estimates got better with time? Why? Was the concept of inspect/adapt useful? What was the most useful? Did team leader help? How? Who made decisions? What is better for you and the client: Deliver all the airplanes in 10 minutes? Deliver a % of airplanes each 2 minutes?

25 Congratulations! You had just lived an Agile Process! The teams became motivated and self-managed The team leader worked for the team The work process became more efficient and organized in iterations The communication became strong and powerful You inspected and adapted, through iterations!

26 Do you have any questions

27 Agile manifesto

28 Individuals and interactions over processes and tools

29 Working software over contract negotiation

30 Customer collaboration over comprehensive documentation

31 Responding to change over following a plan

32 Do you have any questions

33 Scrum

34 Scrum

35 5 principles 1. Deliver every sprint 2. Team decides everything 3. Inspect and adopt everyday 4. Define chief impediments removal 5. Priorities come from one person

36 3 roles 1. Scrum master 2. Product owner 3. Team

37 Scrum master Responsible for the success of Scrum 1. Enforces the Scrum rules 2. Facilitates all Scrum meetings 3. Shields the team from external interference 4. Leads the team to be self-organized and to continuously improve 5. Coaches and supports PO 6. Removes impediments

38 Product owner Responsible for the product success 1. Envisions the product 2. Is the only one responsible for Product backlog 3. Is responsible for the product s profitability 4. Decides on release date and content 5. Accepts or rejects work results 6. Collaborates with both the team and stakeholders

39 Team Responsible for delivering product 1. Self-organizing 2. Cross-functional with no roles 3. 7± 2 members 4. Responsible for meeting their commitments 5. Authority to do whatever is needed to meet commitments

40 4 meetings 1. Sprint planning 2. Daily scrum 3. Sprint review 4. Sprint Retrospectives 5. Backlog grooming

41 Sprint planning Define what to do 1. PO presents top priority Product Backlog items 2. Team selects the amount of Backlog for the upcoming Sprint 3. Acceptance criteria are negotiated and clarified 4. Sprint Goal is defined

42 Sprint planning Define how to do 1. Team participates while PO s available 2. Team breaks items into tasks to form the Sprint Backlog 3. Involves detailed design 4. Team makes commitment for the Sprint

43 Daily scrum Inspection and adaption for the sprint 1. What have you completed since last meeting? 2. What will you complete before next meeting? 3. What is in your way?

44 Sprint review Inspection and adaption for product 1. Team presents the Done work and Undone work 2. Get feedback from the Product Owner and Stakeholders 3. Update Product Backlog and release Burndown chart

45 Sprint retrospectives Inspection and adaption about process 1. Scrum Team inspects the last sprint regarding people, relationships, processes and tools 2. Scrum Team identifies possible improvements and agrees on the measures for next Sprint 3. Scrum Team may update its own working agreement

46 Scrum Customers Scrum Master Backlog grooming Stand-up Product Owner Team Sprint 2 weeks Review Team s commitment Product Backlog Planning Sprint Backlog 0 Changes Feature release Retro

47 Do you have any questions

48 Kanban

49 3 rules 1. Visualize workflow 2. Limit work in progress 3. Measure flow

50 Kanban

51 Do you have any questions

52 Scrum and Kanban differences

53 Scrum Product creation Manufacturing Rhythm Flow Frozen backlog 1 backlog : 1 team vs Event-driven 1 board : n teams Kanban Any size tasks Similar sized tasks Board restarts Persistent board

54 Scrum and Kanban similarities

55 Scrum Pull scheduling Limit WIP Transparency Release early and often Self-organizing teams Kanban Velocity based planning

56 Do you have any questions

57 Have we met expectations

58 Do you have any questions

59 Thank you!