Workflow template

Sprint Board for Nextcloud Deck as a normal Nextcloud Deck board.

A sprint board for Nextcloud Deck with an ordered backlog, acceptance criteria written before the sprint, one card in progress per person, and a review against those criteria.

Last verified

Board preview

Sprint

Backlog1

Keep the backlog ordered, not complete

The top ten cards need to be right. Everything below that can stay rough.

Chore

Sprint2

Write acceptance criteria before the sprint starts

A card without acceptance criteria will be argued about on the last day instead of the first.

  • State what a reviewer must see to accept it
  • Note what is explicitly not included
  • Flag anything that depends on another card
Feature

Commit to what the team can actually finish

Base the commitment on what you finished last sprint, not on what you hope for this one.

Featuredue in 14 days

In Progress1

One card in progress per person

Two cards in progress means one of them is really waiting. Move it to Blocked and say why.

Blocked

Review1

Review against the acceptance criteria

Review the card that was agreed, not the code that happens to be there.

  • Check every acceptance criterion is met
  • Run it yourself rather than reading it only
  • Raise a new card for anything out of scope
Bug

Done1

Demo what actually works

Show the running result. A status update is not a demo.

Feature
FeatureBugChoreBlocked
View the portable v1 template JSON
{
  "schema": "deckloud-template-v1",
  "schemaVersion": 1,
  "slug": "sprint-board-nextcloud-deck",
  "locale": "en",
  "title": "Sprint Board for Nextcloud Deck",
  "description": "A sprint board with an ordered backlog, acceptance criteria written up front, and one card in progress per person.",
  "category": "software",
  "tags": [
    "sprint",
    "agile",
    "team"
  ],
  "quickCreateStackKey": "backlog",
  "compatibility": {
    "requiresBoardCreate": true,
    "includesAttachments": false,
    "includesComments": false
  },
  "board": {
    "title": "Sprint",
    "color": "4F46E5"
  },
  "labels": [
    {
      "key": "feature",
      "title": "Feature",
      "color": "3B82F6"
    },
    {
      "key": "bug",
      "title": "Bug",
      "color": "EF4444"
    },
    {
      "key": "chore",
      "title": "Chore",
      "color": "64748B"
    },
    {
      "key": "blocked",
      "title": "Blocked",
      "color": "F59E0B"
    }
  ],
  "stacks": [
    {
      "key": "backlog",
      "title": "Backlog",
      "order": 1
    },
    {
      "key": "sprint",
      "title": "Sprint",
      "order": 2
    },
    {
      "key": "in-progress",
      "title": "In Progress",
      "order": 3
    },
    {
      "key": "review",
      "title": "Review",
      "order": 4
    },
    {
      "key": "done",
      "title": "Done",
      "order": 5
    }
  ],
  "cards": [
    {
      "stack": "backlog",
      "title": "Keep the backlog ordered, not complete",
      "description": "The top ten cards need to be right. Everything below that can stay rough.",
      "labels": [
        "chore"
      ]
    },
    {
      "stack": "sprint",
      "title": "Write acceptance criteria before the sprint starts",
      "description": "A card without acceptance criteria will be argued about on the last day instead of the first.\n\n- [ ] State what a reviewer must see to accept it\n- [ ] Note what is explicitly not included\n- [ ] Flag anything that depends on another card",
      "labels": [
        "feature"
      ]
    },
    {
      "stack": "sprint",
      "title": "Commit to what the team can actually finish",
      "description": "Base the commitment on what you finished last sprint, not on what you hope for this one.",
      "labels": [
        "feature"
      ],
      "dueOffsetDays": 14
    },
    {
      "stack": "in-progress",
      "title": "One card in progress per person",
      "description": "Two cards in progress means one of them is really waiting. Move it to Blocked and say why.",
      "labels": [
        "blocked"
      ]
    },
    {
      "stack": "review",
      "title": "Review against the acceptance criteria",
      "description": "Review the card that was agreed, not the code that happens to be there.\n\n- [ ] Check every acceptance criterion is met\n- [ ] Run it yourself rather than reading it only\n- [ ] Raise a new card for anything out of scope",
      "labels": [
        "bug"
      ]
    },
    {
      "stack": "done",
      "title": "Demo what actually works",
      "description": "Show the running result. A status update is not a demo.",
      "labels": [
        "feature"
      ]
    }
  ]
}

01

When to use this board

For teams running fixed-length sprints who keep arguing on the last day about whether something is finished. Acceptance criteria are written before the sprint starts, the commitment is based on what was actually finished last time, and one card in progress per person keeps the board honest.

02

How to run this board

  • Order the top of the backlog.

    Keep the top ten cards in Backlog accurate and leave the rest rough.

  • Plan the sprint from last sprint's result.

    Write acceptance criteria on each card in Sprint and commit only to what the team finished last time.

  • Review against the criteria and demo.

    Check each card in Review against its criteria, then show the running result before moving it to Done.

03

What this creates

5 stacks, 4 board labels, and 6 starter cards carrying 6 checklist steps. Attachments and comments are intentionally omitted so the template stays portable.

04

Why it fits Deckloud

The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.

05

Safe import rules

IDs are not stored. Stack and label keys are remapped at creation time, due dates use relative offsets instead of stale fixed dates, and checklists are written into the card description as ordinary Markdown task lists.

FAQ

Practical questions

Does this change my Nextcloud server schema?

No. It creates ordinary boards, stacks, labels, and cards through the normal Deck model.

Does the template include comments or attachments?

No. V1 templates are text-only because comments imply authorship and attachments vary by server/version.

Can I edit the board after creating it?

Yes. After creation it is just a normal Nextcloud Deck board.

Why write acceptance criteria before the sprint?

Criteria agreed up front turn the review into a check. Criteria invented at review time turn it into a negotiation.

Does this assume a specific agile method?

No. The stacks are plain states. It works with Scrum vocabulary, but nothing on the board requires ceremonies or estimates.

Get Deckloud

Work with your Nextcloud Deck boards natively

Get Deckloud for iPhone and iPad, or the desktop app for Mac, Windows, and Linux. Your boards, cards, and due work stay on your own server.