RE: [agile-usability] incremental design -vs- overall user experience
- helen johnstone wrote:
> In order to get my head around how this all hangsWould it help if your Integration Tests took pictures
> together, and how to move
> it forward, I use screen-shots of existing screens
> and mock-ups of future
> screens. I put these in powerpoint and add workflows
> for the various
> user/business scenarios that we support. I also show
> groupings of technology
> - which obviously have a significant impact on the
> UI style and behaviour,
> as well functional groupings.
of every screen (regardless of its platform) in every
data state, and uploaded all of these to a Web site
for you and your minions to flick thru?
> I find it is a great communications tool as well forYeah. I want to automate that. (It turns out to be
> the rest of the team
> (development, sales, support etc) so they can
> understand what we've got and
> where it is going for those aspects.
absurdly easy.) Specifically, I want tests that drive
a GUI view thru a sequence of states, then upload an
animated GIF of the faked interaction.
GUI changes would produce new GIFs with their
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
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 email@example.com, "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: firstname.lastname@example.org
> 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