Re: [agile-usability] Design Values
- There is more to it --- specifically, there's a particular horror story or two for each item on the list, which will be talked about in future blog posts by members of my team. I think those articles will be more fun to read, once they're written.I can't really disagree with the accuracy of your simplification, but I don't know how useful it is. People who know what "well-researched" means don't need to be told, and people who don't often think that they do.-johnOn 11-Jul-09, at 9:50 AM, Jared Spool wrote:
- One of Jeff's points resonated strongly with me. To put it flippantly, no one cares how we build products, just how much they get from using them. Ideally, the way we work makes us happy, makes our customers happy, and makes our bosses happy. (note: money is often a significant component of said happiness)Adherence to the process can be almost comical. At a prior company, when talking to someone about why they missed their release deadline (yeah, I know. Agile and deadlines are not the best of friends) he explained that a certain activity had to be done 2 sprints prior to release, but that its associated story got cut from the sprint it needed to happen in. Clearly, there is a lot at work here that I'm not going to bother to dissect, but this team was more focused on the agile process than the success of the product and the perceptions of the company leadership. It was not pretty.-jer"Be well, do good work & keep in touch."
- Garrison Keillor
On Sun, Jul 26, 2009 at 11:00 PM, Ron Jeffries <ronjeffries@...> wrote:Hello, John. On Sunday, July 26, 2009, at 10:53:07 PM, you wrote:I often recommend exercise and eating sensibly ...
> Heh. It would never occur to me to recommend something that I wasn't
> doing myself.
-- John Kenneth Galbraith