User Centered Interaction Design In Agile Environment

1,519 views

Published on

My earlier presentation from Agile India Bangalore - 2005

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,519
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
27
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

User Centered Interaction Design In Agile Environment

  1. 1. User Centered Interaction Design in Agile Environment Agile India Bangalore 2005
  2. 2. www.henryjacob.com
  3. 3. What customer want?
  4. 4. $
  5. 5. Dollar Printing Machine or Give them tools which helps them to make money(legally)
  6. 6. A good system is something which eliminates existing tasks(wherever its possible), or speedup the tasks with efficiency, save money and time.
  7. 7. Engineering Business Design
  8. 8. The hardest single part of building a software system is deciding precisely what to build? -- Fred Brooks
  9. 9. “Plan for artifacts, whose form, content, behavior is useful, usable, desirable, as well as economically viable, and technically feasible” – Alan Cooper
  10. 10. Engineering Business Design
  11. 11. XP is an Engineering Process
  12. 12. Planning Game Story Card Planning Iteration Plan Stories Game Release Plan Decide on scope and priorities Estimate cost and schedule Benchmark for feedback
  13. 13. Who does the design?
  14. 14. Customer Users Programmer Graphics Designer
  15. 15. software development is not just about coding
  16. 16. Can you imagine Windows without mouse?
  17. 17. Customer Users Programmer Graphics Designer
  18. 18. Interaction Designer Application Architect Solution Architect
  19. 19. Customer SME Architect Users
  20. 20. Design Game Design Game Stories Design Team
  21. 21. Planning Game Story Card Planning Iteration Plan Game Release Plan Design Team
  22. 22. The Design Team typically creates a sizeable queue within just a few iterations by continuing to work with the Customer to develop new stories while current ones are being implemented.
  23. 23. Design involves a sizable up-front activities
  24. 24. Domain Customer Personas Goal Design Tasks Context Objects
  25. 25. Domain Customer Personas Goal Design Tasks Context Objects
  26. 26. StocksDirect.com Buy MyStocks SD.com Stocks Sell Domain: Stock Trading, Stock Exchange Entities/Objects: Stocks, User Tasks: login, Buy, List, Sell
  27. 27. Shekar Alex
  28. 28. StocksDirect.com Agent Shekar
  29. 29. Alex LOGIN USRNAME:PWD SELL STOCK_SYMBOL
  30. 30. Domain Customer Personas Goal Design Tasks Context Objects
  31. 31. Shekar Alex Customer Goal: More Transaction Potential Users: Working Professional – Especially IT and Sales Personas: Shekar, Alex Context: Shekar - Work Environment & Work, Alex - Always on Move
  32. 32. “No matter how skillful and creative the designer ,If he does not have a clear and detailed knowledge of the users he is designing for , what the constraints of the problem are, and what business or organizational goals the design is hoping to achieve , he will have little chance of success.” - Alan Cooper
  33. 33. A good system is something which eliminates existing tasks(wherever its possible), or speedup the tasks with efficiency, save money and time.
  34. 34. Engineering Business Design
  35. 35. Interaction Designer Application Architect Solution Architect
  36. 36. Domain Customer Personas Goal Design Tasks Context Objects
  37. 37. Planning Game Story Card Planning Iteration Plan Game Release Plan Design Team
  38. 38. “If the software were magic, what would it do?”
  39. 39. Domain
  40. 40. Functioning of particular [business] environment Understanding the terminology Creating language for all stories, conversations, customer tests & code
  41. 41. Freeform Domain Discussion
  42. 42. Customer
  43. 43. Why some one has to buy our product? decision process for purchasing a product
  44. 44. Personas
  45. 45. User Models Personas represent behavior patterns
  46. 46. Goals
  47. 47. A goal is an end condition, whereas a task is an intermediate step that helps to reach a goal.
  48. 48. Context
  49. 49. Design is Technology Dependent
  50. 50. where, when, and how frequently would the users interact with this task?
  51. 51. Tasks
  52. 52. A goal is an end condition, whereas a task is an intermediate step that helps to reach a goal.

×