0
[email_address]
[email_address] Or why we needed to create a Lean Culture
Polopoly – Web Content Management
Began with Scrum  autumn  2007
The 15 Scrum word we use - The  things  we can talk about <ul><li>Product Owner
Scrum Master
The Team
Pigs
Chickens
Product Backlog
Story
DOD
Sprint
Sprint Planning Meeting
Sprint board
Daily Scrum Meeting
Upcoming SlideShare
Loading in...5
×

SCRUM at Polopoly - or building a lean culture

617

Published on

Lightning talk held at Agila Sverige 2008, on the importance of building a lean culture to get Scrum (or Agile) to work.

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

  • Be the first to like this

No Downloads
Views
Total Views
617
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "SCRUM at Polopoly - or building a lean culture"

  1. 1. [email_address]
  2. 2. [email_address] Or why we needed to create a Lean Culture
  3. 3. Polopoly – Web Content Management
  4. 4. Began with Scrum autumn 2007
  5. 5. The 15 Scrum word we use - The things we can talk about <ul><li>Product Owner
  6. 6. Scrum Master
  7. 7. The Team
  8. 8. Pigs
  9. 9. Chickens
  10. 10. Product Backlog
  11. 11. Story
  12. 12. DOD
  13. 13. Sprint
  14. 14. Sprint Planning Meeting
  15. 15. Sprint board
  16. 16. Daily Scrum Meeting
  17. 17. Burndown Graph
  18. 18. Sprint Review Meeting
  19. 19. Sprint Retrospective Meeting </li></ul>
  20. 20. Good, but also a lot of problems
  21. 21. Technical difficulties <ul><li>Specialist teams
  22. 22. Long sprints
  23. 23. Hard to reach goals
  24. 24. Lots of trouble with support and defects
  25. 25. To much planning
  26. 26. And more... </li></ul>
  27. 27. Theoretical difficulties <ul><li>How make people trust the 15 simple Scrum rules and artifacts?
  28. 28. How to do all the daily micro decisions? </li></ul>
  29. 29. Choosing road <ul><li>Either become experts on the Scrum manuals </li><ul><li>That is, find the answer to all questions by finding practical suggestions from the books </li></ul><li>Or internalize the principles that make Scrum work </li></ul>
  30. 30. We choose the principles <ul><li>No litterary exegetic
  31. 31. But building a culture where one ”feels what is right” </li></ul>
  32. 32. But how do you build a culture? And from what? <ul><li>We found help outside of Scrum </li></ul>
  33. 33. The Team <ul><li>Make a cult of quality
  34. 34. Provide lots of satisfying closures
  35. 35. Build a sense of elitness
  36. 36. Allow and encourage heterogeneity </li></ul>
  37. 37. Testing, testing, testing
  38. 38. The Process <ul><li>Lean ground rules </li><ul><li>Eliminate Waste (JIT)
  39. 39. Expose problem (Stop-the-Line) </li></ul><li>Pull system </li></ul>
  40. 40. We try to express the culture (every day) through a number of phrases <ul><li>” the Right thing, the Right way, Regularly”
  41. 41. &quot;Art of the possible&quot;
  42. 42. &quot;Inspect and adapt&quot;
  43. 43. &quot;One piece flow&quot;
  44. 44. &quot;Stop the line&quot;
  45. 45. ” Don't overdo it”
  46. 46. &quot;Eliminate waste&quot;
  47. 47. &quot;Cross-functional teams&quot;
  48. 48. &quot;JIT planing&quot; - &quot;Last responsible moment&quot;
  49. 49. &quot;Adapt to Capacity&quot;
  50. 50. ” Closed door politics” </li></ul>
  51. 51. Now it is working much better
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×