MEX Experience Boards:  A Set of Agile Tools for User Experience Design<br />Carlos Rosemberg<br />Instituto Atlântico<br ...
Entering in the Agile World<br />Individualsand interactionsover processes and tools <br />Working software over comprehen...
Yes, Agile developers and UX people have many agreements. But some issues remain...<br />How to do good user research when...
To create a real UX vision in the agile projects, UX people <br />“need to use simpler tools and techniques, focusing  mor...
In other words<br />to  invest more in simple,  fast-making artifacts; <br />to  intensively use visual language for team ...
The Mex Experience Boardsuse good pratices from the Agile and UX worlds.<br />...By reorganizing and customizing some well...
Before continue... What is MEX?<br />
MEX : a Modelfor User Experience<br />CONTEXT<br />ACTIVITIES<br />This conceptual model of a generic user experience help...
Individual<br />
What he/she thinks ? <br />What he/she likes? <br />What he/she knows? <br />What he/she is able or unable to do?<br />How...
 Activities<br />
What the individual is trying to accomplish?<br />What are his/her objectives?<br />Which steps must/might be taken?<br />...
Artifacts<br />
Artifacts<br />Which objects play relevant role in the experience? <br />Which are your characteristics?<br />
Interactions<br />
How the individual interacts with artifacts around?<br />The artifacts interacts between themselves?<br />Which stimmuli h...
Context<br />
Context<br />How the social and cultural aspects affect what is happening?<br />In wich environmental conditions the exper...
Momentum<br />
The experience clearly has a beginning, middle and end?<br />The individual can really get engaged?<br />Momentum<br />
The well-succeeded <br />experience stages<br />Beginning<br />Middle<br />End<br />Pos-experience<br />Conclusion<br />En...
Ok, let´s come back to the experience boards.<br />
Mex Experience Boards in Agile context<br />       Development Phase<br />(sprints 1 to n)<br />         Initial Requireme...
First, let’s take a look in the Experience Summary Board<br />
Experience Summary Boarddetails all MEX elements in the early  product conception phase providing insights to requirements...
Mex Summary Board Example using plain text<br />Also recommended: post its or white board + camera<br />
Now, let’s see the Experience Flow Board<br />
Experience Flow Board is intended to  discover  or  design task flows. <br />Simple task flow analysis in a swim lane boar...
An Experience Flow Board example<br />In an ordinary task flow chart, the MEX elements are exposed and studied.<br />And.....
An Experience Flow Board example<br />Splitting the experience  into phases helps to focus in the Start and Extension poin...
Early Results in small Case Studies<br />More team awareness about user experience<br />More user experience requirements ...
First Conclusions<br />The main benefit of using these tools is the reinforcement of the connection between UX and agile a...
Future work<br />Create more tools in order to cover the whole extension of agile development processes;<br />Mature and r...
Main References<br />Carlos  Rosemberg.  MEX  -  Modelo Genérico de  Experiência do Usuário: Uma Evolução Conceitual.  In:...
Thank you!<br />Carlos Rosemberg<br />carlosrosemberg.com<br />carlbberg@gmail.com<br />
Upcoming SlideShare
Loading in …5
×

Mex Experience Boards - A Set of Agile Tools for User Experience Design

3,006 views

Published on

The Mex Experience Boards are a set of agile modeling tools created to identify and/or design important aspects of User Experience (UX) in an interactive product. Grounded on MEX - Generic User Experience Model, it can be easily used in conjunction with other UX/Agile approaches, such as user roles, personas and task flows.

Published in: Design
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,006
On SlideShare
0
From Embeds
0
Number of Embeds
164
Actions
Shares
0
Downloads
38
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide

Mex Experience Boards - A Set of Agile Tools for User Experience Design

  1. 1. MEX Experience Boards: A Set of Agile Tools for User Experience Design<br />Carlos Rosemberg<br />Instituto Atlântico<br />SWIB / IHC2010<br />Belo Horizonte - Brazil<br />
  2. 2. Entering in the Agile World<br />Individualsand interactionsover processes and tools <br />Working software over comprehensive documentation <br />Customer collaboration over contract negotiation<br />Responding to change over following a plan<br />
  3. 3. Yes, Agile developers and UX people have many agreements. But some issues remain...<br />How to do good user research when working code is asked to be delivered very early?<br />And about the workingartifacts produced? How much effort is necessary? How are they now used by developers?<br />
  4. 4. To create a real UX vision in the agile projects, UX people <br />“need to use simpler tools and techniques, focusing more in understanding than documenting, and supporting rapid input and change.” <br />(Craig Larman)<br />
  5. 5. In other words<br />to invest more in simple, fast-making artifacts; <br />to intensively use visual language for team fast assimilation;<br />to allow team and stakeholders collaboration (participatory design)<br />
  6. 6. The Mex Experience Boardsuse good pratices from the Agile and UX worlds.<br />...By reorganizing and customizing some well-known tools and techniques in order to make them more light-weight.<br />They are the Summary Board and Flow Board.<br />
  7. 7. Before continue... What is MEX?<br />
  8. 8. MEX : a Modelfor User Experience<br />CONTEXT<br />ACTIVITIES<br />This conceptual model of a generic user experience helps to organize the complex relationship between main user experience elements.<br />MOMENTUM<br />INTERACTIONS<br />ARTIFACTS<br />INDIVIDUAL<br />
  9. 9. Individual<br />
  10. 10. What he/she thinks ? <br />What he/she likes? <br />What he/she knows? <br />What he/she is able or unable to do?<br />How he/she reacts to stimmuli?<br />Individual<br />
  11. 11. Activities<br />
  12. 12. What the individual is trying to accomplish?<br />What are his/her objectives?<br />Which steps must/might be taken?<br />Activities<br />
  13. 13. Artifacts<br />
  14. 14. Artifacts<br />Which objects play relevant role in the experience? <br />Which are your characteristics?<br />
  15. 15. Interactions<br />
  16. 16. How the individual interacts with artifacts around?<br />The artifacts interacts between themselves?<br />Which stimmuli happen? <br />Which senses are involved?<br />Interações<br />
  17. 17. Context<br />
  18. 18. Context<br />How the social and cultural aspects affect what is happening?<br />In wich environmental conditions the experience occurs?<br />
  19. 19. Momentum<br />
  20. 20. The experience clearly has a beginning, middle and end?<br />The individual can really get engaged?<br />Momentum<br />
  21. 21. The well-succeeded <br />experience stages<br />Beginning<br />Middle<br />End<br />Pos-experience<br />Conclusion<br />Engagement<br />Extension<br />Atraction<br />FLOW<br />The mental state of operation in which a person in an activity is fully immersed in a feeling of energized focus, full involvement, and success in the process of the activity<br />Sources: Nathan Shedroff / Mihály Csíkszentmihályi / John Dewey<br />
  22. 22. Ok, let´s come back to the experience boards.<br />
  23. 23. Mex Experience Boards in Agile context<br /> Development Phase<br />(sprints 1 to n)<br /> Initial Requirements Phase (Sprint 0?)<br />User roles definition<br />User stories definition<br />Development<br />Activities<br />Vision statement with initial requirements<br />Experience <br />Summary Board<br />Details MEX elementsall at once, providing insights to requirements definition, focusing in the overall user experience.<br />Experience <br />Flow Board<br /> A customized flow analysis intended to discover or design task flows<br />
  24. 24. First, let’s take a look in the Experience Summary Board<br />
  25. 25. Experience Summary Boarddetails all MEX elements in the early product conception phase providing insights to requirements definition.<br />It focuses in the overall user experience (i.e: buy a book on-line)<br />and summarizes the agile user experience analysis in just one place.<br />
  26. 26. Mex Summary Board Example using plain text<br />Also recommended: post its or white board + camera<br />
  27. 27. Now, let’s see the Experience Flow Board<br />
  28. 28. Experience Flow Board is intended to discover or design task flows. <br />Simple task flow analysis in a swim lane board. <br />In each lane there is an experience stage that refers to the MEX element momentum (start, development, finish and extension). <br />
  29. 29. An Experience Flow Board example<br />In an ordinary task flow chart, the MEX elements are exposed and studied.<br />And...<br />
  30. 30. An Experience Flow Board example<br />Splitting the experience into phases helps to focus in the Start and Extension points. This is the main advantage of this approach.<br />Is very easy to pay attention only at the development (middle) stage.<br />
  31. 31. Early Results in small Case Studies<br />More team awareness about user experience<br />More user experience requirements gathered<br />Team buying<br />
  32. 32. First Conclusions<br />The main benefit of using these tools is the reinforcement of the connection between UX and agile approaches, getting the better of the two worlds.<br />
  33. 33. Future work<br />Create more tools in order to cover the whole extension of agile development processes;<br />Mature and refine this tools in several types of projects.<br />
  34. 34. Main References<br />Carlos Rosemberg. MEX - Modelo Genérico de Experiência do Usuário: Uma Evolução Conceitual. In: Simpósio de Fatores Humanos em Sistemas Computacionais, Porto Alegre, 2008. <br />James Shore et Al. The Art of Agile Development, O'Reilly Media, 2007. <br />Mike Beedle et Al. Available at: http://agilemanifesto.org. <br />Nielsen, J.Agile Development Projects and Usability. Available at http://www.useit.com/alertbox/agile-methods.html <br />Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, Third Edition. Prentice Hall, 2004. <br />Mike Cohn. User Stories Applied for Agile Software Development, Addison-Wesley, 2009.<br />
  35. 35. Thank you!<br />Carlos Rosemberg<br />carlosrosemberg.com<br />carlbberg@gmail.com<br />

×