The "UCD community" is truly in need of some basic
strategies. ...A manifesto of some sort could
be a valuable tool.
On the other hand, while this
discussion group is engaged in a really interesting
valuable discussion, I'm not sure we're ready for (or
manifesto. We're still working out the basic
ground rules of our
conversations and collaborations.
So, I think Josh is saying that he believes a UCD manifesto would
be useful but that some kind of combined 'agile-usabilty' manifesto might
be a bit ambituous at the moment. Josh, who would an agile-usability
manifesto be aimed at?
Michael Mahemoff said-------
"it's easier to be concrete about
something that's more
narrowly defined. So I'd argue we're more ready for an
manifesto than a usability
"...I would argue that if there is to be
a manifesto, it
should be agile-usability, not just-usability. Aside from
this being the
wrong forum, a usability manifesto is inherently
I don't share your clarity Michael. Who would this agile-usability
manifesto be aimed at? I can see a UCD manifesto providing a mandate or a modus
operandi for UCD professionals, but I dont see so clearly what you mean or who
it is for.
Jon Meads said----------
not convinced that a manifesto is needed for UCD. Having been in the UCD
community for over 20 years, I think most of us realize the
- Usability is critical to success use of an interactive system or
- Usability is not the same as User Experience but affects it
are obtained by focusing design on "what the user can do" as opposed to what
the system/product can do;
need to design for usability and this requires understanding:
the users are,
- what the context of use will be, and
- what factors will affect their
I think Jon is saying that we don't need a manifesto because it is already
implicit and most of us would agree on what it should say, and those things
are those which Jon listed above.
What a manifesto could
do is to bring together a common set of xCD values, and provide a banner/brand
under which all of various xCD camps could take a common message forward to
those looking to advance their capabilities.
agree with the bringing together part, though the phrase about advancing
capabilities is a bit odd but I think i know what you mean, like UCD Capability
in the CMM sense.
After reading all these comments I began rethinking
what I am doing here and what this agile_usability thing is all about. I feel
like I just walked into a lecture 20 minutes late and am the annoying person who
still thinks it's ok to ask questions even though they missed the start. So, I
re-read the agile-usability yahoo group intro and I quite like it and quite
agree with the intent.
One aim was to 'Define usability roles on agile projects'
- I think this fits with the idea of recognising there is a UCD role on the
project (some people seemed unhappy talking about roles, but without this, us
UCD people don't even come to the party). I think it also fits with the idea of
having a manifesto so that we are all clear on what that UCD person should do in
the team, what will be there modus operandi and their guiding
really don't know what people mean by an 'agile-usability' manifesto. Does this
mean a manifesto specifically for the UCD person working on an Agile project? If
so, I'd rather go with the UCD manifesto and make it work for both. Another aim was to,
"Describe essential usability practices usable on agile projects -
practices that are lighter weight and more collaborative . " Perhaps this is what those advocating an
'agile-usabiity' manifesto are talking about, specific usability practices for
this kind of development???
------------------What is this
agile-usability group all about, the yahoo group
This group has the goal of
connecting the usability community to the agile development community - and both
these groups to the business community they both serve.
community has a lot of guidance to offer software development on requirements
elicitation, product design, user interaction and interface design, and
The agile community offers the potential for higher
software quality by way of agile development techniques. The agile community
offers the potential for the business community to reap larger benefits through
incremental delivery which might allow businesses to earn return on software
sooner, or cease development on unprofitable projects before too much capital is
But, agile software development approaches described so far
seem to give short shrift to usability practices. If you're from the agile
community and disagree with that statement, this is the group where you may want
to say so.
Many folks from the usability community seem to disagree with
agile approaches in particular notions such as emergent design and incremental
delivery. Those proficient in usability practices believe that failing to gather
and act on critical user data short changes the users of the software and the
software's subsequent usability and value to the users and owners of that
software. If you're from the usability community and disagree with anything in
those statements, this is the group where you may want to say so.
hopes that this groups might move forward to:
* Define usability roles on
* Define a basic body of usability knowledge all members of a
project should understand
* Describe essential usability practices usable on
agile projects - practices that are lighter weight and more collaborative
Describe where specific financial returns are for including usability practices
on agile projects