 - 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."
 |
Learn more about Scrum software development |
| How Covad made the switch to a distributed agile development process: Waterfall methodologies weren't working for Covad Communications, so the company switched its process to agile and cut costs while achieving faster project completions. |
| Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?: Agile software development calls on developers to write clean code, according to Robert "Uncle Bob" Martin. This free chapter introduces the concepts and methods of clean code. |
| Scrum and requirements gathering: Hello. We are a very small company interested in agile, specifically Scrum. I am wondering if becoming certified in Scrum would be really helpful or if I could do without this certification. ... |
| Big Blue dog learns new tricks: How IBM Software Group moved to agile: In this case study, IBM's VP of development transformation, explains how and why the IBM Software Group made the transition to agile. |
| Addressing software quality issues with development models, methods: Each development model has its own practices for building quality software. The challenge is determining which one fits your needs. The resources here can help you decide. |
| Best practices for Scrum and when to apply them: There are many situations where Scrum "best practices" are not the appropriate practice to be using. This expert tip will help you decide when to use Scrum to deliver a project. |
| Test-driven testing face-off: Waterfall vs. Agile: Most software test pros pick a preferred methology and stand by it, in this tip two testers square-off, one advocating for agile development, the other in the waterfall corner. |
| Accelerate your agile software testing: This expert tip explains how adopting agile development and risk-driven and test-driven development can accelerate testing. |
| Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?: Agile software development calls on developers to write clean code, according to Robert "Uncle Bob" Martin. This free chapter introduces the concepts and methods of clean code. |
| LAST UPDATED: |
15 Feb 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
