Iterative framework for complex product development with defined roles, events and artifacts.
Scrum is a framework for developing complex products where requirements are not fully known at the outset. It is based on empirical process control: rather than planning everything in advance, the team works in short iterations, inspects the results, and adapts course. The three pillars of transparency, inspection, and adaptation form the foundation.
In practice, Scrum consists of three roles (Product Owner, Scrum Master, Development Team), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). The team works in fixed Sprints of one to four weeks and delivers a potentially shippable product increment at the end of each Sprint. A typical two-week rhythm begins on Monday with Planning, includes daily stand-ups, and closes on Friday with Review and Retrospective. This structure creates predictability and regular feedback loops.
Scrum was introduced in 1995 by Ken Schwaber and Jeff Sutherland and is documented in the Scrum Guide. The framework is deliberately lightweight and prescribes very little, which in practice is both its strength and its challenge: teams must fill the gaps with suitable practices themselves.
Apply methods, don't just know them. View trainings and workshops
