// PROCESS GUIDE
A software development process from idea to release.
The software development process is the set of decisions and activities a team uses to understand a need, plan and build software, check its quality, release it, and support it over time.
These SDLC phases can repeat and overlap. The right level of process depends on product risk, scope, and how quickly the team needs feedback.
Seven stages
- 01
Discovery
Understand users, goals, constraints, and risks.
- 02
Planning
Sequence work and make scope, dependencies, and decisions visible.
- 03
Design
Make user journeys, interfaces, and technical approach concrete.
- 04
Development
Implement the agreed product increments with reviewable changes.
- 05
QA
Check agreed behaviour, risks, and release readiness.
- 06
Launch
Release with appropriate checks, ownership, and monitoring.
- 07
Support
Maintain the product and use feedback to guide improvements.
Deliverables and ownership by stage
| Stage | Purpose and deliverables | Participants | Typical duration |
|---|---|---|---|
| Discovery | Understand users, goals, constraints, and risks. Problem statement, user needs, assumptions, and initial scope. | Client: product owner and subject experts. NUMVOX: product and engineering representatives. | 3–5 days |
| Planning | Sequence work and make scope, dependencies, and decisions visible. Prioritised backlog, milestones, estimates, and risk register. | Client: decision maker and product owner. NUMVOX: delivery lead and engineers. | 2–4 days |
| Design | Make user journeys, interfaces, and technical approach concrete. Flows, prototypes or specifications, architecture decisions, and acceptance criteria. | Client: users and approvers. NUMVOX: product/design and technical roles. | 1–2 weeks |
| Development | Implement the agreed product increments with reviewable changes. Working software, reviewed code, and updated technical notes. | Client: product owner and domain experts. NUMVOX: engineering team. | 3–8 weeks, in weekly increments |
| QA | Check agreed behaviour, risks, and release readiness. Test results, defects, regression evidence, and release recommendation. | Client: product approvers. NUMVOX: QA and engineering roles. | 1–2 weeks, running alongside development |
| Launch | Release with appropriate checks, ownership, and monitoring. Deployment plan, release notes, access handover, and rollback approach. | Client: system owner and approvers. NUMVOX: delivery and engineering roles. | 2–3 days |
| Support | Maintain the product and use feedback to guide improvements. Support plan, prioritised backlog, maintenance work, and agreed reporting. | Client: product owner and operations. NUMVOX: agreed support roles. | Ongoing, on a monthly plan |
Change, quality, and security
Change requests are reviewed for user value, scope, dependencies, risk, and delivery impact before priorities or estimates are updated. QA and security considerations run through every stage: requirements and threat context inform design, implementation uses agreed reviews, and verification and release checks match the product risks. Exact practices should be agreed for the engagement.
What we need from the client
- A product owner or decision maker available for timely decisions.
- Access to users, domain knowledge, systems, and relevant constraints.
- Clear ownership of acceptance, business priorities, and launch approval.
- Timely access to approved environments, data, and third-party contacts.
For a broader explanation of lifecycle terminology, read What is the software development life cycle?
Related services
Related ways we can help
Insights
Helpful reading
Plan your next release with a clear process.
Project enquiry
Discuss your delivery process
We read each brief and reply by email. Do not include passwords or sensitive personal data.