Einführung Scrum2

Slide 1: presents Effektiver mit Scrum 18.06.08 | Buchhandlung Lehmanns | Hamburg 1

Slide 26: The End

Slide 27: “Equally responsible for the initiation of project with predefined failure is management that insists upon having fixed commitments from programming personnel prior to the latter’s understanding what the commitment are for. Too frequently, management does not realize that !in asking the staff for “the impossible”, the staff will feel the obligation to respond out of respect, fear or misguided loyalty.!Saying “no” to the boss frequently requires courage, political and ! psychological wisdom, and business maturity that comes with much experience.” -- The Management of Computer Programming Projects\" by Charles Lecht. 1967

Slide 29: Philosophy and Soziology

Slide 30: EDS | BroadVision | ONE

Slide 31: France | Germany | Austria

Slide 32: 1st Certi ed ScrumTrainer

Slide 33: SPRiNT iT

Slide 35: What is Scrum?

Slide 36: 36 Scrum is not a ....

Slide 37: 37 Yahoo Chief Product Owner – “Scrum is faster, better, cooler! It’s the way we first built software at Yahoo, yet is scalable to large, distributed, and outsourced teams.”

Slide 38: 38

Slide 39: 39

Slide 40: 40

Slide 41: 41 Process Types It is typical to adopt the defined (theoretical) modeling approach when the underlying mechanisms by which a process operates are reasonably well understood. When the process is too complicated for the defined approach, the empirical approach is the appropriate choice.” Process Dynamics, Modeling, and Control, Ogunnaike and Ray, Oxford University Press, 1992

Slide 42: Scrum Roles Scrum Roles are Responsibilites of a process not positions in an enterprise

Slide 43: 43 Manager Kunde ScrumMaster Team Product Owner Anwender

Slide 44: 44 Estimation Meeting

Slide 45: 44 Estimation Meeting

Slide 46: 44 Estimation Meeting Preparation of Sprint Planning Formal estimation Spend at least two meetings per Sprint Estimate only Size not Time => Input for Release Planing

Slide 47: 45 Planning Meeting

Slide 48: 45 Planning Meeting

Slide 49: 45 Planning Meeting

Slide 50: 45 Planning Meeting

Slide 51: 45 Planning Meeting Product Backlog Team Capabilities Next Sprint Goal Business Conditions Review, Selected Product Consider, Backlog Technology Stability Organize Sprint Backlog Executable Product Increment

Slide 52: 46 Daily Scrum Meetings

Slide 53: 46 Daily Scrum Meetings

Slide 54: 46 Daily Scrum Meetings • Daily 15 minute meeting

Slide 55: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day

Slide 56: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room

Slide 57: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs

Slide 58: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions

Slide 59: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions • What have you ACHIEVED since last meeting?

Slide 60: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions • What have you ACHIEVED since last meeting? • What will you ACHIEVE before next meeting?

Slide 61: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions • What have you ACHIEVED since last meeting? • What will you ACHIEVE before next meeting? • What is in your way?

Slide 62: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions • What have you ACHIEVED since last meeting? • What will you ACHIEVE before next meeting? • What is in your way? • Impediments and

Slide 63: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions • What have you ACHIEVED since last meeting? • What will you ACHIEVE before next meeting? • What is in your way? • Impediments and • Decisions

Slide 64: 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions • What have you ACHIEVED since last meeting? • What will you ACHIEVE before next meeting? • What is in your way? • Impediments and • Decisions

Slide 65: 47 Sprint Review

Slide 66: 47 Sprint Review

Slide 67: 47 Sprint Review Done!

Slide 68: 47 Sprint Review When a Team member says “done,” what does that mean? Done!

Slide 69: 47 Sprint Review When a Team member says “done,” what does that mean? Done! Code adheres to standards, is clean, has been re-factored, has been unit tested, has been checked in, has been built, and has had a suite of unit tests applied to it

Slide 70: 47 Sprint Review When a Team member says “done,” what does that mean? Done! Code adheres to standards, is clean, has been re-factored, has been unit tested, has been checked in, has been built, and has had a suite of unit tests applied to it Development environment for this to happen requires source code library, coding standards, automated build facility, and unit test harness

Slide 71: 47 Sprint Review When a Team member says “done,” what does that mean? Done! Code adheres to standards, is clean, has been re-factored, has been unit tested, has been checked in, has been built, and has had a suite of unit tests applied to it Development environment for this to happen requires source code library, coding standards, automated build facility, and unit test harness

Slide 72: 47 Sprint Review When a Team member says “done,” what does that mean? Done! Code adheres to standards, is clean, has been re-factored, has been unit tested, has been checked in, has been built, and has had a suite of unit tests applied to it Development environment for this to happen requires source code library, coding standards, automated build facility, and unit test harness

Slide 73: HEARTBEAT RETROSPECTIVES Learning from the past for the future

Slide 74: 49 Running a Sprint

Slide 75: 50

Slide 76: 51 Running 30 days Team builds functionality that includes product backlog and meets Sprint goal Team self-organizes to do work Team conforms to existing standards and conventions Tracks progress

Slide 77: 52

Slide 78: 53

Slide 79: 54 Hrs Sprint Ende Trendline aktuelle Tendline Tage

Slide 80: 55 News -- 50 Produkte -- 30 Schnittstellen - 10 ... 20 9 30 x

Slide 81: 56 Scaling / Distributed Teams / Enterprise

Slide 82: In 1967 I submitted a paper called \"How Do Committees Invent?\" to the Harvard Business Review. HBR rejected it on the grounds that I had not proved my thesis. I then submitted it to Datamation, the major IT magazine at that time, which published it April 1968. Here is one form of the paper's thesis: Conways Law Any organization that designs a system (de ned broadly) will produce a design whose structure is a copy of the organization's communication structure.

Slide 83: 58 Marketing Sales Kunde Dev. IT Kunde Kunde Kunde P P P P P P P P P P P P P Product Owner P P P P P P Team Team Team Team Team P Team Team Team Team P P P

Slide 84: 59 Common Pitfalls

Slide 85: No Vision

Slide 86: No Product Backlog

Slide 87: Product Backlog is not sized

Slide 88: Product Backlog is not estimated

Slide 89: Sprint gets disturbed

Slide 90: No Burn Down Chart

Slide 91: No Daily Scrum

Slide 92: No Impediment list

Slide 93: No nal product increment

Slide 94: No retrospective!

Slide 95: Schwarzwaldstrasse 139 76532 Baden-Baden +49170525 6348 boris.gloger@gmail.com