Software Development Planning Template

Plan software development work from backlog through build, code review and QA, with story points per item.

Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.

Category

Product & Software DevelopmentRoadmapping & Feature Prioritization

Ideal for

Technology & Startups

Columns

Product backlog → Sprint backlog → In progress → Code review → QA → Done

Sample cards

7

Custom fields

Story points, Sprint

Request form

Creates cards in Product backlog

Columns and sample cards

The 6 columns of this board with its 7 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.

  1. Product backlog

    2
    • Spike: choose a background job queuePriority: highSpike
      Story points:
      1
    • User can reset password by emailPriority: mediumStory
      Story points:
      3
      Checklist 0/5: Write acceptance criteria, Estimate, Implement, Write tests, Demo
  2. Sprint backlog

    1
    • Admin audit logStory
      Story points:
      8
  3. In progress

    1 / 5
    • Remove deprecated v1 endpointsPriority: lowTech debt
      Story points:
      5
  4. Code review

    1
    • Rate limiting on public APIPriority: urgentStory
      Story points:
      5
      Checklist 3/4: Reproduce, Root cause, Fix, Regression test
  5. QA

    1
    • Login fails with plus-sign emailsPriority: highBug
      Story points:
      13
  6. Done

    1 · done stage
    • Release notes for 2.0Bug
      Story points:
      1

Labels

Story, Bug, Spike, Tech debt, Blocked

Custom fields

Story points (Single select, on card), Sprint (Text, on card)

Request form: Submit a story or bug · Software Development Planning

Tell us what you need; it lands on the “Product backlog” column of this board. Asks for Title, Description, Priority, Story points, Attachments; each submission becomes a card in Product backlog.

Card templates

User story, Bug

Software Development Planning Template: questions

Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.

Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.

Related templates