1 / 59

User Centered Interaction Design

User Centered Interaction Design. in Agile Environment. www.henryjacob.com. What customer want?. $. Dollar Printing Machine. II Give them tools which helps them to make money(legally). A good system is something which eliminates existing tasks(wherever its possible),

wilda
Télécharger la présentation

User Centered Interaction Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. User Centered Interaction Design in Agile Environment

  2. www.henryjacob.com

  3. What customer want?

  4. $

  5. Dollar Printing Machine II Give them tools which helps them to make money(legally)

  6. A good system is something which eliminates existing tasks(wherever its possible), or speedup the tasks with efficiency, save money and time.

  7. Engineering Business Design

  8. Design + Engineering + Business Design + Engineering Engineering

  9. Engineering Business Design

  10. Deciding what to build It is all about how we develop stories

  11. “Plan for artifacts, whose form, content, behavior is useful, usable, desirable, as well as economically viable, and technically feasible” – Alan Cooper

  12. The hardest single part of building a software system is deciding precisely what to build? -- Fred Brooks

  13. Engineering Business Design

  14. Agile is an Engineering Process

  15. Planning Game Story Card Planning Game Stories Iteration Plan Release Plan Decide on scope and priorities Estimate cost and schedule Benchmark for feedback

  16. Who does the design?

  17. Customer Users Programmer Graphics Designer

  18. software development is not just about coding

  19. Can you imagine Windows without mouse?

  20. Customer Users Programmer Graphics Designer

  21. Interaction Designer Application Architect Solution Architect

  22. Customer SME Architect Users

  23. Design Game Design Game Stories Design Team

  24. Planning Game Planning Game Story Card Iteration Plan Release Plan Design Team

  25. 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.

  26. Design involves a sizable up-front activities

  27. Design Domain Personas Customer Goal Tasks Context Objects

  28. Design Domain Personas Customer Goal Tasks Context Objects

  29. StocksDirect.com SD.com Buy Stocks MyStocks Sell Domain:Stock Trading, Stock Exchange Entities/Objects:Stocks, User Tasks:login, Buy, List, Sell

  30. Alex Shekar

  31. StocksDirect.com Agent Shekar

  32. Alex LOGIN USRNAME:PWD SELL STOCK_SYMBOL

  33. Design Domain Personas Customer Goal Tasks Context Objects

  34. Alex Shekar Customer Goal: More Transaction Potential Users: Working Professional – Especially IT and Sales Personas: Shekar, Alex Context:Shekar - Work Environment & Work, Alex - Always on Move

  35. “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

  36. A good system is something which eliminates existing tasks(wherever its possible), or speedup the tasks with efficiency, save money and time.

  37. Engineering Business Design

  38. Interaction Designer Application Architect Solution Architect

  39. Design Domain Personas Customer Goal Tasks Context Objects

  40. Planning Game Planning Game Story Card Iteration Plan Release Plan Design Team

  41. “If the software were magic, what would it do?”

  42. Domain

  43. Functioning of particular [business] environment Understanding the terminology Creating language for all stories, conversations, customer tests & code

  44. Freeform Domain Discussion

  45. Customer

  46. Why some one has to buy our product? decision process for purchasing a product

More Related