One decision-maker
Content and priorities are approved by an identified person. Conflicting feedback is consolidated before moving forward.
THE VELTRISEN APPROACH
The right scope.
The right stages.
From the first enquiry to handover, important decisions are made visible.
AN EXPLICIT PROGRESSION
Each stage leaves
something concrete.
Open each stage to see what is decided and handed over.
01Locate the need
We start with an example use case, the people involved and known constraints. Questions help choose a manageable problem, rather than fill a technology list.
Output: an articulated need and identified unknowns.02Define the release
The proposal specifies screens, data, deliverables, boundaries, price and dependencies. Necessary access, content and external services are listed before agreement.
Output: a written framework you can accept or discuss.03Build and check
A preview or test environment lets you review concrete work. Feedback is consolidated. Any change expanding the scope is discussed before implementation.
Output: a version checked against agreed criteria.04Hand over and explain
Handover lists files, guidance, checks and remaining limits. Production release and possible maintenance are explicitly arranged as needed.
Output: usable deliverables and an understandable next step.WHAT HELPS THE PROJECT FLOW
Clear roles.
Available inputs.
Authorised access
Rights and licences are checked. Tests use ordinary fictional data when that is sufficient.
A chosen next step
Hosting, operation and maintenance are specified. A one-off project does not create an implied subscription.
THE RIGHT NEXT STEP
What would you like
to make simpler?
A context, a constraint, an idea. Let’s use that to choose a realistic first release.
Prepare my project