An outside view of the development team
We interview the people, go through the technology and deliver a report.
What the report covers
The final report is five to twenty pages long, referenced and made for internal use. The focus is agreed case by case. It can include:
- key findings and how critical they are
- development speed and code quality
- version control, project management and responsibilities
- architecture and technical implementation
- how management and the development team communicate
Ask us
Atte PohjanmaaCEO, Board member
atte@vertics.co
044 282 0291
Timo MoilanenOperating Partner, Board member
timo@vertics.co
050 363 7323
How it works
Kick-off meeting
We agree what to focus on.
Interviews with the rest of the organisation
Interviews with the development team
Review of the technology
Code and architecture.
Report
Closing meeting
We go through the recommendations with you.
Who you work with
Experienced Vertics developers and management.
FAQ
When does an audit help?
When management doubts the development pace, when the team grows or shrinks, or when the software needs a thorough review, for example in due diligence.
Does the development team see the report?
You decide. The report is for internal use.
Do we need to prepare anything?
We need access to the code and time for interviews. Anything else is agreed at the kick-off.
Tell us what situation makes you consider an audit.
Book a kick-off meetingTell us about your situation
Tell us briefly what you need. We reply right away.
Timo MoilanenOperating Partner, Board membertimo@vertics.co
050 363 7323