Scrum is an agile software
development model based on multiple small teams working in an intensive and interdependent
manner. The term is named for the scrum (or scrummage) formation in rugby, which is used to restart
the game after an event that causes play to stop, such as an infringement.
Scrum employs real-time decision-making processes based on actual events and information. This
requires well-trained and specialized teams capable of self-management, communication and
decision-making. The teams in the organization work together while constantly focusing on their
common interests.
Scrum involves:
- Initial appointment of a project manager called the "scrum master."
- Definition and prioritization of tasks to be done.
- Planning sessions for each task.
- Daily meetings among teams.
- Identification and evaluation of potential project risks and process pitfalls.
- Execution of projects in brief, high-intensity, frequent work sessions.
- Reviews of progress and evaluations of completed projects.
- Openness to constructive criticism and ideas for improvement.
The scrum concept was introduced by Hirotaka Takeuchi and Ikujiro Nonaka in a 1986 article in
The Harvard Business Review, "The New New Product Development Game" The original context was
manufacturing. Jeff Sutherland, John Scumniotales and Jeff McKenna are credited with adopting,
implementing and documenting the model for software development at Easel Corporation in 1993. In
1995, Ken Schwaber presented an influential white paper at OOPSLA, "SCRUM
Development Process."
This was last updated in February 2007
Email Alerts
Register now to receive SearchSoftwareQuality.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy
More News and Tutorials
-
Software consultant Nari Kannan describes how agile practices and work can be scaled appropriately for success in large organizations. Using lean thinking, reduction of waste, and appropriately organizing work and people, agile can be successfully adapted, regardless of the size of the organization.
-
Undiscovered software glitches in complex systems are common, and one of the primary drivers is the loss of mainframe knowledge of a retiring workforce. Software glitches are lurking in many large systems, particularly mainframe systems, and the COBOL programmers that understand the code best are retiring, according to Jeff Papows, author of the new book, "Glitch - The hidden impact of faulty software." Papows describes how faulty software caused a huge charge to debit card holder's account and why such mistakes are on the rise in this interview. Papows notes the three most pressing drivers for software glitches: loss of intellectual knowledge, market consolidation and the ubiquity of technology
-
Karen Johnson suggests a variety of ways that testers can gain additional skills and experience, including social networking and open source testing.
-
Articles
-
Resources from around the Web
