presents




Effektiver mit Scrum
        18.06.08 | Buchhandlung Lehmanns | Hamburg
                                      ...
The End
“Equally responsible for the initiation of project with
predefined failure is management that insists upon having
fixed co...
Philosophy and Soziology
EDS | BroadVision | ONE
France | Germany | Austria
1st Certi ed ScrumTrainer
SPRiNT iT
What is Scrum?
36




Scrum is not a ....
37




Yahoo Chief Product Owner – “Scrum is faster, better, cooler! It’s the way we first built
 software at Yahoo, yet is...
38
39
40
41




Process Types
It is typical to adopt the defined (theoretical) modeling
 approach when the underlying mechanisms by ...
Scrum Roles
Scrum Roles are Responsibilites of a process
not positions in an enterprise
43




                                       Manager




Kunde
                        ScrumMaster


                    ...
44




Estimation Meeting
44




Estimation Meeting
44




Estimation Meeting


                 Preparation of Sprint Planning
                 Formal estimation
           ...
45




Planning Meeting
45




Planning Meeting
45




Planning Meeting
45




Planning Meeting
45




Planning Meeting


               Product Backlog
               Team Capabilities                  Next Sprint Goa...
46




Daily Scrum Meetings
46




Daily Scrum Meetings
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
46




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




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
46




Daily Scrum Meetings
                   • Daily 15 minute meeting
                   • Same place and time every da...
47




Sprint Review
47




Sprint Review
47




Sprint Review
Done!
47




Sprint Review
                When a Team member says “done,” what does that mean?


Done!
47




Sprint Review
                When a Team member says “done,” what does that mean?


Done!           Code adheres t...
47




Sprint Review
                When a Team member says “done,” what does that mean?


Done!           Code adheres t...
47




Sprint Review
                When a Team member says “done,” what does that mean?


Done!           Code adheres t...
47




Sprint Review
                When a Team member says “done,” what does that mean?


Done!           Code adheres t...
HEARTBEAT
RETROSPECTIVES
    Learning from the past for the future
49




Running a Sprint
50
51




Running

 30 days
 Team builds functionality that includes
  product backlog and meets Sprint goal
 Team self-organ...
52
53
54




Hrs
                     Sprint Ende




      Trendline


                  aktuelle
                  Tendline


...
55




News -- 50   Produkte -- 30   Schnittstellen - 10   ...




                 20                   9
   30          ...
56




Scaling / Distributed Teams / Enterprise
In 1967 I submitted a paper called quot;How Do Committees
              Invent?quot; to the Harvard Business Review. HBR r...
58




Marketing      Sales       Kunde         Dev.               IT          Kunde         Kunde     Kunde


           ...
59




Common Pitfalls
No Vision
No Product Backlog
Product Backlog is not sized
Product Backlog is not estimated
Sprint gets disturbed
No Burn Down Chart
No Daily Scrum
No Impediment list
No nal product increment
No retrospective!
Schwarzwaldstrasse 139
76532 Baden-Baden
+49170525 6348
boris.gloger@gmail.com
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Einführung Scrum2
Upcoming SlideShare
Loading in …5
×

Einführung Scrum2

966 views

Published on

Scrum Vortrag, Boris Gloger, Buchhandlung Lehmanns, Hamburg

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
966
On SlideShare
0
From Embeds
0
Number of Embeds
89
Actions
Shares
0
Downloads
28
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Einführung Scrum2

  1. 1. presents Effektiver mit Scrum 18.06.08 | Buchhandlung Lehmanns | Hamburg 1
  2. 2. The End
  3. 3. “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 Projectsquot; by Charles Lecht. 1967
  4. 4. Philosophy and Soziology
  5. 5. EDS | BroadVision | ONE
  6. 6. France | Germany | Austria
  7. 7. 1st Certi ed ScrumTrainer
  8. 8. SPRiNT iT
  9. 9. What is Scrum?
  10. 10. 36 Scrum is not a ....
  11. 11. 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.”
  12. 12. 38
  13. 13. 39
  14. 14. 40
  15. 15. 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
  16. 16. Scrum Roles Scrum Roles are Responsibilites of a process not positions in an enterprise
  17. 17. 43 Manager Kunde ScrumMaster Team Product Owner Anwender
  18. 18. 44 Estimation Meeting
  19. 19. 44 Estimation Meeting
  20. 20. 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
  21. 21. 45 Planning Meeting
  22. 22. 45 Planning Meeting
  23. 23. 45 Planning Meeting
  24. 24. 45 Planning Meeting
  25. 25. 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
  26. 26. 46 Daily Scrum Meetings
  27. 27. 46 Daily Scrum Meetings
  28. 28. 46 Daily Scrum Meetings • Daily 15 minute meeting
  29. 29. 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day
  30. 30. 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room
  31. 31. 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs
  32. 32. 46 Daily Scrum Meetings • Daily 15 minute meeting • Same place and time every day • Meeting room • Chickens and pigs • Three questions
  33. 33. 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?
  34. 34. 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?
  35. 35. 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?
  36. 36. 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
  37. 37. 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
  38. 38. 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
  39. 39. 47 Sprint Review
  40. 40. 47 Sprint Review
  41. 41. 47 Sprint Review Done!
  42. 42. 47 Sprint Review When a Team member says “done,” what does that mean? Done!
  43. 43. 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
  44. 44. 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
  45. 45. 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
  46. 46. 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
  47. 47. HEARTBEAT RETROSPECTIVES Learning from the past for the future
  48. 48. 49 Running a Sprint
  49. 49. 50
  50. 50. 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
  51. 51. 52
  52. 52. 53
  53. 53. 54 Hrs Sprint Ende Trendline aktuelle Tendline Tage
  54. 54. 55 News -- 50 Produkte -- 30 Schnittstellen - 10 ... 20 9 30 x
  55. 55. 56 Scaling / Distributed Teams / Enterprise
  56. 56. In 1967 I submitted a paper called quot;How Do Committees Invent?quot; 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.
  57. 57. 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
  58. 58. 59 Common Pitfalls
  59. 59. No Vision
  60. 60. No Product Backlog
  61. 61. Product Backlog is not sized
  62. 62. Product Backlog is not estimated
  63. 63. Sprint gets disturbed
  64. 64. No Burn Down Chart
  65. 65. No Daily Scrum
  66. 66. No Impediment list
  67. 67. No nal product increment
  68. 68. No retrospective!
  69. 69. Schwarzwaldstrasse 139 76532 Baden-Baden +49170525 6348 boris.gloger@gmail.com

×