PLAN FOR IMPROVISATION

photo credit: herval I got an advertisement for a workshop about how to develop SaaS products. The title was, "Silly Agility--The Myth of the SaaS Agile Product Manager". Here is some of the text of the advertisement: "XP was an attempt to replace waterfall development approaches with something new...[References a generic project]...objectively analyzed, [this project] was a failure; after five years the product wasn't completed and the development effort was terminated." My first though is that this is a sensational advertisement to get bodies in the door of a poorly conceived of workshop. My second thought is that this is damaging to the career of person advertising it. Factually speaking: When the Agile principals were defined, it wasn't an exercise in creating newness for its own sake. Another objection, is that a "Agile" project that drags on and on then finally fails isn't using Agile principals in the first place. If its goi

Anybody who has been to our office knows I am an Android fan. My prediction is that the Android platform will end up with a much, much larger install base than iPhone OS. Originally, I felt this way because you can get a Android phone on every carrier for a lower cost than the iPhone - many of them are now free with a contract. This is good enough, but I have a new insight. The Android OS does a great job of directing your attention to highly important information. As such, its easier for new users to pick up and for busy people to use. How can this be? You should argue that the the Android OS so similar to the iPhone OS. You are right. However, it comes down to usability. The majority of people out there won't explore their device to find information. They just want the phone to do the work for them. If it doesn't smack them in the head it might as well not exist. Android has two crucial features that make it a helper more than just a smart phone. First, Android b