DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 966,904 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Fabrice Ndabitezamaso
Fabrice Ndabitezamaso

Posted on • Updated on

What is scrum(software development)?

Scrum (software development)

Scrum is a framework for developing, delivering, and sustaining products in a complex environment,[1] with an initial emphasis on software development, although it has been used in other fields including research, sales, marketing and advanced technologies.[2] It is designed for teams of ten or fewer members, who break their work into goals that can be completed within time-boxed iterations, called sprints, no longer than one month and most commonly two weeks. The Scrum Team assess progress in time-boxed daily meetings of 15 minutes or less, called daily scrums (a form of stand-up meeting). At the end of the sprint, the team holds two further meetings: the sprint review which demonstrates the work done to stakeholders to elicit feedback, and sprint retrospective which enables the team to reflect and improve.

Name

The software development term SCRUM was first used in a 1986 paper titled "The New New Product Development Game" by Hirotaka Takeuchi and Ikujiro Nonaka.[3] The paper was published in the Jan 1986 issue of Harvard Business Review. The term is borrowed from rugby, where a scrum is a formation of players. The term scrum was chosen by the paper's authors because it emphasizes teamwork.[4]

Scrum is occasionally seen written in all-capitals, as SCRUM.[5] While the word itself is not an acronym, its capitalized styling likely comes from an early paper by Ken Schwaber[6] that capitalized SCRUM in its title.[7][8]

While the trademark on the term scrum itself has been allowed to lapse, it is now deemed as a generic trademark owned by the wider community rather than an individual.[9]

Many of the terms used in scrum literature are typically written with leading capitals (e.g., Scrum Master, Daily Scrum), but in many cases should not be capitalized if they are common nouns. To maintain correct grammar, this article uses normal sentence case for these terms (e.g., scrum master, daily scrum) – unless they are recognized marks (such as Certified Scrum Master and Professional Scrum Master).

Key ideas

Scrum is a lightweight, iterative and incremental framework for developing, delivering, and sustaining complex products.[10][11] The framework challenges assumptions of the traditional, sequential approach to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines involved.

A key principle of scrum is the dual recognition that customers will change the scope of what is wanted (often called requirements volatility[12]) and that there will be unpredictable challenges β€” for which a predictive or planned approach is not suited. These changes come from a variety of sources, but according to scrum, understanding why is irrelevant, and change should simply be accepted, embraced and analyzed for benefits.

As such, scrum adopts an evidence-based empirical approach – accepting that the problem cannot be fully understood or defined up front, and instead focusing on how to maximize the team's ability to deliver quickly, to respond to emerging requirements, and to adapt to evolving technologies and changes in market conditions.

Example: Technology Article – Wikipedia

Fabrice
Batch Capricon
trainee at Archis Academy

Top comments (0)

🌚 Life is too short to browse without dark mode