Describe the concern before choosing the review
A development audit is useful when you need an independent view of how software is specified, built, tested and released. Begin with the decision: which practices need attention, what evidence is missing, or what should be checked before a change? A concern is a starting question, not a finding.
- Requirements change, but their approval and impact are hard to trace.
- The evidence supporting release decisions is unclear.
- Responsibilities between development, testing and production support need clarification.
Trace one requirement through the process
Choose representative work within the agreed scope. Follow the requirement into a design decision, a code change, tests and a release. Check how acceptance criteria, review records and deployed versions connect. This can show whether the process produces a record that the relevant people can understand and use.
Review controls where decisions happen
Examine who approves changes, how code review works and which test results support a release. Consider build and deployment controls, dependencies, environment configuration and recovery arrangements where relevant. Judge practices against the agreed questions and criteria. Record limitations in the available evidence and avoid treating a written procedure as proof of execution.
Connect findings to responsibility
Discuss technical findings with the people who own the process and its business consequences. Recommendations should state the reason, dependencies and a way to verify the change. The client decides responsibilities and implementation. A focused improvement plan should help teams choose the next action without implying that every practice needs replacement.
Prepare for the first conversation
Start with the general concern, the type of system and the decision you need to make. We agree scope, confidentiality and access before technical materials are shared. I personally conduct the assessment and reporting, with no delegation. Selected implementation changes can be checked in an agreed follow-up review.