RE: [agile-usability] The missing manifesto
- Jeff,One of the fun things about UCD is that a lot of people from a lot of different fields have contributed techniques and insight to the methodology. One reason is that people and their behaviors and situations tend to vary enormously, so there tends to be room for a lot of different approaches. The catch, of course, is that a method or technique works in one situation might not work in another.And then there are all the different types of people who claim a piece of the action: ethnologists and anthropologists, cognitive task analysts, human factors engineers, information architects, user experience designers, usability engineers, interaction designers, graphic designers, usability test specialists, and, even, webmasters and programmers.However, for a good overview that most of the experienced UCD and usability folk gravitate towards is the Usability Engineering Lifecycle. Deborah Mayhew put out a good overview book on this a few years back.Cheers,jon
Usability Architects, Inc.
PO Box 3222
Kirkland, WA 98083-3222Voice: 425-827-9296
Email: jon@...Specialists in User-Centered Design & Engineering
-----Original Message-----I'm doing a little bit of writing work this morning on the topic of agile
From: Jeff Patton [mailto:jpatton@...]
Sent: Tuesday, November 23, 2004 9:57 AM
Subject: [agile-usability] The missing manifesto
software development and user centered design. I'm working to generalize
about these two things.
In agile software development there's this "agile manifesto" thingy that
describes a core set of values [hopefully] held by people practicing agile
approaches. And while the specifics of agile approaches such as XP,
Crystal, or FDD might vary they all espouse to share the common ground
captured in the manifesto [at least for the time being].
There are lots of approaches that one might generally classify as User
Centered Design approaches: Goal Directed Design, Scenario Driven Design,
Contextual Design, Usage-Centered Design etc.. But, it seems there's an
emphasis by each of these authors to point out differences rather than the
common ground. [I could be wrong about that. I'm still pretty new to this
UCD community.] Also, UCD isn't always clearly understood to be a general
class of approaches. There are lots of books with User Centered Design in
the title that describe specific approaches - and not necessarily the
general class of approaches that I consider the term UCD to represent.
Does there exist in the UCD community some element of common ground? Some
general brief understanding of what we mean by UCD? - similar to the role
the agile manifesto serves to the agile community. I don't think there is -
but I could have missed something. Assuming there's not, do you [UCD
people] believe the community suffers for not having this shared
understanding? And, it might be fair to ask agile people: do you believe
the agile community benefits from having this common understanding?
I'd love feedback on these questions.
Agile usability news group: http://groups.yahoo.com/group/agile-usability/
see Essentional Interaction Design in Cockburn's Crystal Clear:
"Computers are useless. They can only give you answers."
-- PABLO PICASSO
- Great link. Thanks. Even if it was mentioned, it is worth repeating.
Cummins, Darin wrote:
> This has probably already been mentioned but there is a Java--
> Look-And-Feel (skin) called Napkin that makes the entire UI (even a
> working one) look like it was drawn on a napkin.
> http://napkinlaf.sourceforge.net <http://napkinlaf.sourceforge.net/>
> Ken Arnold created this PLAF for exactly the reason you are discussing
> here: to make a prototype provisional so stake holders won’t say “Great,
> the UI is done so we should be ready to deliver in a few days”.
> *From:* Jim Kauffman [mailto:jkauff@...]
> *Sent:* Friday, February 25, 2005 3:48 PM
> *To:* firstname.lastname@example.org
> *Subject:* RE: [agile-usability] Risks of prototypes
>> -----Original Message-----
>> From: hj [mailto:hjohnstone@...]
>> Sent: Friday, February 25, 2005 1:13 PM
>> To: email@example.com
>> Subject: RE: [agile-usability] Risks of prototypes
>> So now I make sure my prototypes are very visibly mock-ups.
> When I worked for Cognetics Corporation, Paul Hoffman created a Visio
> stencil with all the UI widgets you'd ever want--and made them look like
> they were drawn with crayons! Clients always knew his prototypes were
> BTW, Paul is one of the few people I've ever known who was equally talented
> at graphic design, UI design, and programming. What an integrated brain!
> Jim K.
> *Yahoo! Groups Sponsor*
> click here
> *Yahoo! Groups Links*
> * To visit your group on the web, go to:
> * To unsubscribe from this group, send an email to:
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
Palveluarkkitehti / Interaction Designer /
Alma Media Interactive Oy / NWS /
+358505050123 / petteri.hiisila@...
"I was told there's a miracle for each day that I try"
- John Petrucci