It may not have been quite so bad, but we went through something similar on the last firmware upgrade. For me, these problems are always management problems, not programmer's. Why, because it's management's job to fix it.
1) Is it a resource problem? Hire more. Yes, adding more people to a late project can make it later, but this has been an ongoing problem over the last couple of years.
2) Is it a skill problem? Hire the appropriate skills, and possibly fire inappropriate ones. If you can't find the skills locally, then outsource.
It is possible that it is a resource issue. Bookeen may be too small to justify sufficient resources. If this is true they have a major issue. The problem is that they are competing against quite a few deep pocket competitors: Sony and eventually Amazon, Samsung, Fujitsu, ASUS, etcetera. As a first entrant the small scale approach worked fine, but if they can't scale up they need to either adapt or die. One option would be to use their current programming $ to pay someone else (pocketbook? Netronix?) to produce a customized version of an existing product.
|