Paper Prototyping @ Usability Week

Hi,

last week I visited the Usability week 2009 in London and today I want to share with you my experience regarding paper prototyping.

On the last day we should work in groups to create a paper prototype in about 1 hour and then test this prototype with a person from another group. I have to say it was really fun and it worked really well. Especially we recognized how easy and FAST a design can be tested and improvements can be found.

In the following pictures you can see fast and creative work :-)

The topic of the paper prototype was part of a shop application where the user has the possibility to create a customized duvet.

In the following short video you can see the start of the test session and our favourite sentence "We are not testing you, we are testing the application".

Hopefully in the next days I have time to add more interesting topics related to the Usability Week.

Br, Claudia

Scrum in a real life project

Hi,

today a short video found on the "All about agile"-Blog about scrum in a real life project (you can turn the sound off :-) ).

Scrum methodology from Soul' on Vimeo.

Greetings from London,

Claudia

Web content accessibility and heuristic evaluation

Hello together,


today I want to introduce you to the WCAGs 2.0 - the web content accessibility guidelines and how to evaluate an existing web site using heuristic evaluation methods as described by Jacob Nielsen.

Web Content Accessibility Guidelines [1]
These guidelines are a good basis to work on when designing web pages for different groups of users including for example visual impaired people and more or less describe what to consider. Important to know is, that these "principles" are just recommendations and not rules.

The W3C consortium describes the WCAGs as follows:

Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.

These guidelines cover a wide range of different topics like how perceivable or how understandable a site is or how good the interoperability is when just using a keyboard. It would be too much now to go into detail but I want to list just a few principles which are the most important ones for me:

1. providing alternatives for all elements: this means, providing ALT attributes for images or video content
2. the contrast between the foreground and background should be a good one to make it easy to differ between real information and background info
3. the UI should be navigable using a keyboard only - so setting the TabIndex attribute is important
4. when designing forms, provide the "name" attribute for the input fields and put them into relation with labels using the "for" or "label" attribute
5. when structuring web content, use the H1-H6 elements to do so, 'cause usually screen reader applications rely on them
   

Considering just these 5 principles make it much more easier to build good accessible web pages.


Heuristic evaluation [2]


Heuristic evaluation is, according to Jacob Nielsen, a discount usability engineering method for quick, cheap, and easy evaluation of a user interface design.

Heuristic evaluation works the following way:

1. find "principles" - so called heuristics on which the evaluation should be based on. In our case, these heuristics would be the WCAG principles. Such principles are usually defined by a group or a single person, commonly used and good recommendations to follow but should not be considered as fixed rules
   
2. according to these principles, evaluators - who are usually usability experts - go through the whole interface of the application step by step and take notes, when the UI does not consider one of the principles. Usually, a good number for the amount of usability experts to use is between 3 and 6, 'cause one expert will only find 35% of all the problems. 5 experts will find about 75% of the existing problems.
   
3. after each evaluator has finished his process, they all meet together and compare their notes. Based on these notes, they rate the problems using the "severity rating". Therefore, each problem is assigned a number from 0 to 4, whereas 0 means, that there is no problem and 4 means, that it is a complete mess and a usability catastrophe
   
4. at the end, these results are summarized and presented to the developer team or the customer

When designing web content according to the WCAGs and using heuristic evaluation you can make your content better accessible and help impaired people understanding your web content.

Heuristic evaluation is a quick method for reflecting your UI and finding major usability problems according to various heuristics. These heuristics can be the WCAGs as well as other defined principles.


[1] ... WCAG web site [http://www.w3.org/TR/WCAG20/]
[2] ... Heuristic Evaluation [http://www.useit.com/papers/heuristic/]
[3] ... How to Conduct a Heuristic Evaluation [http://www.useit.com/papers/heuristic/heuristic_evaluation.html]

Role of Usability in the agile process

Hi,

in the last weeks we often have the discussion @ TT which role should the usability engineer have in the agile/scrum process. Is the usability engineer a member of the team or on the same level as the product owner?

In the article "Twelve emerging best practices for adding UX work to agile development" on the blog "AgileProductdesign.com" Jeff Patton advises as a main point that the UX practitioners should be part of the customer and product owner team. This has the advantage that the UX expert is in the position to decide and influence what should be build in the next sprint.

In my opinion it's not always clear how this can be handeld during the sprints to keep up the communication between the development team and the UX team - also to get fast feedback and not wait until the end of a sprint.
Another interesting question is how efforts/estimation should be handled? If the UX team is part of the product owner team and not part of the "TEAM" the efforts will not be part of the estimation at the beginning of the sprints. I'm not sure if this is good. Jakob Nielson also mentioned in his blog-article "Agile Development Projects and Usability" that story points should be assigned for the interaction design and usability.

Do you have any opinions and suggestions on this?

Br, Claudia

Event - Kundenfrühstück bei TechTalk

Hi,

today in german:

Kundenfrühstück bei TechTalk am 23.4.2009 um 9:00 zum Thema:

"Usability meets Development"
Wie schafft man es den Spagat zwischen Development und Usability optimal zu spannen?
Erfahren Sie auch, wie die Qualität/Userexperience von Applikationen für den Endanwender durch die Zusammenarbeit von Programmierung und Design verbessert werden kann.

Ich würde mich freuen wenn möglichst viele Interessierte dabei wären.

Br, Claudia

Inspiration needed?

Hi,

today I want to share some interesting links:

• Interaction Designers - Flickr Group
• Blogarticle "20 cool interaction design concepts"

And a great website is the "Wall of Deliverables". The idea was born at the IA Summit 2008 in Miami and the aim of the site is to share examples of deliverables.

Have fun, br Claudia

MIX09, Surface & Userability Podcast (again)

Hi,

today I want to recommend to view the following session videos of the MIX09. Of course the Keynote of Bill Buxton (recommended by michbex) and i was really fascinated by SketchFlow (presented by Christian Schorman - our judge @ Imagine Cup 08) and I'm looking forward to try it out. SketchFlow is currently not included in the Blend3 Preview. This is a screenshot of the SketchFlowPlayer:

Microsoft Surface Stove

A nice april fool by the Silverlight team is the Surface Stove.

20 years, No Improvement?

And one interesting podcast with Scott Berkun is now available at the Userability podcast answering the following question:

Don Norman’s seminal, The Design of Everyday Things, is approaching it’s 20th year in print. It explained why so many basic things in life are poorly designed and hard to use, such as pull handles on doors that need to be pushed. Since the world has been aware of these design flaws for two decades, why are so many basic usability failures still around?

Have fun,

br Claudia