Your SlideShare is downloading. ×
0
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
Agile UX
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

Agile UX

608

Published on

There are challenges in bringing UX and Agile processes together. This presentation contains 6 tips for incorporating these practices together.

There are challenges in bringing UX and Agile processes together. This presentation contains 6 tips for incorporating these practices together.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
608
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
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. AGILE UX: Embrace or Tolerate Rob Keefer @rbkeefer
  • 2. @pomietpomiet.com@rbkeefer Process Overview BACKLOG PLAN WORK REVIEW RELEASE PRODUCTRETROSPECTIVE PROJECT Product Owner: Represents all stakeholders. Team: Implementers of the cycle goals. Project Manager: Responsible for the success of the project. Stakeholders: Interested in product’s outcome as investors and users. Developers:Practice code craftsmanship: TDD, continuous integration, refactor mercilessly
  • 3. @pomietpomiet.com@rbkeefer Big Idea So, Embrace It or Tolerate It, Be Agile promote GOOD DESIGN, and Things go better when done with others -
  • 4. @pomietpomiet.com@rbkeefer Challenges Agile is developer-centric Little time for design up-front Little time for tests
  • 5. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers
  • 6. @pomietpomiet.com@rbkeefer Work in Parallel
  • 7. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers Work within the process
  • 8. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers Work within the process Use short tests during the cycle (Perform larger tests out of cycle)
  • 9. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers Work within the process Use short tests during the cycle (Perform larger tests out of cycle) Rely heavily on Information Architecture
  • 10. @pomietpomiet.com@rbkeefer Do-Go Map
  • 11. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers Work within the process Use short tests during the cycle (Perform larger tests out of cycle) Rely heavily on Information Architecture Use just-in-time Documentation (invitation to a conversation)
  • 12. @pomietpomiet.com@rbkeefer Stories: Invitation to a Conversation
  • 13. @pomietpomiet.com@rbkeefer Wireframes: Invitation to a Conversation
  • 14. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers Work within the process Use short tests during the cycle (Perform larger tests out of cycle) Rely heavily on Information Architecture Use just-in-time Documentation (invitation to a conversation) Turn Developers into Designers
  • 15. @pomietpomiet.com@rbkeefer Developers into Designers Goal: Train developers to do the little things so that you can do the interesting things. Teach them to Value: • People over Features • User Feedback over Generalized Opinions • Ease of Use over Ease of Development • Discovery over Documentation
  • 16. @pomietpomiet.com@rbkeefer 6 Tips for Working in an Agile Environment Work in Parallel with Developers Work within the process Use short tests during the cycle (Perform larger tests out of cycle) Rely heavily on Information Architecture Use just-in-time Documentation (invitation to a conversation) Turn Developers into Designers
  • 17. @pomietpomiet.com@rbkeefer If your stomach knots when you get in the car in the morning, something is wrong with your project and it’s your job to effect the change. - Kent Beck, Extreme Programming Explained
  • 18. @pomietpomiet.com@rbkeefer The heart of Scrum is assessing the condition of activities and determining what to do next. This determination arises from experience, training and common sense. - Ken Schwaber, Agile Software Development
  • 19. @pomietpomiet.com@rbkeefer Big Idea So, Embrace It or Tolerate It, Be Agile promote GOOD DESIGN, and Things go better when done with others -
  • 20. @pomietpomiet.com@rbkeefer Rob Keefer, PhD Rob.Keefer@pomiet.com @rbkeefer Continue the Conversation
  • 21. @pomietpomiet.com@rbkeefer How do I prioritize a feature? Use Role and Task Priority Determine the Feature Priority Use details about the user role that benefits from the feature and the task that the feature supports. Risk Business Value High Risk Low Value Low Risk Low Value High Risk High Value Low Risk High Value AVOID PRIORITY OPPORTUNITY SUPPORT
  • 22. @pomietpomiet.com@rbkeefer How can I be sure I haven’t missed something? Reconcile Roles and Goals with Tasks For each goal associated with a role, ensure that a task exists to help the person achieve the goal. Make sure that the features support the goal.

×