De techniek van Agile Prototyping werd door Involved in huis ontwikkeld. Het is de tegenslag en de uitdagingen die we de afgelopen jaren op projecten tegenkwamen die de uitwerking van deze techniek bepaald hebben. Agile Prototyping is een algemene projectaanpak waarbij het gekende SCRUM framework met enkel zeer specifieke zaken wordt uitgebreid. Het zijn concrete taken uit de wereld van User-Experience Design in combinatie met enkele specifieke "regels" die ons helpen sneller, betere software op te leveren. Concreet helpt Agile Prototyping om het voortschrijdend inzicht te versnellen, het budget onder controle te houden en de kwaliteit van het finale product te verbeteren.

1. Agile prototyping
Project Experience for clients and developers

2. About Involved1
Software Projects are hard
Agile solves everything
User-Experience Design solves everything
2
3
4
Agenda
Agile Prototyping5

3. About Involved
1.

4. Een groep van 24 nuchtere software
engineers met een focus op het ontwerpen,
bouwen en leveren van web-applicaties
met een unieke gebruikerservaring.

5. www.involved-it.be

6. Software projects
are hard
2.

7. reason #1
Business People don’t know
what they want
And it isn’t their fault

8. reason #2
Scope Creep

9. reason #3
Requirements are
“to little, to late”

10. reason #4
Money is being wasted,
constantly

11. Business Peoplehate softwareprojects

12. Agile solves
everything
3.

13. Lean Thinking

14. Toyota Production System

15. Value

16. The Unimportance of Practically
Everything

17. The 7 types of Waste or Muda
Overproduction1
Rework2
Waiting3
Inventory4
Transport5
Motion6
Proces7

18. Muda

19. SCRUM

20. User Story

21. Product Backlog

22. SCRUM Framework
ScrumMaster
Daily Scrum
Meeting and
Artifacts Update
Review
Potentially
Shippable Product
Increment
Retrospective
Sprint
1-4 weeks
Team
Product Backlog
Sprint Planning
Meeting
Product Owner
Team selects how
much to commit to
for the next sprint.
Input from end-users,
customers and other
stakeholders.

23. DevelopmentAnalysis
time
workload Waterfall

24. Analysis
time
workload
Development
Agile

25. SCRUM Framework
ScrumMaster
Daily Scrum
Meeting and
Artifacts Update
Review
Potentially
Shippable Product
Increment
Retrospective
Sprint
1-4 weeks
Team
Product Backlog
Sprint Planning
Meeting
Product Owner
Team selects how
much to commit to
for the next sprint.
Input from end-users,
customers and other
stakeholders.

26. SCRUM Framework
ScrumMaster
Daily Scrum
Meeting and
Artifacts Update
Review
Potentially
Shippable Product
Increment
Retrospective
Sprint
1-4 weeks
Team
Product Backlog
Sprint Planning
Meeting
Product Owner
Team selects how
much to commit to
for the next sprint.
Input from end-users,
customers and other
stakeholders.

27. Problems with SCRUM
Textual Documentation
-
No focus on User-Experience
-
Feedback after development

28. Muda

29. User Experience Design
Solves Everything
4.

30. User-Centered Design
!=
User-Experience

31. User Centered Design

32. User Experience

33. Let’s call it User-Experience Design.

34. User-Experience Design put topractice

35. Persona

36. Context or Scenario
87%of mobile internet
users are using
their devices
while watching TV

37. Sketching

38. Storyboarding

39. Wireframing

40. Prototyping

42. Nobody reads analysis document

43. Nobody understands analysis document

45. User Testing

46. User-Experience Design inreality

47. Step #1 – Hire a UX Hipster

48. Analysis
time
workload
Development
Step #2 – Introduce UX-Spike

49. Analysis
time
workload
Development
UX
Step #2 – Introduce UX-Spike

50. Step #3 – Admire his creations

51. Step #4 – Build it and die

52. Analysis
time
workload
Development
UX
UX Spike is bad practice

53. Problems with User-Experience Design
UX-Spike approach often used
-
Disconnect UCD-Process and Development
-
Disconnect UCD-Process and FunctionalAnalysis

54. Muda

55. Recap !

56. DevelopmentAnalysis
time
workload Level #1 – Waterfall

57. time
workload
Development
Analysis
Level #2 – SCRUM

58. Analysis
time
workload
Development
UX
Level #3 – User-Experience Design (UX-Spike)

59. Analysis
time
workload
Development
Agile Prototyping
Level #4 – Agile Prototyping

60. Agile Prototyping
5.

61. Analysis
time
workload
Development
Agile Prototyping
Agile Prototyping

62. Sprint
UX
Workshops and
User-Testing
UX-Expert / Proxy
Product Owner
Sprint Planning
Agile Prototyping

63. Team
Proxy Product Owner
& UX-Expert
Product Owner
& Users
Sprint - 8Sprint - 7 Sprint - 9 Sprint - 10
User Stories & Prototype Revised User Stories &
Prototype
Feedback
Input & Feedback
Sprint
Planning
Development
Shippable
Product
Demo
Agile Prototyping

64. Advantages
Less Waste
-
Better User Experience
-
Money well spent

65. User-Centered Software Design & Delivery
Send us a message
E-mail
You can contact us at
post@involved-it.be
Or me directly at
rik.vancamp@involved-it.be
Our address
Veldkant 33a
2550 Kontich
On the web
www.involved-it.be
twitter.com/involved_it
linkedin.com/involved