TechSoft
Playbook menu: How the team is organized

Delivery Playbook · Start here

How the team is organized

The client and TechSoft roles in an engagement, and how they work together.

Owner: Delivery Manager · Last reviewed: · Next review: 28 April 2027

Every engagement is a joint team. The client side brings the business goals, access and decisions. Our side brings delivery management, technical leadership, design, engineering, quality and operations. We define roles by responsibility, not headcount. On a small engagement, one person may hold several roles.

Client

  • Client Sponsor
  • Product owner and technical contacts
  • Users and stakeholders

TechSoft delivery team

Leadership

  • Delivery Manager
  • CTO (security, compliance, AI and data)

Design

  • UX/UI Designer
  • Requirements work is shared across the whole team

Engineering

  • Solution Architect / Tech Lead
  • Software Engineers

Quality & operations

  • QA / Test Automation
  • DevOps / Platform
  • Support & Operations

One backlog · one definition of done · one status report

All roles work from the same plan, visible to the client

The client and the team work together every week.

Small engagements combine several roles in one person, but every responsibility is still covered.

Typical team shapes

EngagementTypical teamNotes
Discovery or assessmentDelivery Manager, Designer, Tech Lead (plus the CTO as needed)Short, with senior people
Product buildDelivery Manager, Designer, Tech Lead, 3–6 engineers, QA, DevOps (part-time)Cross-functional, one backlog
ModernizationTech Lead, engineers, QA, DevOps, CTO (security)Starts with assessment and characterization tests
Workflow automationTech Lead, engineers, QA, CTO (AI, data and security)Process owners from the client join workshops
Monthly engineeringDelivery Manager, named engineers, QA, SupportStable team over time

Detailed role descriptions follow in the Roles section.

Related