The Joel Test, a basic checklist to rate the operational maturity and health of a dev team:
- Do you use source control?
- Can you make a build in one step?
- Do you make daily builds?
- Do you have a bug database?
- Do you fix bugs before writing new code?
- Do you have an up-to-date schedule?
- Do you have a spec?
- Do programmers have quiet working conditions?
- Do you use the best tools money can buy?
- Do you have testers?
- Do new candidates write code during their interview?
- Do you do hallway usability testing?
Read some great stuff on the current AI hype over the weekend: The Seven Deadly Sins of AI Predictions and predictions in general I might add. Is AI Riding A One Trick Pony, a little history of the deep learning breakthrough, fueling the current hype, allowing for a better understanding of its potential and limitations. Last but not least How To Navigate The Coming A.I. Hypestorm, with a less than ideal example but a rather revealing look under the hood.
Understand, eNumerate, Paper, Historical context, Advantages, Think -> UNPHAT. Ozan Onay‘s approach to deal with the fact, that for most cases you (or your client) are not Google, Amazon, Twitter or the likes and therefore some of their currently hyped solutions might not fit your problems.
While MVP as an approach may not solve all of the problems associated with product development (and project definition), in almost all cases some valuable insights can be derived from it. There only is one caveat to this: In order for the magic to work, all sides involved have a clear grasp of what the concept actually entails.