Nice paper. Multiple goals. Multiple stories. A vague sort of what Tom Gilb calls Impact Estimation in his book?Competitive Engineering.
But left implicit is identifying the stakeholders, identifying the top ten goals and making numerical targets for them as measured by explicitly identified metrics, and tracking the effectiveness of your methods in order to improve them in the long term. I mean, for example, are two week sprints more or less effective than one week sprints?
But even Gilb leaves out the rules and principles from Jef Raskin's?The Humane Interface. You can find the author's summary on my website or ask me to mail them to you or to the list. Jef wants computers to be so simple to learn and use that your fingers know what to do. This lets the user keep her singular focus of attention on her content and not be distracted by the mechanism.?
Jef says we don't go to the theater to watch the projector. Well, in our case some of us actually do, but regular folks do not. This means that modal dialog boxes, which stop everything until you click OK and thus guarantee to break your train of thought should be universally banned from programs intended for human use.?
Humans don't really multi-task unless all but one of those things are already automatic and need no conscious attention. However, application designers and implementors act as if they don't know such fundamental facts about humans. I think that may be because they really do NOT know that.
Thus my radical claim is that before we start to build software for humans, we should learn a few things about how humans work and intentionally design applications to avoid interfering with their users' thought processes. I know it is a lot to ask, but if you even partly succeed, users will find your app addictive and highly valuable.
Dick Karpinski, Nitpicker extraordinaire
148 Sequoia Circle,
Santa Rosa, CA 95401
Home: [masked] ? ?http://nitpicker.pbwiki.com/