Skip to content

04 · Velnex Method

A controlled path from requirement to reliable operation.

Six stages, each with defined inputs, outputs and a checkpoint. The method scales from a short definition sprint to a multi-phase platform programme.

Method schematic

  1. Stage 01

    Inspect

    Understand the current operation, goals, users and constraints.

    Gate · Shared understanding of the problem

    Inputs
    Stakeholder interviewsExisting systems and dataBusiness goals
    Outputs
    Current-state mapConstraint list
  2. Stage 02

    Specify

    Define requirements, priorities, risks and success conditions.

    Gate · Scope and success agreed

    Inputs
    Current-state mapUser needsCommercial priorities
    Outputs
    Prioritized requirementsRisk registerSuccess conditions
  3. Stage 03

    Architect

    Plan the experience, system structure, integrations and delivery sequence.

    Gate · Architecture and plan approved

    Inputs
    RequirementsTechnical constraints
    Outputs
    Architecture and decision recordsPrototypesDelivery plan
  4. Stage 04

    Engineer

    Build in focused cycles with demonstrations and testing.

    Gate · Acceptance of each increment

    Inputs
    Delivery planPrioritized backlog
    Outputs
    Working incrementsAutomated testsCycle demonstrations
  5. Stage 05

    Introduce

    Prepare infrastructure, data and teams for release.

    Gate · Release readiness confirmed

    Inputs
    Release candidateMigration plan
    Outputs
    Production environmentMigrated dataTrained users
  6. Stage 06

    Maintain

    Monitor, support and evolve the system.

    Gate · Ongoing health reviews

    Inputs
    Live systemUsage and feedback
    Outputs
    MonitoringService reportsImprovement roadmap

Operating rules

How control is maintained throughout.

R1Checkpoints are approvals
Work moves to the next stage only after you approve the stage output.
R2Demonstrations every cycle
You see working software at the end of each engineering cycle, not only at the end of the project.
R3Decisions are recorded
Significant technical choices are written down with the reasoning and alternatives considered.
R4Risks are visible
A shared risk register is maintained from Inspect through Maintain.

Project workspace concept

The method, visible in one workspace.

Interface concept with example data.

Customer portal rebuild · example project

Interface concept · example data

Delivery phase

04 · Engineer

Inspect

Specify

Architect

Engineer

Introduce

Maintain

Current cycle

Cycle 3 · Billing and notifications

Next demonstration

End of current cycle

Next step

Build a stronger technical foundation.

Tell us what you are creating, replacing or improving. Velnex will help turn it into a practical engineering plan.