Technical due diligence checklist for startups • TechCrunch


Earlier, the author He detailed the technical due diligence (TDD) process that investors go through before committing cash to early-stage startups.

Through this monitoring, C-level executives and VCs are given a detailed checklist for C-level executives tasked with determining whether their “codebase is safe enough for investment.”


Product road map

  1. Explain how to collect user and customer feedback.
  2. Provide a large sample of user/customer feedback that you collect.
  3. Provide user/customer feedback integration results.
  4. Provide the last 12 months of product management data to engineering (eg Jira tickets). How much was the cost for new features/functions compared to maintenance? What are the main items on the list?
  5. Clarify the roadmap for the next 12 months.

Code quality

  1. How Much Will Finance Invest in Tech Debt Prevention and Remediation? In security risk prevention and improvement? In IP disaster prevention and recovery?
  2. What software languages ​​do you use? Is the use of new languages ​​manageable?
  3. Is renovation being considered or may be necessary?
  4. What testing methods do they use and how extensive are they? Do you perform unit tests, automated tests, manual QA testing, and user acceptance testing? Share the most recent results from each test type.
  5. Is there a line level scanning tool like SonarQube in place? If yes, share a sample report.
  6. Is third-party code managed by an administrator, embedded in the code, or both? why?
  7. Define your architecture and provide architectural sketches.

Enrollment of intellectual creativity



Source link

Related posts

Leave a Comment

1 × 3 =