Process & Design
Scrum is an Agile framework for managing complex work in which cross-functional teams deliver working increments of a product in fixed-length iterations called sprints, guided by defined roles, events, and artefacts.
The three core Scrum roles are the Product Owner (who prioritises the backlog and represents stakeholder interests), the Scrum Master (who removes impediments and facilitates the process), and the Development Team (who self-organises to deliver the sprint goal). Scrum's five events structure the sprint: Sprint Planning (committing to a goal and selecting backlog items), Daily Scrum (a 15-minute synchronisation standup), Sprint Review (demonstrating the increment to stakeholders), Sprint Retrospective (team process improvement), and the Sprint itself (the container for all other events). The Product Backlog is an ordered list of all desired work, and the Sprint Backlog is the subset committed to in the current sprint — both are transparent, inspectable artefacts that drive empirical decision-making. Scrum is not prescriptive about technical practices, making it compatible with any programming language, architecture, or domain.
Example
A six-person development team runs two-week Scrum sprints, holds a 30-minute sprint review every other Friday where the product owner demos new features to the client and collects feedback that reshapes next sprint's priorities.
Related terms
Agile
Agile is a software development philosophy that prioritises iterative delivery, collaboration, customer feedback, and adaptability to change over rigid upfront planning and documentation.
MVP (Minimum Viable Product)
An MVP is the earliest version of a product that includes only the core features needed to deliver value to early adopters and generate validated learning about the market — with everything else deferred.
Version Control
Version control is a system that records every change made to source code over time, enabling teams to track history, revert to previous states, and collaborate on the same codebase simultaneously without overwriting each other's work.
CI/CD (Continuous Integration / Continuous Delivery)
CI/CD is a DevOps practice in which code changes are automatically built, tested, and deployed through a pipeline, enabling teams to deliver software updates rapidly and reliably.
Ready to grow your business?
Tell us what you're building. We'll reply within one business day with a clear next step.