My earlier presentation from Agile India Bangalore - 2005

1. User Centered Interaction Design
in Agile Environment
Agile India
Bangalore
2005

2. www.henryjacob.com

3. What customer want?

4. $

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

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

9. Engineering Business
Design

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

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

12. Engineering Business
Design

13. XP is an Engineering Process

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

15. Who does the design?

16. Customer Users Programmer Graphics Designer

17. software development is
not just about coding

18. Can you imagine Windows
without mouse?

19. Customer Users Programmer Graphics Designer

20. Interaction Designer
Application Architect
Solution Architect

21. Customer
SME
Architect
Users

22. Design Game
Design
Game
Stories
Design Team

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

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

25. Design involves a
sizable up-front activities

26. Domain
Customer
Personas
Goal
Design
Tasks
Context
Objects

27. Domain
Customer
Personas
Goal
Design
Tasks
Context
Objects

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

30. Shekar Alex

31. StocksDirect.com Agent
Shekar

32. Alex LOGIN USRNAME:PWD
SELL STOCK_SYMBOL

33. Domain
Customer
Personas
Goal
Design
Tasks
Context
Objects

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

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. Domain
Customer
Personas
Goal
Design
Tasks
Context
Objects

40. Planning Game
Story Card
Planning Iteration Plan
Game
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

47. Personas

48. User Models
Personas represent behavior
patterns

49. Goals

50. A goal is an end condition,
whereas a task is an
intermediate step that helps to
reach a goal.

51. Context

52. Design is Technology
Dependent

53. where, when, and how frequently
would the users interact with this
task?

54. Tasks

55. A goal is an end condition,
whereas a task is an
intermediate step that helps to
reach a goal.