Skip to content

Planning web software

Most project risks arise before the first line of code: with the question of what the software should be able to do, which systems are involved and what happens to the existing data. These texts help with exactly these decisions.

Recommended reading order

  1. Custom web application or standard software?The fundamental decision, with the items that count in both directions.
  2. What does a custom web application cost?The six drivers of effort — and which details make an estimate reliable.
  3. Taking over existing PHP softwareWhen something is already running: what an audit of the existing system examines and delivers.
  4. What is an API?As soon as a second system is involved, this topic determines the effort.
  5. Database and interfaceWhy "just one more field" is not a measure of effort.
  6. Planning roles and permissionsOne of the most consequential early decisions.
  7. Requirements specification and functional specificationWhat you really need to write down before you start.
  8. REST API and webhookThe technical deep dive into interfaces.

A project in the planning stage?

Describe your process and the systems involved. You will receive an assessment with stated assumptions.