Wstęp do estymacji w Scrum.

Transcription

1 Wstęp do estymacji w Scrum pawel.rola@pwr.wroc.pl

2 Agenda Kim jesteśmy? Wprowadzenie Cel, plan, itd. Moduł 1: Podstawy Scrum Moduł 2: Wymagania w projekcie. Moduł 3: Podstawy estymacji Podsumowanie i zakończenie 2

3 Kim jestem Paweł Rola

4 ESVP Explorer Shopper Vacationer Prisoner

5 Rules Presentation in English; Phones, laptops, tablets; Engagement is required; Feel free to ask a question; Parking lot; The lecture is for you, I already know Agile and Scrum < 5 >

6 Goals To acquaint students with estimation in the Scrum method Verification of the acquired theoretical knowledge in practical exercises

7 Introduction to Scrum

8 Agile vs Waterfall < 8 >

9 Agile, Scrum and XP be Agile do Scrum FDD DSDM XP Lean Kanban Crystal < 9 >

10 Agile Manifesto < < 10 >

11 Scrum Definitions Scrum is a framework for developing and sustaining complex products. Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques. Values and principles Scrum is based on own values and pillars (other than Manifesto for Agile Software Development ) The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.

12 Scrum values Commitment Be willing to commit to a goal. Scrum provides people all the authority they need to meet their commitments. Focus Openness Do your job. Focus all of your efforts and skills on doing the work that you ve committed to doing. Don t worry about anything else. Scrum keeps everything about a project visible to everyone. Respect Individuals are shaped by their background and their experiences. It is important to respect the different people who comprise a team. Courage Have the courage to commit, to act, to be open, and to expect respect.

13 Scrum framework 13

14 Project roadmap Item A Item B Item C Item D Item E

15 How describe requirements

16 What is a User Story? A concise, written description of a piece of functionality that will be valuable to a user (or owner) of the product.

17 Cards, Conversation, Confirmation Clean house. My girlfriend wants the house My girlfriend to be clean, wants because the house we to have be clean. dinne guests tonight Who is asking? Goal? Where should I start? When I will be done? < 17

18 User identification Desired feature to be deliv. Description why it`s need as a user A I want to action B because target c A+B+C = USER STORY As who I want what so that why How does the work change as the subject, or user changes? How does the work change as the reason changes? < 18

19 What is a good user story? Independent Negotiable Valuable Estimable Sized properly Testable 19

20 Exercise Your life partner told you to prepare a Christmas party, because of family visit. Today is match of Polish national football team, and you want to see the match. Colleagues have offered to help in party preparation. You agree that it would be the best to manage the project in Agile way. Using user stories describe all work that need to be done. Write not less then 15 user stories, pay attention to the needs, Product Owner (wife / girlfriend) and stakeholders (family and mother in law, team-mates?) Work in group. Time: 10 minutes! < 20 >

21 priority Product Backlog Iceberg High Size 2-3 Sprints Detail Sprint Release Future Release Low < 21

22 priority Product Backlog Iceberg High Product Backlog Throw away newspaper Clean table Put away shirt Clean bedroom No dust on ferniture Throw away bottel Clean 2nd floor Clean bathroom Made-up bed Put away towel Clean 1st floor Clean toilet Clean windows Wash the glass Low Clean ground floor Clean living room Clean floors Clean house Clean garage Clean basement Clean dining-room Clean hall Sprint Backlog < 22

23 Basis of estimation

24 Estimation Relative estimates Abstract units Re-estimations Team estimates / planning poker 24

25 Story Points Story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story. In simple terms its a number that tells the team how hard the story is. Hard could be related to complexity, Unknowns and effort. Story points are not a measurement of duration, but rather a measurement of size/complexity

26 Story Points

27 What the Planning Poker is? It is based on Wideband Delphi and Delphi Method; Combines expert opinion, analogy, feedback, iterative, independence; Focus on estimating the size, not the duration; Put estimates in abstract units that we can add together; It`s fun; < 27 >

28 Planning poker - overview An iterative approach to estimating Steps Each player has deck of cards that read: 0, 1, 2, 3, 5, 8, 13, 20, 40, 60 and 100 Product Owner reads a story and it s discussed briefly Each estimator selects a card that s his or her estimate Cards are turned over simultaneously so anyone can see them Outliners discuss differences (but others can join) Re-estimate until estimates converge

29 Planning Poker Why to use it? Why to use it?

30 Examples - real projects pawel.rola@pwr.wroc.pl

31 Scrum practice Sprint planning and tracking NOT STARTED ONGOING DONE

32 Scrum practice sprint burndown chart Sum over all done-activities Estimated velocity Additional tasks identified

33 Scrum practice daily planning and tracking

34 Real project < 34 >

35 Real project < 35 >

36 Real project < 36 >

37 Real project < 37 >

38 Parking lot