Agile Project Management with Scrum Katharina Pflgler Free

Agile Project Management with Scrum Katharina Pflügler Free template from www. brainybetty. com

Agenda 1. 2. 3. 4. 5. 6. 7. 9/13/2021 The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts Scrum Meetings Sprint Why Scrum works Free template from www. brainybetty. com 2

Agenda 1. 2. 3. 4. 5. 6. 7. 9/13/2021 The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts Scrum Meetings Sprint Why Scrum works Free template from www. brainybetty. com 3

Scrum (Rugby) Source: http: //en. wikipedia. org/wiki/Image: Rugby_union_scrummage. jpg 9/13/2021 Free template from www. brainybetty. com 4

Agenda 1. 2. 3. 4. 5. 6. 7. 9/13/2021 The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts Scrum Meetings Sprint Why Scrum works Free template from www. brainybetty. com 5

Quick Overview I Product Owner Product Backlog Sprint Planning Meeting Sprint Backlog Scrum Team Scrum Master Sprint Executable Product Increment 9/13/2021 Free template from www. brainybetty. com 6

Quick Overview II Daily Scrum Sprint Planning Meeting 9/13/2021 SPRINT Sprint Review Meeting Free template from www. brainybetty. com 7

Agenda 1. The term “Scrum” 2. Quick Overview 3. Scrum Roles 3. 1 Product Owner 3. 2 Scrum Master 3. 3 Scrum Team 4. 5. 6. 7. 9/13/2021 Scrum Artifacts Scrum Meeting Sprint Why Scrum works Free template from www. brainybetty. com 8

Scrum Roles: Chickens and Pigs A chicken and a pig are walking down the road. The chicken says to the pig: “Do you want to open a restaurant with me? ” The pig considers the question and replies, “Yes, I’d like that. What do you want to call the restaurant? ” The chicken replies, “Ham and Eggs”. The pig stops, pauses and replies, “On a second thought, I don’t think I want to open a restaurant with you. I’d be committed, but you’d only be involved. ” 9/13/2021 Free template from www. brainybetty. com 9

Scrum Roles: Product Owner • Represents the interests of all stakeholders in the project and resulting system • Tasks/Responsibilities: – is the only person in charge of the Product Backlog • maintains and sustains content • prioritizes Product Backlog items • estimates Product Backlog effort – is responsible for initial and ongoing funding 9/13/2021 Free template from www. brainybetty. com 10

Scrum Roles: Scrum Master • Represents management and team to each other • Tasks/Responsibilities: – ensures that Scrum values, practices and rules are enacted and enforced – plans and initiates Sprints together with the team – conducts Daily Scrums and ensures that impediments are promptly removed – controls progress and takes appropriate measures 9/13/2021 Free template from www. brainybetty. com 11

Scrum Roles: Scrum Team • Tasks/Responsibilities: – formulates a Sprint Goal at the Sprint Planning Meeting – commits to turn a set of Product Backlog into a working product – self-organizes (assigns, works on, modifies and (re-)estimates tasks) → responsible for doing all analysis, design, coding, testing and user documentation → has full authority to do whatever is necessary to meet the Sprint Goal • Team size: seven people, plus or minus two • Team composition: cross-functional → analysts, designers, coding engineers 9/13/2021 Free template from www. brainybetty. com 12

Agenda 1. 2. 3. 4. The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts 4. 1 Product Backlog 4. 2 Sprint Backlog 4. 3 Executable Product Increment 5. Scrum Meetings 6. Sprint 7. Why Scrum works 9/13/2021 Free template from www. brainybetty. com 13

Scrum Artifacts: Product Backlog • Description: Product Backlog is a prioritized list of all features, functions, technologies, enhancements and bug fixes • Creation: first Product Backlog derived from a vision document, marketing requirements or brainstorming • Contains: – product features and technology – issues: need to be resolved before starting working on it – items are estimated in days • Who: – influenced by pigs and chickens – Product Owner makes decisions on contents, prioritizes items and estimates the effort 9/13/2021 Free template from www. brainybetty. com 14

Scrum Artifacts: Sprint Backlog • Description: is a highly visible, real-time picture of the work that the Team plans to accomplish during the Sprint • Creation: Sprint Backlog is selected during a Sprint Planning Meeting after having established a Sprint Goal • Contains: – tasks which more detailed than in Product Backlog – each task takes four to sixteen hours to finish • Who: – Scrum Team selects the tasks and modifies/estimates them throughout the Sprint 9/13/2021 Free template from www. brainybetty. com 15

Scrum Artifacts: Sprint Backlog 9/13/2021 Free template from www. brainybetty. com 16

Scrum Artifacts: Executable Product Increment • Or: Increment of Potentially Shippable Product Functionality • Creation: implemented during the Sprint • Contains: – thoroughly tested, well-structured and well-written code – documentation • Who: – Scrum Team committed to deliver an executable increment at the end of the Sprint 9/13/2021 Free template from www. brainybetty. com 17

Agenda 1. 2. 3. 4. 5. The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts Scrum Meetings 5. 1 Sprint Planning Meeting 5. 2 Sprint Review Meeting 5. 3 Daily Scrums 6. Sprint 7. Why Scrum works 9/13/2021 Free template from www. brainybetty. com 18

Scrum Meetings: Sprint Planning Meeting I Consists of two consecutive meetings. First Meeting: • Who: – pigs: Scrum Team, Scrum Master, Product Owner – chickens: management, users, customer(s) • Input: – Product Backlog – Latest increment – Team capabilities, business conditions, technology stability • Steps: – Product Owner presents top priority Product Backlog – Discussion about what changes to the backlog are appropriate – Team identifies the backlog items that it believes it can develop during the Sprint – Team formulates a Sprint Goal • Output: – Sprint Goal – Selected Product Backlog items 9/13/2021 Free template from www. brainybetty. com 19

Scrum Meetings: Sprint Planning Meeting II Second Meeting: • Who: – Scrum Team – Team may invite others, i. e. Product Owner • Input: – – • Selected Product Backlog items Sprint Goal Latest increment Team capabilities, business conditions, technology stability Steps: – Team compiles a list of tasks – Team estimates effort and assigns tasks → Scrum Team self-organizes • Output: – Sprint Backlog 9/13/2021 Free template from www. brainybetty. com 20

Scrum Meetings: Sprint Review Meeting • Who: – pigs: Scrum Team, Scrum Master, Product Owner – chickens: management, users, customer(s), other engineers • Input: – Product increment • Steps: – Before: Scrum Master meets with the team to establish an agenda, who will present the results and how they will be presented – Scrum Master gives a concise overview of the Sprint – Team members compare Sprint Goal and selected Product Backlog to the actual results – Product increment is demonstrated • Important: – Sprint Review Meetings are very informal, i. e. Power Point Presentations are forbidden – Sprint Review Meeting is informational, not critical or actionoriented 9/13/2021 Free template from www. brainybetty. com 21

Scrum Meetings: Daily Scrums I • Who: – Scrum Master and Team – Chickens & other pigs • Location: – Near the team’s working location – Equipment: table & enough chairs for all team members, white boards, speakerphone • Steps: – Scrum Master gets team members from remote locations on the conference phone – All team members have to answer the following questions: – What have you done since last Daily Scrum? – What will you do between now and the next Daily Scrum? – What got in your way of doing work? 9/13/2021 Free template from www. brainybetty. com 22

Scrum Meetings: Daily Scrums II • Rules: – Don’t discuss design or start to solve a problem – Speak as briefly as possible – Don’t be late or you will be charged small fine for tardiness • Goals: – – – 9/13/2021 Improve communication Eliminate other meetings Identify/remove impediments Highlight and promote quick decision-making Continuous monitoring Free template from www. brainybetty. com 23

Agenda 1. 2. 3. 4. 5. 6. 7. 9/13/2021 The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts Scrum Meetings Sprint Why Scrum works Free template from www. brainybetty. com 24

Sprint !!! The Scrum Team has full authority !!! • Mandatory accountabilities – Daily Scrum Meetings – Sprint Backlog → all work is measured and empirically controlled • Factors influencing the amount of work accomplished – – – 9/13/2021 Team’s ability to work together Skills of team members Work to be performed Capabilities of the tools Company standards Free template from www. brainybetty. com 25

Sprint Backlog Graphs Perfect Backlog Graph • Working on weekends • Worked the same amount every day • Planning and estimating was perfect Source: Schwaber, K. ; Beedle, M. (2001), p. 74 f More likely Backlog Graph • 4 -5: no updates • 6 -8: more work discovered • 18: Sprint Backlog reduced • 19 -30: team motivated, even works on weekend 9/13/2021 Free template from www. brainybetty. com 26

Sprint Backlog Graphs Source: Schwaber, K. ; Beedle, M. (2001), p. 78 Team didn’t update its estimates while it was working → Management and Scrum Master can’t use graph 9/13/2021 Free template from www. brainybetty. com 27

Sprint Backlog Graphs Backlog Graph for underestimating • 4 -8: team discovers new work and re-estimates • 18: remove 700 h of work from Sprint Backlog Source: Schwaber, K. ; Beedle, M. (2001), p. 79 ff Backlog Graph for overestimating • 1 -12: team gets work done faster than expected • 13: decides to deepen the degree of functionality 9/13/2021 Free template from www. brainybetty. com 28

Agenda 1. 2. 3. 4. 5. 6. 7. The term “Scrum” Quick Overview Scrum Roles Scrum Artifacts Scrum Meetings Sprint Why Scrum works 7. 1 Noise 7. 2 Process Control Model 7. 3 Empirical Management Model 9/13/2021 Free template from www. brainybetty. com 29

Why Scrum works: Noise • Noise refers to the unpredictable, irregular, nonlinear parts of system development • Noise level/category: Source: Schwaber, K. (2003), p. 5 – Y-axis: degree of uncertainty about project requirements – X-axis: likelihood that the selected technologies will be able to help accomplish the project’s goals 9/13/2021 Free template from www. brainybetty. com 30

Why Scrum works: Process Control Model • Defined Process Control Model – Noise category: • simple – Management & Control: • defined process can be reused several times → same results • exercised by defining the process • Empirical Process Control Model – Noise category: • rest – Management & Control: • any attempt to reuse complex process → different outcomes • exercised through frequent inspection and adaptive response 9/13/2021 Free template from www. brainybetty. com 31

Why Scrum works: Empirical Management Model • Empirical process control models employs feedback mechanisms to monitor and adapt to the unexpected, providing regularity and predictability • Empirical Management Model: Source: Schwaber, K. ; Beedle, M. (2001), p. 101 – – 9/13/2021 “I”- Input (requirements, technology, team) “Process” (Sprint) “C”- Control unit at Daily Scrums, Sprint Review Meetings “O”- Output (executable product increment) Free template from www. brainybetty. com 32