Scrum
The Scrum method dates back to a Harvard Business Review article from the mid-1980s.[1] It was applied to software by many individuals, including Ken Schwaber, Jeff Sutherland, John Scumniotales, and Jeff McKenna. Takeuchi and Nonaka define a set of process philosophies by using an analogy to rugby. Many of the activities described for XP also apply to a Scrum team. Like XP, Scrum teams will time-box coding activities, that is, set a fixed development cycle and fit as much functionality as possible into the time quantum. The process defined by Takeuchi and Nonaka includes size characteristics: Built-in stability, self-organizing teams, overlapping phases, “multilearning,” subtle control, and organizational transfer of learning. The original ...
Get The Practical Guide to Defect Prevention now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
