agile ux - conveyux
Post on 07-Dec-2014
564 Views
Preview:
DESCRIPTION
TRANSCRIPT
Agile and UX:Embrace or Tolerate
Rob Keefer@rbkeefer
@pomietwww.pomiet.com
So, Embrace It or Tolerate It,
Be Agile
promote GOOD DESIGN, and
Big Idea
Things go better when done with others -
@pomietwww.pomiet.com
Challenges
Agile is developer-centric
Little time for design up-front
Little time for tests
@pomietwww.pomiet.com
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
Work in Parallel with Developers
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
Work in Parallel
@pomietwww.pomiet.com
Work in Parallel with Developers
Work within the process
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
Work in Parallel with Developers
Work within the process
Use short tests during the cycle (Perform larger tests out of cycle)
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
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
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
Do-Go Map
@pomietwww.pomiet.com
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 Conversation)
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
Stories: Invitation to a Conversation
@pomietwww.pomiet.com
Wireframes: Invitation to a Conversation
@pomietwww.pomiet.com
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 Conversation)
Turn Developers into Designers
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
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
@pomietwww.pomiet.com
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 Conversation)
Turn Developers into Designers
6 Tips for Working in an Agile Environment
@pomietwww.pomiet.com
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
@pomietwww.pomiet.com
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
@pomietwww.pomiet.com
Things go better when done with others -
So, Embrace It or Tolerate It,
Be Agile
promote GOOD DESIGN, and
Big Idea
@pomietwww.pomiet.com
Continue the Conversation
Rob Keefer, PhD
Rob.Keefer@pomiet.com
@rbkeefer
@pomietwww.pomiet.com
@pomietwww.pomiet.com
How do I prioritize a feature?
Use Role and Task Priority Determine the Feature PriorityUse details about the user role that benefits from the feature and the task that the feature supports.
@pomietwww.pomiet.com
How can I be sure I haven’t missed something?
Reconcile Roles and Goals with TasksFor 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.
top related