Embed Size (px)
Citation preview
1ICELW, New York, June 2010
PROJECT USABILITY : SCHMOOSABILITY
…what does it matter?
2ICELW, New York, June 2010
PROJECT ZEN
3ICELW, New York, June 2010
PROJECT ZEN
Development processes to improve organizational performance
4ICELW, New York, June 2010
PROJECT DESIGN : ROLES
•Test Manager, Analysts
•Usability
•Instructional Designer
5ICELW, New York, June 2010
PROJECT DESIGN
‘ The project manager must ensure that there is transparency of roles
across the project team...’
6ICELW, New York, June 2010
PROJECT DESIGN : COMMUNICATIONS
7ICELW, New York, June 2010
INFORMATION GATHERING
•What information to capture?
•Who and what will you ask?
8ICELW, New York, June 2010
USER CENTRED DESIGN
‘ UCD is about designing the
total user experience...’
9ICELW, New York, June 2010
USABILITY
‘ The ease with which a user can successfully interact with and use an application, web site or process to achieve their goals...’
10ICELW, New York, June 2010
USABILITY
11ICELW, New York, June 2010
USABILITY : COMMUNICATIONS
12ICELW, New York, June 2010
WHEN THINGS GO WRONG
13ICELW, New York, June 2010
WHEN THINGS GO WRONG : TESTING
14ICELW, New York, June 2010
WHEN THINGS GO WRONG : TESTING
Test Plan about:
• Tasks and metrics• Scenarios to be used• Scripted into Test Cases
15ICELW, New York, June 2010
WHEN THINGS GO WRONG : UI
16ICELW, New York, June 2010
SUMMARY
• Communications strategy
• Include ALL stakeholders
• Project usability successful if team have clear understanding of their role
17ICELW, New York, June 2010 17
THANKS
18ICELW, New York, June 2010
REFERENCES
Sandler, John ICELW 2010 Proceedings
www.dilbert.com
CONTACT
@greyrab (Twitter)
