Agile Ucd

901 views
784 views

Published on

Published in: Technology, Business
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
901
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
0
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

Agile Ucd

  1. 1. Making Deliverables  Making Deliverables Consumable By The Designers
  2. 2. Why can’t developers and designers Wh ’d l dd i understand each other?
  3. 3. What is the use of We need to do  designers when we  di h User study… are the one who  build applications
  4. 4. Why do you need  Why do you take 3  the screens, we  days to come up  first  need to make the  fi t dt k th with a wireframe,  ith if work flow and  which looks like a  architecture scribble
  5. 5. If its just a sketch  why can’t you  accommodate the  d t th changes in  requirement?
  6. 6. Because they don’t speak  the same language! the same language!
  7. 7. Do you think users are  important ? important ?
  8. 8. Users, not technology, drive the  product’s success
  9. 9. So, What is User Centered Design?
  10. 10. • Example of bottle design Example of bottle design • Manufacturing design and UCD design
  11. 11. An approach  With  that supports  User‐centered  the entire  activities development  process So, What is User Centered Design?
  12. 12. An approach  In order to  With  that supports  create  User‐centered  the entire  applications activities development  process So, What is User Centered Design?
  13. 13. An approach  In order to  With  Which are easy  that supports  create and are  User‐centered  to use the entire  applications activities of added value  development  to the intended  process users. So, What is User Centered Design?
  14. 14. What do we do?
  15. 15. The client gave us “sample”  screens , requirements  screens requirements and information finalized
  16. 16. Application redesign Requirements fixed
  17. 17. Concept fixed
  18. 18. Concept fixed
  19. 19. Product Strategy
  20. 20. Product innovation
  21. 21. Product innovation
  22. 22. Product innovation
  23. 23. Which means, we are saying …
  24. 24. Good design is good business  Good design is good business – TJ Watson, founder IBM
  25. 25. Good design is  For good business Good design is ‘For’ good business 
  26. 26. To sum up, design helps business To sum up, design helps business The biggest cost benefit that UCD can provide is by more accurately  • defining requirements.  – A change made late in the design process will typically cost ten times  more than if the change were identified during requirements.  – Making changes to working systems will cost about one hundred times  more.  Design helps in making a better product  • – by innovation and better interaction, aesthetics – by acting as a business differentiator by acting as a business differentiator.
  27. 27. How do we do it ?
  28. 28. How do we do it ?
  29. 29. How do we do it ?
  30. 30. How do we do it ? H d d i?
  31. 31. Process diagram – actors, roles, relationships, questions Gram e’Arth
  32. 32. Let us condense this a nut shell… Business Product User Technology User Requirement We are here to help you build things….
  33. 33. Hand in Hand with Agile
  34. 34. Product Pd Planning Pl i Building B ildi Stakeholder  Concept Product Owner Product Owner Designer +  Designer + Stakeholder Team Developer Hand in Hand with Agile
  35. 35. Planning Product Pd Building B ildi Product Owner Stakeholder  Concept Team Designer +  Designer + Designer + Product  Stakeholder Developer manager +  User Representative Hand in Hand with Agile
  36. 36. Product Building B ildi Planning Pl i Concept Stakeholder  Market research + Business Goals Business Goals Agile and UCD Process
  37. 37. Planning Product Building B ildi Concept Phase 0:  User requirement  User requirement gathering Phase 1:  Ph 1 Feature list,  according to priority 1. 2, 3,4, 5 …. Break it into  independent  independent modules (stories) A (1, 2, 3) , B (4, 5) Agile and UCD Process
  38. 38. Building Developer Designer Release A Research 1+2 D l R h 1 2 Development  Design 1  groundwork Design 2  Design 2 Develop 1 Develop 1 Release B Rl B Research 3 Design 3  Develop 2 Research 4 Test 1  Product Agile and UCD Process
  39. 39. How this helps…. How this helps…. • Better understanding of the problem Better understanding of the problem. • Allows rapid testing and validation of story  concepts before time consuming coding. concepts before time consuming coding • Provides a clear, sociable visual representation  of the project vision. fh j ii • Engaging the end user as a customer. • Improves basis for estimation. • Mitigates project risk Mitigates project risk.
  40. 40. UCD in an agile environment UCD in an agile environment • Ideal Role Sharing Ideal Role Sharing • Team Based • Team (designer + developer) takes ownership  (d i dl )k hi of the design • Provides the vision of the design for multiple  development cycles
  41. 41. Thank you !

×