A prep guidelines for startups about to endure technical due diligence • TechCrunch

Beforehand, the creator supplied an in depth overview of the technical due diligence (TDD) course of buyers conduct earlier than injecting money into early stage startups.

On this follow-up, he provides an in depth guidelines for C-level executives and senior managers who’re answerable for serving to VCs decide whether or not their “codebase is protected sufficient for funding.”

Product roadmap

1. Clarify the way you gather person and buyer suggestions.
2. Present a pattern subset of essentially the most granular person/buyer suggestions you gather.
3. Present the outcomes of the synthesis of person/buyer suggestions.
4. Present the final 12 months of product administration knowledge for Engineering (e.g. Jira tickets). How a lot was spent on new options / performance in comparison with upkeep? What are the most important gadgets on the record?
5. Clarify the roadmap for the subsequent 12 months.

Code high quality

1. How a lot does Finance spend money on tech debt prevention and remediation? In safety threat prevention and remediation? In IP threat prevention and remediation?
2. Which software program languages do you employ? Is the usage of new languages managed?
3. Is a refactoring being thought-about or presumably wanted?
4. Which testing strategies do you employ and what’s their breadth? Do you carry out unit assessments, automated assessments, handbook QA testing, and person acceptance testing? Share the latest outcomes from every kind of take a look at.
5. Is a line-level scanning device akin to SonarQube in place? If sure, share a pattern report.
6. Is third-party code managed via a supervisor, saved within the code, or each? Why?
7. Describe your structure and supply architectural diagrams.

Mental property