Skip to content

Scrum

Scrum is a process-oriented approach that helps you manage projects iteratively. Work is done in short sprints with clear goals, followed by evaluation and adjustment. For example, if you are developing an interactive installation with sensors and visuals, Scrum allows your team to build a basic version in one sprint, test it with users, and then improve it in the next sprint.

Why is this relevant to you as a Creative Technologist? Because your projects often combine design, coding, and hardware. Scrum provides structure without limiting creativity. By making progress visible, distributing responsibility across the team, and reflecting regularly, you can adapt quickly and keep complex projects manageable.

Starting Points

  • Explore the basics of Scrum: What is Scrum?
  • Start with a product backlog: a list of features or user stories that describe what the project should achieve.
    Example: “As a visitor, I want to wave my hand to trigger a light effect, so that I feel part of the installation.”
  • Plan a short sprint (1–2 weeks) with clear goals, such as building the first prototype interaction.

Key Points

  • You work in short iterations (sprints) with predefined tasks and goals. After each sprint, you evaluate results in a retrospective and apply lessons learned in the next cycle.
  • You actively maintain a sprint backlog with user stories and tasks. The status of tasks is updated during the sprint, so that progress is transparent for everyone.
  • You take initiative in your role: prepare for stand-ups (share what you did yesterday, what you will do today, and blockers), and contribute ideas during planning and retrospectives.
  • You adapt Scrum to your project: sometimes the sprint output is working code, other times a physical prototype, a design test, or a user study.

Company-Specific Variations

Many companies adapt Scrum to fit their own culture and workflow. A well-known example is the Google Design Sprint: a five-day process that compresses design thinking and Scrum-like iteration into a short, focused sprint. Find more info here.

  • Day 1: Understand and define the challenge.
  • Day 2: Sketch possible solutions.
  • Day 3: Decide which solution to pursue.
  • Day 4: Build a realistic prototype.
  • Day 5: Test the prototype with real users.

This approach is especially useful when you need fast validation of a concept before investing more time and resources.

Other companies might use Kanban boards (continuous workflow, no fixed sprints) or hybrid models that mix Scrum with design methodologies. As a Creative Technologist, it is important to be flexible: learn the principles of Scrum, but also be ready to work with company-specific frameworks.