This article was automatically translated from the original Turkish version.
Advantage(s) | Rapid delivery - Flexibility - Transparency - Team focus - Continuous improvement | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Artifacts | Product Backlog - Sprint Backlog - Increment (Product Increment) | ||||||||
Key Events | Sprint: A 1-4 week development cycle. Sprint Planning: The meeting where the sprint is planned. Daily Scrum: A daily 15-minute meeting. Sprint Review and Retrospective: Review and evaluation meetings. | ||||||||
Core Roles | Product Owner: Defines and prioritizes product requirements. Scrum Master: Ensures the process operates correctly. Development Team: The team that builds the product. | ||||||||
Scrum | Scrum is one of the agile software development methodologies. It enables the product to be developed in small parts continuously through short sprints. | ||||||||
Scrum is one of the agile methodologies used in software development and project management. It was defined in the early 1990s by Ken Schwaber and Jeff Sutherland. Scrum is an iterative and incremental approach for managing complex projects and provides an effective work model especially in environments with changing requirements.
Scrum embraces the core values of the Agile Manifesto: individuals and interactions, working software, customer collaboration, and responding to change over following a plan. Scrum is based on three fundamental roles, events, and artifacts:
Scrum is widely adopted in software development common and together; it has also been successfully applied in marketing, product development, education, and even the healthcare sector.
Cohn, Mike. Succeeding with Agile: Software Development Using Scrum. Boston: Addison-Wesley, 2009.
Highsmith, Jim. Agile Project Management: Creating Innovative Products. Boston: Addison-Wesley, 2009.
Pressman, Roger S. Software Engineering: A Practitioner’s Approach. 8. baskı. New York: McGraw-Hill, 2014.
Rubin, Kenneth S. Essential Scrum: A Practical Guide to the Most Popular Agile Process. Boston: Addison-Wesley, 2012.
Schwaber, Ken, and Jeff Sutherland. *The Scrum Guide.* Accessed April 8, 2025. https://scrumguides.org.
Advantage(s) | Rapid delivery - Flexibility - Transparency - Team focus - Continuous improvement | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Artifacts | Product Backlog - Sprint Backlog - Increment (Product Increment) | ||||||||
Key Events | Sprint: A 1-4 week development cycle. Sprint Planning: The meeting where the sprint is planned. Daily Scrum: A daily 15-minute meeting. Sprint Review and Retrospective: Review and evaluation meetings. | ||||||||
Core Roles | Product Owner: Defines and prioritizes product requirements. Scrum Master: Ensures the process operates correctly. Development Team: The team that builds the product. | ||||||||
Scrum | Scrum is one of the agile software development methodologies. It enables the product to be developed in small parts continuously through short sprints. | ||||||||
Definition and Core Principles
Roles
Events
Artifacts
Advantages of Scrum
Application Areas