Dr. Jeff Sutherland is one of the inventors of the Scrum software development process. Together with Ken Schwaber, he created Scrum as a formal process at OOPSLA'95. Sutherland helped to write the Agile Manifesto in 2001. He is the writer of The Scrum Guide.
||This section of a biography of a living person does not include any references or sources. (January 2014) (Learn how and when to remove this template message)|
Sutherland is a Graduate of the United States Military Academy, a Top Gun of his USAF RF-4C Aircraft Commander class. He flew more than one hundred missions over North Vietnam. After 11 years in the military he became a doctor at the University of Colorado School of Medicine. Here he got involved in data collection and IT systems development.
Scrum is a framework for enabling business agility at scale across an entire organization. Well known for its application to software development, it is now used in other domains at GE, 3M, Toyota, Mearsk, British Petroleum, Tesla, and other leading companies. A meeting which was strongly influenced by the founders of Scrum created the Agile Manifesto. Sutherland is quoted as saying the "systems development process is an unpredictable and complicated process that can only roughly be described as an overall progression".
The agile approach was developed by Sutherland, John Scumniotales and Jeff McKenna while at Easel Corporation. The principle was based on a 1986 article by Hirotaka Takeuchi and Ikujiro Nonaka in the Harvard Business Review, and incorporates practices from a draft study published in Dr. Dobb's Journal. It involves 30-day cycles of plan, build and monitor sprints. The name Scrum was chosen in reference to the rugby scrummage, as the system involves "a cross-functional team" who "huddle together to create a prioritized list". Scrum has been used by several major corporations. Sutherland has claimed that distributed teams coached to use the system can make large productivity increases against the industry average.
Scrum involves a cross-functional team creating a list to work on. The team consists of three roles, the Product Owner, the Team and the Scrummaster, who each have specific tasks. The team then work through three phases - pre-sprint planning, the sprint and then a post-sprint meeting. The group has daily meetings and keeps a Product Backlog. In contributing to the book The Secrets of Happy Families, Sutherland modified the Agile approach to family interactions.
Sutherland has been quoted as saying the three distinguishing factors between Scrum teams and normal teams are self-management, continuity of team membership, and dedication to a single project. Clarification of user needs is an essential component. Sutherland said no coding should occur while user needs were in doubt, and is quoted as saying "It is better for the developers to be surfing than writing code that won't be needed". Sutherland has also been quoted as saying that Scrum should run with software architecture.
In 1995, Sutherland and Schwaber jointly presented a paper describing the Scrum methodology at the Business Object Design and Implementation Workshop held as part of Object-Oriented Programming, Systems, Languages & Applications '95 (OOPSLA '95) in Austin, Texas, its first public presentation.
In the book Lean-Agile Software Development: Achieving Enterprise Agility, it was noted that the Scrum system as originally developed by Sutherland, had testing and engineering components which were removed to make the system easier. This decision was criticized, as "without them the quality of your code will degrade", and future change becomes more difficult.
- Schwaber, Ken (2009). Agile Project Management with Scrum. O'Reilly Media, Inc. ISBN 9780735637900.
- Scrum: The Art of Doing Twice the Work in Half the Time
- Pham, Andrew Thu (2012). Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean) Implementation: An Action Guide for Business and IT Leaders. CRC Press. ISBN 9781466578562.
- Zelkowitz, Marvin (2008). "History of Computers, Electronic Commerce". Advances in Computers: Emerging Technologies. 73: 32.
- Sims, Peter (2011). Little Bets: How breakthrough ideas emerge from small discoveries. Random House. p. 85. ISBN 9781409038030.
- Coplien, James O. (2011). Lean Architecture: for Agile Software Development. John Wiley & Sons. ISBN 9780470970133.
- Armour, Phillip G. (2004). The Laws of Software Process: A New Model for the Production and Management of Software. CRC Press. p. 112. ISBN 9780203505649.
- McQuarrie, Gray (2010). Change Your Dam Thinking. Bound Publishing. p. 133. ISBN 9780986723308.
- Larman, Craig (2008). Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum. Pearson Education. ISBN 9780321617149.
- Woodward, Elizabeth (2010). A Practical Guide to Distributed Scrum. Pearson Education. ISBN 9780137061365.
- Rico, David F. (2007). Effects of Agile Methods on Website Quality for Electronic Commerce. ProQuest. ISBN 9780549764946.
- Kroll, Per (2006). Agility and Discipline Made Easy: Practices from OpenUP and RUP. Pearson Education. ISBN 9780132702485.
- Parrish, Shane (9 December 2013). "The secrets of happy families". The Week. Retrieved 18 December 2013.
- Viscardi, Stacia (2013). The Professional ScrumMaster’s Handbook. Packt Publishing Ltd. ISBN 9781849688031.
- Alan Shalloway; Guy Beaver; James R. Trott (2009). Lean-Agile Software Development: Achieving Enterprise Agility. Pearson Education. ISBN 9780321647993.