With all due respect to Seth Godin, while he may be a marketing guru, his post about minimum viable product makes me think that he hasn’t participated in the product development process in a very long time, considering that his definition of minimum viable product is pretty coarse (and likely why it doesn’t work!). As [...]
Over the last few months, there’s been so much turmoil in the touchscreen tablet space! Consider: HP’s newest foray into tablet computing, not with a Windows OS but instead with WebOS, subsequently gets beheaded in under 2 months after the TouchPad’s launch. Android’s Honeycomb and Gingerbread tablets are growing in number, but not so much [...]
So last night, I had the opportunity to see Ken Schwaber in action at the AgileNYC event in LimeWire’s Tribeca offices with a friend of mine. It was a great event with a lot of people ranging widely in their exposure to Scrum. I find that there’s always a particular nuance that I relearn when [...]
Scrum and agile (note the lowercase!) development techniques have been around for a few years now, and prominent companies use it in some form or another. However, I’ve seen multiple instances where clients and management alike will derail the whole notion of Scrum! It pains me to see it, so here’s a Part 1 (of [...]
Twitter and Foursquare are two easy examples that come to mind for services that have failed very publicly. They get pretty bad press from people because of service outages. I myself have been on the receiving end too, but as someone who’s been in the application development side of the house, I know that these [...]
What is Wolfram Alpha good for, and how would you use it? What should we look for in the future?
When it comes to the classic “iron triangle” project management model of time, scope, and cost, the three key stakeholder groups which directly contribute, guide, and work on a typical interactive project would certainly get into a fight with very little prodding. The question is: How do you make it work?
Software development lifecycle processes can sometimes be seen as impediments or tedious tasks. But it is worth reminding everyone that the smart work up front will save you headaches later. In my experience, well-written software requirements serve two main purposes: it orients all project participants and helps get buy-in about what you’re trying to do [...]
