Agile Alliance Sizing Spikes

Source identity:

ddx:
  id: resource.agile-alliance-sizing-spikes
  authoring:
    home: repo

Agile Alliance Sizing Spikes

Source

URL: https://agilealliance.org/the-practice-of-sizing-spikes-with-story-points/
Accessed: 2026-05-12

Summary

Agile Alliance published a practitioner discussion arguing that spikes are best handled as time-boxed learning work rather than as value-delivery work hidden inside velocity. The article frames a spike as work aimed at answering a question or gathering information instead of producing shippable product.

Relevant Findings

A spike exists to answer a question or gather information.
Time-boxing keeps uncertainty visible and limits open-ended investigation.
Treating spike effort as normal delivery can obscure how much user value is actually being produced.
Spike results should make planning and estimation more honest, not make progress metrics look better.
Persistent spikes can reveal deeper design or technology uncertainty that needs direct attention.

HELIX Usage

This resource informs the Technical Spike artifact. HELIX uses it to keep spikes visibly separate from delivery work and to require a concrete learning result before design or build proceeds.

Authority Boundary

This resource is a practitioner article hosted by Agile Alliance. It supports spike framing and measurement hygiene, but it does not define HELIX planning policy or replace project-specific estimation rules.

Innsigle seal: model-primary by HELIX

The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.

Composition: model-primary
Issuer: HELIX helix
Signing key: ed25519:b0865d76d834a52c48506414d16f4e5a (build key)
Signed source: research/agile-alliance-sizing-spikes.md
Signed: 2026-09-23T14:11:58Z
Content digest: sha256:0437e843…71d89cc8

This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.

Raw attestation JSON

{
  "payload": {
    "innsigle": "1",
    "type": "https://innsigle.dev/claim/colophon/v1",
    "issued_at": "2026-09-23T14:11:58Z",
    "issuer": {
      "id": "helix",
      "name": "HELIX",
      "key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
      "key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
    },
    "subjects": [
      {
        "uri": "https://documentdrivendx.github.io/helix/research/agile-alliance-sizing-spikes/",
        "digest": {
          "alg": "sha256",
          "value": "0437e843210a744c830db8f012a7155c2f7f503f9e7e17a12e3bc04e71d89cc8"
        }
      }
    ],
    "colophon": {
      "schema_version": "1",
      "composition": "model-primary",
      "ingredients": [
        {
          "kind": "model",
          "name": "Claude",
          "role": "draft"
        },
        {
          "kind": "tool",
          "name": "sloptimizer",
          "role": "rewrite"
        },
        {
          "kind": "human",
          "name": "operator",
          "role": "structure-edit"
        }
      ],
      "notes": null
    }
  },
  "payload_encoding": "json",
  "signatures": [
    {
      "key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
      "alg": "ed25519",
      "sig": "ba8kfUakSiUKcWmccf_SivZl0NIon5dypaAVHq4K5ojQYv5wnkg1ou4_lY934MBUqZxTMh2xZcemw1BOQ1ZuBg",
      "signed_at": "2026-09-23T14:11:58Z"
    }
  ]
}

attestation file · issuer keys