---
title: "What is a Sprint?"
canonical: https://wavect.io/glossary/sprint/
language: en
description: "A fixed-length unit of work (usually 1 to 2 weeks) at the end of which a shippable increment is delivered and reviewed."
image: "https://wavect.io/img/general/bak/open_graph_preview.jpg"
---

ENGAGEMENT

# Sprint

A fixed-length unit of work (usually 1 to 2 weeks) at the end of which a shippable increment is delivered and reviewed.

Last reviewed: 2026-05-24 by [Kevin Riedl](/team/kevin-riedl/) [wiki ↗](https://www.wikidata.org/wiki/Q139796365)

Sprint is a Scrum-specific term that has leaked into general usage to mean any short, time-boxed unit of work. The original definition requires three things: a fixed length, a planning session at the start, and a review at the end. Most teams keep the first two and drop the third, which is why a lot of teams call their cadence “sprints” but produce no demonstrable increment. A sprint without a demo is just a deadline; a sprint without a retro is a treadmill.

The duration matters. One-week sprints force tight scope and surface delivery problems fast. Two-week sprints give more room for substantial work but absorb more drift. Three-week sprints almost always become two badly-planned ones.

Worked example of the silent failure: a team runs two-week “sprints” for six months, hits every planning meeting, and ships nothing a stakeholder can click on. The board keeps slipping because work is sized by hope, not by what fits, and there is no review forcing the team to confront a working increment. The fix is brutal and simple: at the end of every sprint, someone outside the team has to be able to use what was built. If they cannot, the cadence is theatre, and shrinking to one-week sprints usually exposes why within a fortnight.

The honest trade-off and the most common founder mistake: treating sprints as a way to hit a fixed external deadline. The cadence is built around fixing the time-box and flexing the scope, which is the opposite of a hard launch date with fixed scope. For genuinely date-driven, fixed-scope work you want a fixed-price plan with explicit [SDLC](/glossary/sdlc/) milestones, not a sprint board. Sprints fit ongoing [agile](/glossary/agile/) delivery and iterative work toward an [MVP](/glossary/mvp/); they fit research and design work poorly, where a time-boxed exploration with a written summary beats a forced demo. They also depend on [CI/CD](/glossary/ci-cd/) being healthy, because a sprint that cannot ship at its end is not a sprint.

**When this matters in a software project.** Any time you are buying ongoing, iterative delivery and want to see working software at a steady cadence rather than one big reveal at the end.

**What founders usually get wrong.** They treat sprints as a way to hit a fixed external launch date, which is exactly backwards: the cadence fixes the time-box and flexes the scope. They also drop the demo and the retro, so they get planning meetings and ship nothing a stakeholder can click on.

**How Wavect handles it.** We keep the demo and the retro, and a working increment someone outside the team can use is the bar at the end of every sprint. For genuinely date-driven, fixed-scope work we plan against explicit milestones instead, as covered in the [QA checklist before launch](/software-development-guide/software-qa-checklist-before-launch/).

// FAQ

## FAQs

### One-week or two-week sprints?

One-week sprints surface delivery problems faster and force tighter scope. Two-week sprints give room for substantial work but absorb more drift. We default to two weeks for most teams, one week when delivery discipline is wobbly.

### Why do most teams' sprints not work?

They drop the review or the retro. A sprint without a demo is just a deadline. A sprint without a retro is a treadmill. If the team cannot show a working increment at the end, the cadence is theatre.

### Do sprints work for research or design work?

Sort of. The cadence helps; the ‘shippable increment’ part rarely does. For research-heavy work, the better unit is a time-boxed exploration with a written summary at the end, not a polished demo.

Related terms

- [Agile](/glossary/agile/)
- [MVP](/glossary/mvp/)
- [CI/CD](/glossary/ci-cd/)
- [SDLC](/glossary/sdlc/)

Related services

- [Custom Software Development](/services/software-development/)

Related case studies

- [Bond Analytics Platform](/case-studies/bond-analytics/)

Related guides

- [Fixed price vs time and materials](/software-development-guide/fixed-price-vs-time-and-materials/)

Talk to us

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://wavect.io/#organization",
      "@type": [
        "Organization",
        "ProfessionalService",
        "LocalBusiness"
      ],
      "employee": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "founder": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "legalRepresentative": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "name": "Wavect GmbH",
      "subjectOf": {
        "@id": "https://wavect.io/verified-claims.json#dataset",
        "@type": "Dataset",
        "creator": {
          "@id": "https://wavect.io/#organization",
          "@type": [
            "Organization",
            "ProfessionalService",
            "LocalBusiness"
          ]
        },
        "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.",
        "inLanguage": "en",
        "isAccessibleForFree": true,
        "license": "https://creativecommons.org/licenses/by/4.0/",
        "name": "Wavect verified publication claims",
        "url": "https://wavect.io/verified-claims.json"
      },
      "url": "https://wavect.io/"
    },
    {
      "@id": "https://wavect.io/team/kevin-riedl/#person",
      "@type": "Person",
      "jobTitle": "Managing Director",
      "name": "Kevin Riedl",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q139796365",
        "https://www.linkedin.com/in/wsdt",
        "https://github.com/wsdt"
      ],
      "url": "https://wavect.io/team/kevin-riedl/",
      "worksFor": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      }
    },
    {
      "@id": "https://wavect.io/team/christof-jori/#person",
      "@type": "Person",
      "jobTitle": "Managing Director",
      "name": "Christof Jori",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q139796367",
        "https://www.linkedin.com/in/jocr77/",
        "https://github.com/jo-chris"
      ],
      "url": "https://wavect.io/team/christof-jori/",
      "worksFor": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      }
    },
    {
      "@id": "https://wavect.io/#website",
      "@type": "WebSite",
      "inLanguage": [
        "en",
        "de",
        "es",
        "zh"
      ],
      "name": "Wavect",
      "potentialAction": {
        "@type": "SearchAction",
        "query-input": "required name=search_term_string",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "https://wavect.io/search/?q={search_term_string}"
        }
      },
      "publisher": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      },
      "url": "https://wavect.io/"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://wavect.io/glossary/sprint/#term",
      "@type": "DefinedTerm",
      "alternateName": [],
      "description": "A fixed-length unit of work (usually 1 to 2 weeks) at the end of which a shippable increment is delivered and reviewed.",
      "inDefinedTermSet": "https://wavect.io/glossary/#termset",
      "name": "Sprint",
      "termCode": "sprint",
      "url": "https://wavect.io/glossary/sprint/"
    },
    {
      "@id": "https://wavect.io/glossary/sprint/#webpage",
      "@type": "WebPage",
      "about": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      },
      "author": {
        "@id": "https://wavect.io/team/kevin-riedl/#person",
        "@type": "Person",
        "name": "Kevin Riedl",
        "url": "https://wavect.io/team/kevin-riedl/"
      },
      "dateModified": "2026-05-24",
      "description": "A fixed-length unit of work (usually 1 to 2 weeks) at the end of which a shippable increment is delivered and reviewed.",
      "headline": "Sprint",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://wavect.io/#website",
        "@type": "WebSite"
      },
      "lastReviewed": "2026-05-24",
      "mainEntity": {
        "@id": "https://wavect.io/glossary/sprint/#term"
      },
      "mentions": [
        {
          "@id": "https://wavect.io/#organization",
          "@type": [
            "Organization",
            "ProfessionalService",
            "LocalBusiness"
          ]
        }
      ],
      "name": "Sprint",
      "reviewedBy": {
        "@id": "https://wavect.io/team/christof-jori/#person",
        "@type": "Person",
        "name": "Christof Jori",
        "url": "https://wavect.io/team/christof-jori/"
      },
      "speakable": {
        "@type": "SpeakableSpecification",
        "cssSelector": [
          ".gls-single__h1",
          ".gls-single__tldr"
        ]
      },
      "url": "https://wavect.io/glossary/sprint/"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "item": "https://wavect.io/",
          "name": "Home",
          "position": 1
        },
        {
          "@type": "ListItem",
          "item": "https://wavect.io/glossary/",
          "name": "Tech, product & engagement glossary",
          "position": 2
        },
        {
          "@type": "ListItem",
          "item": "https://wavect.io/glossary/sprint/",
          "name": "Sprint",
          "position": 3
        }
      ]
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "One-week sprints surface delivery problems faster and force tighter scope. Two-week sprints give room for substantial work but absorb more drift. We default to two weeks for most teams, one week when delivery discipline is wobbly."
      },
      "name": "One-week or two-week sprints?"
    },
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "They drop the review or the retro. A sprint without a demo is just a deadline. A sprint without a retro is a treadmill. If the team cannot show a working increment at the end, the cadence is theatre."
      },
      "name": "Why do most teams' sprints not work?"
    },
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Sort of. The cadence helps; the 'shippable increment' part rarely does. For research-heavy work, the better unit is a time-boxed exploration with a written summary at the end, not a polished demo."
      },
      "name": "Do sprints work for research or design work?"
    }
  ],
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      ".faq-question",
      ".faq-answer"
    ]
  }
}
```