Skip to content
Checklist20 review points10 minreviewed 10/08/2026

Get the software project ready to go

A practical test for goal, user journey, data, security and operations before the first development sprint.

For whom
Product managers, departments and project teams before a new application or major expansion.
When to use it
Before the proposal, kickoff or first sprint and again when there is a significant scope change.
THE SHORT ANSWER

A software project is ready to start when the problem, target group, complete core process, success signal, non-goals, data responsibility and operational path are clear enough for a verifiable first version.

Download PDF
01

problem and decision

The application first needs a testable purpose, not the longest possible list of functions.

02

User journey and requirements

The first scope must enable a complete process, even if it remains deliberately small.

03

Data and connections

Unclear data sources and responsibilities quickly become the biggest project risk later on.

04

Security and operations

Security, recovery and accountability belong in the first complete user journey.

05

Start decision

Open points may remain, but must be visibly evaluated and assigned responsibly.

Result of the joint review

  • A clear project mandate with a signal of success
  • A delineated complete user journey
  • A visible risk and assumption register
  • An initial operational and security framework

Sources and professional basis

This working aid translates general recommendations into a compact initial review. The primary sources and your specific context remain decisive.

Frequently asked questions

Do all points have to be completed before the first interview?

No. The checklist just makes it clear which information is missing. However, critical points regarding purpose, responsibility, data and operation should be clarified or deliberately limited before development begins.

Is the checklist a requirement specification?

No. It is a starting test. Specialist models, processes, interfaces and quality requirements are then deepened to suit the project.

Browser checkmarks are not stored or transmitted to sudo/PORT.

Nächster Schritt

Turn open points into a next step

We help prioritise risks and define an appropriate scope for analysis, a project or an immediate measure.

Discuss the checklist