Your SlideShare is downloading. ×
Design and UX in an Agile Process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Design and UX in an Agile Process

39,153
views

Published on

My talk on how to adjust an agile process to accommodate design and UX, as given at the Web 2.0 Expo in New York in September, 2008.

My talk on how to adjust an agile process to accommodate design and UX, as given at the Web 2.0 Expo in New York in September, 2008.

Published in: Technology, Business

14 Comments
287 Likes
Statistics
Notes
No Downloads
Views
Total Views
39,153
On Slideshare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
3,015
Comments
14
Likes
287
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Web 2.0 Expo / NYC / 2008 DESIGN & UX IN AN AGILE PROCESS M. JACKSON WILKINSON
  • 2. First things first... Who is This Dude?
  • 3. A Short History of SOFTWARE DEVELOPMENT PROCESSES
  • 4. A (REALLY) Short History of (CERTAIN) SOFTWARE DEVELOPMENT PROCESSES
  • 5. Source: I wish I knew
  • 6. THE PRACTICE: CHAOS
  • 7. The Solution? WATERFALL
  • 8. INCREMENTAL
  • 9. REQUIREMENTS DESIGN DEVELOPMENT TESTING MAINTENANCE
  • 10. DOCUMENTED
  • 11. http://www.flickr.com/photos/simona_/2194407083/
  • 12. GATHER PROBLEM IDENTIFY DESIGN SOLUTION IMPLEMENT TIME
  • 13. GATHER PROBLEM IDENTIFY DESIGN SOLUTION IMPLEMENT TIME
  • 14. GATHER PROBLEM IDENTIFY DESIGN SOLUTION IMPLEMENT TIME
  • 15. The Solution? WATERFALL
  • 16. Failure
  • 17. REQUIREMENTS DESIGN DEVELOPMENT TESTING MAINTENANCE
  • 18. REQUIREMENTS DESIGN DEVELOPMENT TESTING MAINTENANCE
  • 19. SPECIALIZATION
  • 20. SPECIALIZATION
  • 21. The Solution? AGILE
  • 22. ITERATIVE
  • 23. REQUIREMENTS DESIGN PREPARATION CYCLE RELEASE DEVELOPMENT TESTING
  • 24. PROTOTYPE BETA LAUNCH PLANNING CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE MAINTENANCE
  • 25. ADAPTABLE
  • 26. PROTOTYPE BETA LAUNCH PLANNING CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE MAINTENANCE
  • 27. PROTOTYPE BETA LAUNCH PLANNING CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE MAINTENANCE
  • 28. RAPID
  • 29. REQUIREMENTS DESIGN PREPARATION CYCLE RELEASE DEVELOPMENT TESTING One to Four Weeks
  • 30. PROTOTYPE BETA LAUNCH PLANNING CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE MAINTENANCE
  • 31. COOPERATIVE
  • 32. REQUIREMENTS DESIGN DEVELOPMENT TESTING MAINTENANCE
  • 33. QUALITY-DRIVEN
  • 34. The Truth About AGILE IN PRACTICE
  • 35. DOGMATIC
  • 36. PROTOTYPE BETA LAUNCH PLANNING CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE MAINTENANCE
  • 37. CYCLE INTERFACE DESIGN VISUAL DESIGN BUILD-OUT DEVELOPMENT TWO WEEKS
  • 38. CYCLE USER RESEARCH? INTERFACE DESIGN ORIGINAL THOUGHT? VISUAL DESIGN BUILD-OUT USER TESTING? DEVELOPMENT TWO WEEKS
  • 39. Rounded Corners Drop Shadows Reflections Pastels Helvetica Gradients FTW!
  • 40. PROTOTYPE BETA LAUNCH PLANNING CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE MAINTENANCE
  • 41. REQUIREMENTS UI DESIGN PROTOTYPE BETA LAUNCH VISUAL DESIGN CYCLE CYCLE CYCLE CYCLE CYCLE CYCLE
  • 42. AGILE TENDS TO YIELD WATERFALL
  • 43. NOW THAT WE KNOW WHAT DOESN’t work, it’s time to start FIXING IT
  • 44. Fixing Agile for Designers Let’s Review the GOALS
  • 45. ITERATIVE
  • 46. ADAPTABLE
  • 47. RAPID
  • 48. COOPERATIVE
  • 49. QUALITY-DRIVEN
  • 50. Fixing Agile for Designers SKEW PROJECT CYCLES
  • 51. CYCLE INTERFACE DESIGN VISUAL DESIGN BUILD-OUT DEVELOPMENT TWO WEEKS
  • 52. CYCLE INTERFACE DESIGN VISUAL DESIGN / BUILD-OUT DEVELOPMENT TWO WEEKS
  • 53. CYCLE N-1 INTERFACE DESIGN CYCLE N+1 CYCLE N-1 VISUAL DESIGN / BUILD-OUT CYCLE N+1 CYCLE N-1 DEVELOPMENT CYCLE N+1
  • 54. CYCLE N-1 INTERFACE DESIGN CYCLE N+1 CYCLE N-1 VISUAL DESIGN / BUILD-OUT CYCLE N+1 CYCLE N-1 DEVELOPMENT CYCLE N+1
  • 55. Fixing Agile for Designers Make Use OF CYCLE 0
  • 56. CYCLE 0 INTERFACE DESIGN CYCLE 2 CYCLE 0 VISUAL DESIGN / BUILD-OUT CYCLE 2 CYCLE 0 DEVELOPMENT CYCLE 2
  • 57. RESEARCH
  • 58. AGGREGATE SURVEYS INTERVIEWS ANALYTICS RESEARCH PERSONAS TESTING CARD SORTING COMPETITIVE
  • 59. PRODUcT DESIGN
  • 60. COMPETITIVE ANALYSIS FEATURE QUADRANTS PRODUCT DESIGN SURVEYS BRAINSTORMING MARKET ANALYSIS
  • 61. OVERHEAD
  • 62. CERTIFICATES SUBVERSION HOSTING DEVELOPMENT OVERHEAD CODE INTEGRATION STAGING DEVELOPMENT ENVIRONMENTS
  • 63. MOOD BOARDS
  • 64. COLOR TITLES TEXTURE MOOD / STYLE BOARDS LOOK/FEEL INSPIRATION STYLES
  • 65. DEFINING “DONE”
  • 66. Fixing Agile for Designers Start Cycles With PLANNING
  • 67. USER STORIES
  • 68. USERS SHOULD BE ABLE TO UPLOAD MULTIPLE PHOTOS AT ONCE
  • 69. TEST PLANS
  • 70. USERS SHOULD BE ABLE TO UPLOAD MULTIPLE PHOTOS AT ONCE - Test with JPEG, PNG, GIF (supported) - Test with an unsupported image format - Test with Flash not present - Test with more than 20 MB of total POST data
  • 71. CYCLE PLANNING
  • 72. 8 USERS SHOULD BE ABLE TO UPLOAD 6 MULTIPLE PHOTOS AT ONCE - Test with JPEG, PNG, GIF (supported) 2 4 - Test with an unsupported image format - Test with Flash not present - Test with more than 20 MB of total POST data
  • 73. 8 USERS SHOULD BE ABLE TO UPLOAD 8 MULTIPLE PHOTOS AT ONCE - Test with JPEG, PNG, GIF (supported) 2 4 - Test with an unsupported image format - Test with Flash not present - Test with more than 20 MB of total POST data
  • 74. 8 USERS SHOULD BE ABLE TO UPLOAD 8 MULTIPLE PHOTOS AT ONCE - Test with JPEG, PNG, GIF (supported) 2 4 - Test with an unsupported image format - Test with Flash not present - Test with more than 20 MB of total POST data This Story: 14 hours
  • 75. COLLABORATIVE UX/UI
  • 76. USE Documents As COMMUNICATION
  • 77. Fixing Agile for Designers GET EVERYONE IN STAND-UP
  • 78. Virtual STand-UP Jackson Yesterday: Finished wireframing the rating features, all updated wireframes are in SVN. Today: Testing image upload interface from C3; diving into some user flows for C4. Blockers: None for now.
  • 79. Fixing Agile for Designers Emphasize VALIDATION
  • 80. FIT IN USER TESTING
  • 81. HAVE DEVELOPERS GIVE PUBLIC DEMOS
  • 82. GET THE TEAM INTO ACCEPTANCE TESTING
  • 83. WHAT IF YOUR PROCESS IS NOT FIXED YET?
  • 84. Process still not working? BE AGILE
  • 85. Process still not working? FOCUS ON THE GOALS
  • 86. ITERATIVE
  • 87. ADAPTABLE
  • 88. RAPID
  • 89. COOPERATIVE
  • 90. QUALITY-DRIVEN
  • 91. THANKS! jackson@viget.com http://viget.com http://jounce.net

×