Commissioning software is a collaboration. The quality of the result depends not only on the development team, but on how decisions are made, how feedback is given and how responsibilities are shared.
Appoint a clear product owner
Nominate one person on your side with the authority to make day-to-day decisions and the time to do so. Projects slow down when decisions wait for committees or when different people give conflicting instructions.
Share context, not only requirements
Explain why a feature matters, who uses it and what problem it solves. Context lets the development team propose better solutions and spot problems early.
Agree a rhythm
Regular, short check-ins work better than occasional long meetings. Many teams use:
- a brief weekly progress review;
- a demonstration of working software at the end of each phase or sprint;
- a shared place for questions, decisions and documents.
Give feedback on working software
Try features as they are delivered, rather than waiting until the end. Early feedback is cheaper to act on. Be specific: describe what you did, what you expected and what happened.
Manage changes openly
Requirements change as everyone learns. That is normal. Discuss changes, understand their effect on time and cost, and record the decision. Untracked changes are a common cause of budget surprises and disagreement.
Make the people available
Developers often need input from users or subject-matter experts. Plan for their availability, especially during discovery and acceptance testing.
Respect each other’s expertise
You understand your organisation and its users; the development team understands technology and delivery. The best outcomes come when both perspectives shape decisions.
Keep ownership clear
From the start, agree who owns the source code, accounts, domains, hosting and data, and make sure credentials and documentation are held by your organisation.
Plan beyond launch
Discuss support, maintenance, hosting and future improvements before launch, so the system has a clear owner and a plan for its next stage.
A good partnership is built on clarity, trust and regular communication. With those in place, even complex projects become manageable.
