* Really: they had a "team happiness person"?
* Featuritis: Why not start with a single sensor (if possible itegrated in the basic product), but try to develop everything once
* Idiotic presumptions everywhere like asssuming that the non-availability of a specifi part for V1 is best cured by a completely revised V2. Or that the resolution of the display matters
* Senseless Perfectionism: Hoho, the company they hired was "not able to use github". Yes, then take the source and put it there yourself (no need to delay, and no excuse for delivering late)
* Lack of a preexisting SW concept (they really had to have a running prototype where a backer looked at the source to tell them that the MC could be put to low-power mode. (If you select a MC, the first thing you do should be to determing if the state transitions between the sleep modes support what you want to do *on the high level*)
* Complete lack of technical understanding about MCs (they complained that thet had no "arduino expert"). MCs are great tools. You dont select the MCs by the SW you have, or by how conevnient and popular they are in the "maker" circles. You select them by the IOs they have, and by the power consumption. For most things you actually dont end up with anything close to an arnduino (e.g. for low power: look at the MSP430, for raw IO features: look at the M16C series)
* A broken assumtion from the very start: That this needs to be modular. I am pretty convinced that (lets exclude the laser module) most of the sensors could have been integrated right away, for less money than the box you put them in.
That being said, this should have been a 2-4 man project for 6 months, with focus on solving the technical problems first. A more or less working prototype electronics design (2man months for the most important sensors) should have been done before promising anything on Kickstarter.