Worklenz
Sign in
EN

Software & IT template

Software Development Template

Plan and deliver a software project in sprints: requirements, technical design, iterative development, testing, release and early support.

Worklenz has a built-in Software Development template you can pick during setup, then shape it to match this plan.

  • Free plan available
  • Open source (AGPL-3.0)
  • Cloud or self-hosted
Developers planning a software project on a whiteboard

What's included in the Software Development template

phases
6
tasks
18
labels
5
statuses
3
1. Requirements · 3 tasks
  • Agree goals and scopeWhat the software must achieve, for whom, and what is out of scope.
  • Write user storiesDescribe features as stories with clear acceptance criteria.
  • Prioritise the backlogOrder stories by value and risk, and agree the first release.
2. Design · 3 tasks
  • Plan the architectureChoose the stack, data model and integrations, and record key decisions.
  • Design screens and flowsWireframes or designs for the main user flows.
  • Set up environments and CIRepositories, development and staging environments and automated builds.
3. Development · 4 tasks
  • Sprint planningChoose the stories for the sprint based on priority and capacity.
  • Build featuresDevelop stories against their acceptance criteria.
  • Code reviewReview every change before it is merged.
  • Sprint review and retrospectiveDemo finished work and agree one improvement for the next sprint.
4. Testing · 3 tasks
  • Automated testsUnit and integration tests run on every change.
  • QA testingTest stories against acceptance criteria on staging.
  • User acceptance testingThe client or product owner confirms the release meets the requirements.
5. Release · 2 tasks
  • Prepare the releaseRelease notes, data migrations and a rollback plan.
  • Deploy to productionDeploy, run smoke tests and monitor errors.
6. Support · 3 tasks
  • Monitor and fix early issuesWatch errors and user feedback in the first weeks and fix urgent bugs.
  • Hand over documentationTechnical documentation, credentials and a support plan for the client.
  • Plan the next releaseReview the backlog and agree what comes next.

Labels

  • Feature
  • Bug
  • Tech debt
  • Blocked
  • Ready for QA

Who this template is for

  • Software agencies and dev shops building products for clients
  • In-house product and engineering teams shipping new features
  • Small teams that want light structure without heavy process

When to use a software development template

Software projects go wrong in familiar ways: unclear requirements, a backlog that never gets prioritised, testing squeezed at the end and a release with no rollback plan. A template does not replace engineering judgement, but it keeps the important steps in view so they are not skipped under pressure.

Use it for building a new application, a significant new feature or a client software project. It works for agile teams running sprints and for teams with a more traditional delivery plan.

How the template is structured

  1. Requirements. Agree goals and scope, write user stories with acceptance criteria and prioritise the backlog.
  2. Design. Plan the architecture, design the main flows and set up environments and automated builds before feature work starts.
  3. Development. Run sprints with planning, building, code review and a sprint review with a retrospective.
  4. Testing. Automated tests on every change, QA against acceptance criteria and user acceptance testing.
  5. Release. Prepare release notes, migrations and a rollback plan, then deploy and monitor.
  6. Support. Fix early issues, hand over documentation and plan the next release.

Labels such as Feature, Bug and Tech debt help you balance new work with maintenance.

How to use it in Worklenz

  1. Start from the built-in Software Development template during setup, or create a project with these phases and tasks.
  2. Add one task per user story and use subtasks for technical steps.
  3. Run sprints on the kanban board, moving stories from to do through review to done.
  4. Make sprint ceremonies recurring tasks on the Pro plan and above.
  5. Track time per story on the Pro plan and above to improve estimates.

Making development work visible and billable

Software agencies often sell projects on estimates, and estimates are only as good as the data behind them. Time tracking per story shows how long work really takes, which makes the next estimate better. On the Business plan, project finance compares the budget with the cost of logged time, and the client portal gives clients a place to raise requests and bugs.

Example: building a client booking app

A dev agency is building a booking app for a fitness studio. Requirements produce 30 user stories, and the client agrees a first release with booking, payments handled by an existing provider and reminders. The team sets up staging and automated builds in the first week, then runs two-week sprints.

Each sprint ends with a demo to the client. QA tests every story on staging, and the studio manager runs acceptance testing before release. The release includes a rollback plan, which is not needed. In the first two weeks after launch, the team fixes three minor bugs and plans the second release with the client.

Keeping scope under control

Scope changes are normal in software projects; the problem is changes nobody tracks. Add every new request to the backlog as a story, estimate it and let the product owner decide what it replaces or whether the timeline moves. For client projects on a fixed budget, label new requests clearly and agree them in writing before work starts. Reviewing the backlog at every sprint planning keeps the trade-offs visible to everyone, so the end of the project holds no surprises.

Who should be involved

A product owner or client representative owns priorities and acceptance. A tech lead owns architecture and code quality. Developers build and review, and a QA engineer owns testing. A project manager or delivery lead keeps scope, timeline and client communication on track. In small teams, one person may hold several of these roles.

Common software project mistakes

The first mistake is starting development before acceptance criteria are written, which makes “done” a matter of opinion. The second is leaving testing to the end. The third is releasing without a rollback plan. This template builds each of these into the plan.

Tips for smoother software projects

  • Write acceptance criteria for every story. They make testing and sign-off simple.
  • Set up CI before features. Automated builds catch problems early.
  • Demo every sprint. Regular demos prevent surprises at the end.
  • Always plan a rollback. You will rarely need it, but when you do, it matters.

Related: the bug tracking template and the quality assurance testing template.

Start your software development project in Worklenz

Sign up free, then set up the phases and tasks above for your team.

Software Development template FAQs

What are the phases of a software development project?

Requirements, design, development, testing, release and support. Many teams run development and testing in short sprints, which this template supports.

Can I use this template for agile or Scrum?

Yes. The development phase includes sprint planning, code review and a sprint review and retrospective. Make sprint ceremonies recurring tasks on the Pro plan and above.

Is this software development template free?

Yes. The full template is on this page, and Worklenz's free plan includes task lists, kanban boards and built-in project templates.

Does Worklenz integrate with GitHub?

A GitHub integration is part of Worklenz version 3.4. Check your plan and version for availability.

Software & IT

Bug Tracking template

A simple bug tracking workflow: capture clear reports, triage and prioritise, fix with review, verify and close, then learn from patterns.

5 phases · 15 tasks. By Worklenz.

Software & IT

E-commerce Development template

Build or rebuild an online store: discovery, platform and design, product catalogue, checkout, payments and shipping, testing and a launch that protects sales.

6 phases · 19 tasks. By Worklenz.

Software & IT

IT Project template

Plan an IT project such as a system rollout, upgrade or migration: assess needs, plan and procure, implement, roll out to users and hand over to support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Data Migration template

Move data between systems safely: assess and map the data, clean it, run test migrations, cut over with a rollback plan and validate the results.

6 phases · 17 tasks. By Worklenz.

Software & IT

QA Testing template

Plan and run software QA: define scope and approach, write test cases, prepare environments, execute tests, track defects and sign off the release.

5 phases · 15 tasks. By Worklenz.

Software & IT

Security Assessment template

Run a security assessment from scope to remediation: inventory assets, review risks and controls, test for vulnerabilities, report findings and track fixes to closure.

6 phases · 17 tasks. By Worklenz.

Explore more templates

Run your next project from a template

Worklenz is an open-source platform for agencies and service teams: projects, time tracking and client work in one place.