SEA - Challenges In Scaling Scrum First...••Scrum can significantly improve developer job satisfaction, but that is a secondary result. Business objectives are driving. ••Scrum
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
4/4/2013
1
Challenges In Scaling ScrumChallenges In Scaling Scrum
Robert WardRobert Ward3 April 20133 April 2013
The Agile Manifesto In ContextThe Agile Manifesto In Context
•• The Manifesto is mostly heuristics, not mandates and The Manifesto is mostly heuristics, not mandates and
not first principles.not first principles.
•• It aimed to legitimize resistance to “conventional It aimed to legitimize resistance to “conventional
wisdom” about software development. wisdom” about software development.
•• The manifesto was what the diverse signatories could The manifesto was what the diverse signatories could
agree to at the time. agree to at the time.
•• We can now say much more about how and why Agile We can now say much more about how and why Agile
•• Software Development is always affected by Software Development is always affected by many unknowable random variables. many unknowable random variables.
•• Stable random processes are Stable random processes are very very predictable in the aggregate.predictable in the aggregate.
•• Agile reporting and planning exploits SPC. Each Agile reporting and planning exploits SPC. Each Velocity measurement is a sample from a Velocity measurement is a sample from a continuous, stable process. Scrum measures continuous, stable process. Scrum measures process output in estimated scope units (story process output in estimated scope units (story points), absorbing both random variation in the points), absorbing both random variation in the estimation and in the production time. estimation and in the production time.
Conflicting Ideas You Conflicting Ideas You Might Might HearHear
•• With planning, sprint review, and retrospective, With planning, sprint review, and retrospective, two week sprints incur too much overhead. We two week sprints incur too much overhead. We need at least four weeks.need at least four weeks.
•• There’s no point in reThere’s no point in re--estimating every day. All we estimating every day. All we need to track is which stories get finished.need to track is which stories get finished.
•• We should just plan a three week “release sprint” We should just plan a three week “release sprint” for all the things we end up needing to do at the for all the things we end up needing to do at the end of the release cycle. end of the release cycle.
Deming, William Edwards.Deming, William Edwards. Out of the CrisisOut of the Crisis. MIT press, 2000.. MIT press, 2000.
Buchholz, Steve, Thomas Roth, and Buchholz, Steve, Thomas Roth, and KärenKären M. Hess.M. Hess. Creating the high performance Creating the high performance
teamteam. John Wiley & Sons Inc, 1987.. John Wiley & Sons Inc, 1987.
ReinertsenReinertsen, D. G. , D. G. The Principles of Product Development FlowThe Principles of Product Development Flow––Second Generation Lean Second Generation Lean
Carson, Shelley.Carson, Shelley. Your creative brain: Seven steps to maximize imagination, productivity, Your creative brain: Seven steps to maximize imagination, productivity,
and innovation in your lifeand innovation in your life. . JosseyJossey--Bass, 2010.Bass, 2010.
GladwellGladwell, Malcolm., Malcolm. Outliers: The story of successOutliers: The story of success. . ePenguinePenguin, 2008., 2008.
Martin, Robert C.Martin, Robert C. Clean code: a handbook of agile software craftsmanshipClean code: a handbook of agile software craftsmanship. Prentice . Prentice
Hall, 2008.Hall, 2008.
Cohn, Mike.Cohn, Mike. Succeeding with agile: software development using ScrumSucceeding with agile: software development using Scrum. Addison. Addison--Wesley Wesley
Professional, 2009.Professional, 2009.
LarmanLarman, Craig., Craig. Agile and iterative development: a manager's guideAgile and iterative development: a manager's guide. Addison. Addison--Wesley Wesley
Professional, 2004Professional, 2004..
KnibergKniberg, , HenrikHenrik. ". "KanbanKanban vsvs Scrum."Scrum." Crisp AB. Crisp AB. ViitattuViitattu 1 (2009): 2011.1 (2009): 2011.