Knowing When You're Done Can Be Difficult to Assess
It's too easy to fall captive to feature creep and endless hours trying to debug a feature that really isn't that important for your MVP (Minimum Viable Product). At this open forum at Make In LA, I will be discussing how to define your requirements for an MVP and set proper milestones and metrics to know when you're done.
Hardware development can rack up incremental costs quickly, so it's important to make sure you stay focused and develop only the important features. Using a PRD (Product Requirements Document) is a critical tool to helping hardware teams stay focused.