15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Project

Free Programming and Tech Demo Project Template

A programming and tech demo project covers the work stages from discovery through release and handover, with cards for the tasks in each phase.

Menlo Works - Programming and Tech Demo Project template preview

Language:

en

Last updated:

September 2026

Share template

Modernising a legacy system tends to come with one hard requirement: the business can’t wobble while the code changes. The worry isn’t the rewrite, it’s the week where invoicing, dispatch, or payments fall over because a dependency got missed. This programming and tech demo project gives the work a staged path, so the risky parts get named early and move forward in an order that protects what’s already live, on a tweed-teal board under Lora headings.

The columns move from Discovery and audit into Strategy and design, then through Extraction and replatforming and Data migration rehearsal before Release and harden and Handover and close. Each column holds the cards for that phase, including codebase and integration audits, an API contract for legacy apps, CI/CD work for legacy repos, migration rehearsal with rollback, and post-cutover verification that reconciles transactions.

  • Discovery and audit This column holds the audit and inventory cards, including the codebase review, dependency and integration mapping, and build and runtime environment inventory.
  • Strategy and design This column covers the planning cards: the cloud re-platform plan, strangler rollout design, the API layer contract for legacy apps, and the database migration and refactor plan.
  • Extraction and replatforming This column tracks the build work, from extracting services out of the monolith to rebuilding interfaces behind existing endpoints, re-platforming components, and implementing CI/CD for legacy repos.
  • Data migration rehearsal This column runs the migration rehearsal as a set of cards, including the rollback plan, production parity checks, and the cutover runbook documentation.
  • Release and harden This column covers the staged cutover and hardening steps, including environment parity checks and post-cutover verification that reconciles transactions.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What is on this board

6 columns carrying 22 cards. Adding it builds the whole thing as a project in your workspace, with every column and card in place.

ColumnWhat is in it

Discovery and audit

This column holds the audit and inventory cards, including the codebase review, dependency and integration mapping, and build and runtime environment inventory.

  • Run legacy system codebase audit
  • Map external dependencies and integrations
  • Inventory build and runtime environments

Strategy and design

This column covers the planning cards: the cloud re-platform plan, strangler rollout design, the API layer contract for legacy apps, and the database migration and refactor plan.

  • Draft re-platform plan for cloud
  • Design strangler pattern rollout for core modules
  • Define API layer contract for legacy apps
  • Produce database migration and refactor plan

Extraction and replatforming

This column tracks the build work, from extracting services out of the monolith to rebuilding interfaces behind existing endpoints, re-platforming components, and implementing CI/CD for legacy repos.

  • Extract service modules from monolith
  • Build API layer for legacy apps
  • Rebuild interfaces behind existing endpoints
  • Re-platform application components to cloud environments
  • Implement CI/CD pipelines for legacy repos

Data migration rehearsal

This column runs the migration rehearsal as a set of cards, including the rollback plan, production parity checks, and the cutover runbook documentation.

  • Run data migration rehearsal with rollback plan
  • Validate migrated datasets against production parity checks
  • Document rollback and cutover runbook

Release and harden

This column covers the staged cutover and hardening steps, including environment parity checks and post-cutover verification that reconciles transactions.

  • Execute staged cutover to services and migrated database
  • Harden release pipeline and environment parity checks
  • Run post-cutover verification and reconcile transactions

Handover and close

This column closes the work out with runbooks, knowledge transfer with the operations team, maintenance cadence and monitoring alerts, then repository archiving.

  • Deliver runbooks and operational documentation
  • Run knowledge-transfer sessions with operations team
  • Set up maintenance cadence and monitoring alerts
  • Close project and archive repositories

What happens when you install it

  • A project is created with its board, 6 columns and 22 cards already there.
  • Nothing carries a due date, because a board holds the order the work runs in rather than a calendar. The dates go on once you know when the job starts.
  • Every card opens as a task with its own description, assignee, dates, subtasks and files, and columns are renamed, reordered or deleted like any other.

Who it is for

Software teams and consultants doing legacy modernisation work where uptime matters, including API & integrations work and custom software re-platforming.

Questions about this project template

Can you modernise a legacy system without stopping day-to-day operations?

That’s the point of a staged approach, where discovery, design, extraction, rehearsal, and cutover get treated as separate phases instead of one big switch. The board keeps those phases visible so the riskier steps don’t get hidden inside a single “rewrite” task.

What happens if the data migration goes wrong on cutover night?

The Data migration rehearsal column includes a rollback plan and parity checks before any cutover work. The same phase also carries a cutover runbook, so the team can follow a written sequence instead of improvising under pressure.

How do you handle a system nobody has fully documented?

The Discovery and audit column starts with a codebase audit plus mapping dependencies and integrations. That work turns unknowns into a concrete inventory before the API contract, migration plan, or extraction work begins.

What work needs to happen before you start extracting services from a monolith?

The board puts discovery and design ahead of extraction, so the codebase and dependency mapping come first and the rollout plan gets written before modules get pulled out. That ordering matters because interfaces get rebuilt behind existing endpoints as part of extraction.

What should be defined before you build an API layer for legacy apps?

The Strategy and design column includes the API layer contract for legacy apps. That contract gives the extraction and replatforming work a target, so the API work doesn’t drift while other modules change.

What do you need from our people week to week during a re-platforming project?

The board needs whoever is doing the work added to the project and assigned to the cards, so ownership stays clear across phases. Dates also need to be added separately, since the columns show order rather than a calendar.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away