Glossary · project-management
Scrum
Definition
Scrum is the framework that makes Agile concrete. Work is split into 1-4 week sprints; roles are Product Owner (what to build), Scrum Master (how to work together), and Development Team. Daily standup, sprint review, and retrospective are core ceremonies.
Detailed explanation
Scrum was formalized in the 1990s by Ken Schwaber and Jeff Sutherland. Core elements: Sprint (1-4 week dev cycle), Product Backlog (full to-do list, owned by PO), Sprint Backlog (this sprint's work), Increment (delivered working software).
Roles: Product Owner maximizes business value, manages the backlog. Scrum Master ensures framework adherence and removes blockers. Development Team self-organizes, cross-functional. Scope does not change mid-sprint.
Scrum in Turkey: 2-week sprints most common. Jira + Confluence most popular tools. PSM certification $200; CSM from Scrum Alliance. Common failure: Scrum ceremonies exist but PO isn't dedicated.
Use cases
→Software sprint planning
→SaaS feature development
→Agency + client project management
→Startup team organization
→Remote development team coordination
Pros
- +Concrete delivery each sprint
- +Transparency (everyone knows what's done)
- +Fast prioritization
- +Retrospective drives process improvement
Cons
- −Blocks if PO isn't full-time
- −Daily standup wastes time if unmanaged
- −Long-range planning is hard
- −Scaling for large teams (may need SAFe)
Related terms
Related services
Planning a project around Scrum?
In a 30-minute discovery call we share a written architecture + cost + team recommendation tailored to your project.
Start a discovery call