Key tips for a successful software development project

Most failed software projects don’t fail because of the code. They fail because the problem was unclear, nobody saw the work until it was too late, or security and testing were left to the end. These tips help you avoid that, whether you build in-house or hire a team.

1. Start with the problem, not the features

Write one paragraph on who has the problem, what it is, and how you’ll know it’s solved. A long list of features is not a plan. A clear problem lets everyone make good decisions when something unexpected comes up.

2. Talk to real users first

Spend time with the people who will use the software. Watch how they work today. You’ll find the real priorities, and the features nobody actually needs.

3. Build the smallest useful version first

Launch the smallest version that solves the main problem, then improve it from real use. It’s faster, cheaper and less risky than building everything and hoping people like it.

4. See progress every two weeks

Work in short cycles, ideally two weeks, and see working software at the end of each one. You’ll spot misunderstandings early, when they’re cheap to fix, and you can change priorities as you learn.

5. Use a clickable prototype before coding

A prototype that people can click through costs a fraction of the real build and answers most design questions before a line of code is written.

6. Make security part of the build

Security added at the end is expensive and patchy. Build it in from the start: safe handling of passwords and personal data, two-factor login for admins, checks on every input, and a security test before launch.

7. Test automatically

Automatic tests catch problems every time the code changes, so new features don’t quietly break old ones. Monitoring catches problems once you’re live.

8. Plan for growth, but don’t over-build

Choose tools and a setup that can grow, without paying today for millions of users you don’t have yet. Good foundations are boring and dependable.

9. Own your code

Make sure your contract says you own the code and the idea, and that you have full access to the source code, the hosting accounts and the documentation. If you ever change supplier, you should be able to carry on without starting again.

10. Plan life after launch

Software needs updates, security fixes, monitoring and small improvements. Agree who looks after it once it’s live, and budget for it.

How we work

We plan with your users, build a clickable prototype, then build in two-week cycles with working software at every review. Security and automatic testing come from day one, and you own all the code. Our own apps, including Pot of Food on the App Store and Google Play, are built and run the same way.