Re: incremental design -vs- overall user experience
- --- In email@example.com, Brian O'Byrne <bobyrne@s...>
> Certainly for the first of the two projects I mentioned the chartwas
> drawn big and stuck on the wall. Everyone got used to referring toThe visible posting and hand notation is an ideal agile adaptation
> it, and anyone could annotate it as they worked.
for a technique. If you were overly formal you might have modified
the diagram through change requests and meetings. For better or
worse the agile community is laying claim to behavior which used to
be called "common sense." ;-)
The fact that was done in UML and printed doesn't bug me at all -
since it was fast to do, and since using UML for that team didn't
exclude anyone. If a business leader or someone from a traditional
XP customer role was expected to understand it, UML may have been a
> I don't agree that the interaction design concern has to gowas
> _everywhere_. On the second of the two projects I mentioned there
> a real n-tiered architecture and were very definitely two teams,one
> for the problem domain and one for the UI.service
> The PD team followed a very traditional methodology and wrote
> code that could be used by many different UIs.I'd suspect even that service code was driven at some level by the
interactions users had with the software. If not, they'd have
implemented unused services, or failed to implement necessary
services. The user interactions may have had a lighter day-to-day
touch on the work this team did - but I'd still assert that they
affected it. I wouldn't have a usability guy wandering through
their team very often....
Thanks for posting Brian!
This is without a doubt an issue that I came across in my experience
as a usability manager.
Do you suggest that this work should be done in iteration 0 using the
agile methodology? This seems to be increasingly a recommendation in
a number of white papers and publications such as Scott Ambler.
However, when you say 'minimal effort' how does this translate into
time scales - is there an average that you work with in your
experience let's say 1-2 weeks?
I also appreciate, if you could forward the pdfs on the collaborative
UI review method that you mentioned in a previous message.
--- In firstname.lastname@example.org, "Larry Constantine"
> An effective way around this problem is to draft a navigation
> (screen flow) in advance based on provisional understanding of userroles
> and tasks in the application. This architecture gives a reasonablywell
> thought out framework on which to hang the features and functionsas they
> arise "organically." The navigation architecture is itself reviewedand
> refactored as needed as the details of the application emerge. Thisapproach
> is what I describe as "architecture-first development" in the newCutter
> Report on agility and usability. It's proven to be a goodcompromise that
> yields maximal payoff in maintaining a sound UI organization withbare
> minimal upfront investment.experience
> --Larry Constantine
> Chief Scientist | Constantine & Lockwood, Ltd.
> -----Original Message-----
> From: Jeff Grigg [mailto:jeffgrigg@...]
> Sent: Tuesday, 13 July 2004 7:48 PM
> To: email@example.com
> Subject: [agile-usability] incremental design -vs- overall user
> I can't claim to be an expert on user interface design or agile
> methods, but here's a thought that's been bothering me for a while:
> It's been my experience that systems that "grow organically" over
> time often have bad user interfaces. New features are often buried
> deep within the existing user interface structure, making it hard
> find. New reports, for example, are added as buttons or menu*not*
> options deep in the work flow, where they're first needed, but
> made available from higher level menus.even
> I've found that drawing screen flow diagrams of the overall system
> illustrates these problems and guides redesign of the GUI to make
> the system more usable.
> How can one avoid this problem in "organically growing" systems?
> Does the "overall user experience" need to be planned up-front,
> when functionality is implemented incrementally?redesigned
> As project direction changes during implementation, what triggers
> you to recognize that the user interface flow needs to be
> to most effectively support the new business requirements you've
> Yahoo! Groups Links