What to ask before commissioning software development
By TechDriven Solutions · · 2 min read
Review business rules, access, background work, deployment, and handover before starting an application feature or modernization project.
The decision to make
A development engagement should explain how business rules, access, failure, and deployment will be verified. Start with the outcome your users need.
Describe the rule that must survive the change
A list of technical tools does not define an application. Start with a task and its rules: who can submit, approve, reverse, or export a record? What should happen when information is missing? Which existing behavior must remain compatible? For an established product, these questions matter before discussing a rewrite.
Use an anonymized record and walk through the real sequence. Record exceptions and side effects such as notifications or third-party updates. Ask the developer to explain how the proposed change fits the existing code rather than assuming a technical upgrade alone solves the business problem.
Ask about delayed and repeated work
Emails, imports, and integrations may run outside the original request. Decide how a user knows a task is pending, how failure is detected, and whether repeating it creates a duplicate business action. A development scope should include the operator's recovery path when that work is important.
For an upgrade, establish a representative baseline before changing dependencies. Test the affected workflow and integrations, not only whether the application starts. Keep a list of known limitations so a release does not imply that unrelated historical issues were fixed.
- What can be retried safely?
- Where are failed jobs or integrations visible?
- Which configuration and worker processes are required?
- Who investigates after deployment?
Make deployment and handover part of acceptance
Ask how configuration, generated assets, scheduled work, and writable storage behave on the target host. A local demonstration does not prove that the deployed runtime has those requirements. Review the actual release path in an agreed environment.
A useful handover includes source, setup and release instructions, relevant tests, required services, and unresolved risks. If you want maintenance after release, agree the hours and responsibility separately. Start with a bounded change that lets you assess this process before committing to a larger application program.
Primary references
Official documentation for the technical principles discussed above. Check the documentation that matches your application when planning implementation.
Continue with your scope
Have a task to discuss?
Send the workflow, current system, and constraints. An anonymized example is enough to begin a scope conversation.
Discuss the work