10 Years of My Scrum Experience

3,178 views

Published on

What Scrum is, what Scrum isn't, what Scrum solves, what it doesn't and some challenges.

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

No Downloads
Views
Total views
3,178
On SlideShare
0
From Embeds
0
Number of Embeds
44
Actions
Shares
0
Downloads
42
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

10 Years of My Scrum Experience

  1. 1. 10 Years Of My Scrum ExperienceStephan SchmidtStephan Schmidt, Vice CTO, brands4friends
  2. 2. MeStephan SchmidtVice CTO brands4friends
  3. 3. Stephan Schmidt - What Top Management needs to know about IT
  4. 4. Development is a solved problem
  5. 5. Waterfall Resources ($$$) Time ScopeKanban (Lean) Agile (Scrum)
  6. 6. Context: After 10 years of ScrumI’m moving on – kind of ….. but would introduce Scrum as a processanytime again for companies coming fromwaterfall or chaos
  7. 7. Scrum is a process to efficientlywork on tasks when you havemore tasks than timeWhat should I work on? Not only softwaredevelopment.
  8. 8. Biggest down side of Scrum:Companies haven’t learned whatagile means for marketing,sales, ….Big impact would be for companies to learnwhat agile means for them and structurethemselves accordingly.
  9. 9. Scrum is not a productdevelopment processDo the right thing vs. doing things right
  10. 10. Scrum is not a portfolio processWhat is my company doing?
  11. 11. Scrum is not a release processRelease, Continuous Deployments ….
  12. 12. Scrum says nothing aboutdevelopment best practicesThe #1 reason for it’s success as very fewdevelopers are opposed. But you need tofill this gap by yourself.
  13. 13. Scrum doesn’t solve time tomarketBiggest lever: do less
  14. 14. What Scrum solves
  15. 15. WorksScrum is one of the first processes that(easily following recipes) just work for mostpeople
  16. 16. QualityScrum increased code quality because itgave responsibility to developers
  17. 17. SatisfactionOverall everyone is satisfied, business,product and developers
  18. 18. When will I be finished answeredwith very little estimationoverhead for projectsWhat am I going to do in what sprint
  19. 19. Scrum Helps With Focus 1. Feature 2. Feature 1. Feature 2. Feature 3. Feature 4. Feature 5. Feature 3. Feature 4. Feature 5. Feature Time Time Parallel Serial
  20. 20. Self Organized TeamsCross functional teams, sharedresponsibility, better communication andfewer SPOFs
  21. 21. What Scrum doesn’t solve
  22. 22. Development StartIdea Front-up DevelopmentProblems are here Everyone focuses here
  23. 23. Top Management Attention of top possible impact management for a project Reinertsen 1998
  24. 24. Scrum Challenges
  25. 25. ArchitectureEmerging architectures?
  26. 26. CareersFlat hierarchies exist and self-organizedteams “without” roles increase the problem
  27. 27. Performance AppraisalPeers to the rescue?
  28. 28. Sometimes there is not enoughtime in a sprint, sometimes thereis too muchThe downside of time boxed sprints is10%-20% less efficiency
  29. 29. X scrum masters for Y teamsScrum masters amount of work isdecreasing over time, but you can’t dowithout a Scrum master either.
  30. 30. Balance HeadroomVs.BusinessMaintainability vs. Business ValueandPull vs. Push
  31. 31. RolesScrum master =! Team LeadScrum master =! DeveloperScrum master =! Project ManagerRole conflicts lead to trouble
  32. 32. CoordinationSPOFs (DBAs etc.) no recipePortfolio management, how to do that?Coordinating POs – often working towardstheir own goalsScrum of Scrums looks not efficient to me
  33. 33. EpicsFocus, not 1 developer == 1 storySometimes too many, too different smallstories in one sprint => Focus on Epics
  34. 34. Self Organized Teams1. Goal and bonus management vs. self organized teams2. Recruiting vs. self organized teams3. Firing vs. self organized teams
  35. 35. Thanks!Questions?@codemonkeyismstephan.schmidt@brands4friends.de

×