the startups.com platform about startups.comCheck out the new Startups.com - A Comprehensive Startup University
Education
Planning
Mentors
Funding
Customers
Assistants
Clarity
Categories
Business
Sales & Marketing
Funding
Product & Design
Technology
Skills & Management
Industries
Other
Business
Career Advice
Branding
Financial Consulting
Customer Engagement
Strategy
Sectors
Getting Started
Human Resources
Business Development
Legal
Other
Sales & Marketing
Social Media Marketing
Search Engine Optimization
Public Relations
Branding
Publishing
Inbound Marketing
Email Marketing
Copywriting
Growth Strategy
Search Engine Marketing
Sales & Lead Generation
Advertising
Other
Funding
Crowdfunding
Kickstarter
Venture Capital
Finance
Bootstrapping
Nonprofit
Other
Product & Design
Identity
User Experience
Lean Startup
Product Management
Metrics & Analytics
Other
Technology
WordPress
Software Development
Mobile
Ruby
CRM
Innovation
Cloud
Other
Skills & Management
Productivity
Entrepreneurship
Public Speaking
Leadership
Coaching
Other
Industries
SaaS
E-commerce
Education
Real Estate
Restaurant & Retail
Marketplaces
Nonprofit
Other
Dashboard
Browse Search
Answers
Calls
Inbox
Sign Up Log In

Loading...

Share Answer

Menu
Start-ups: How do you find the right balance between setting up automated testing, code reviews, refactoring, etc. and staying lean/MVP minded?
Dan Martell, SaaS Business Coach, Investor, Founder of Clarity answered:

"Right action, right time" Eric Ries

The key is to invest in the parts of the product that need that attention. In the early parts of a startup (MVP) then it's all about building something to put in front of users.

As that scales, then you can spend some time paying down the technical debt by getting good Unit Test coverage, and eventually building automated deployments and an integration server.

I would spend more time trying to get to some level of Product/Market fit first before spending too much time on development processes that might not matter if you fail to build anything someone wants.

You'll usually feel the impact of what's missing as users report more bugs, or the # of defects your dealing with weekly outweight the # of features.

Right time, right action. Start simple.

(If you want something more concrete, just do 80/20 - 80% on user facing / value creating stories, 20% of paying down code debt / automation).

Talk to Dan Upvote • Share
•••
Share Report

Answer URL

Share Question

  • Share on Twitter
  • Share on LinkedIn
  • Share on Facebook
  • Share on Google+
  • Share by email