integrating ux and agile pssigchi panel discussion oct. 22, 2009
DESCRIPTION
The slides from my introductory presentation for the panel discussion on integrating UX and Agile/SCRUM at the Puget Sound SIGCHI event on Oct. 22, 2009.TRANSCRIPT
Integrating UX and Agile /SCRUM
A work in progress
CitizenBrain
Estimating scope is impossible Deadline aren’t being met Code needs to be rewritten Software is unusable Users aren’t part of the equation Budgets run over Everybody is frustrated Insert your favorite painpoint here
UX And Agile Address The Same Problems
CitizenBrain
Agile Values Individuals and interactions over
processes and tools Working software over
comprehensive documentation Customer collaboration over contract
negotiation Responding to change over following
a plan
CitizenBrain
Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Agile Principles
CitizenBrain
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
CitizenBrain
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
CitizenBrain
Design Process (Cooper)
CitizenBrain
Product Development Process (Cooper)
CitizenBrain
Lack of corporate strategy Executives that change their mind every week Poor judgment of people in control Lack of adequate accounting Lack of quality/success metrics Inadequate skill sets Too many developers, not enough designers
Things That Neither UX Nor Agile Can Fix
CitizenBrain
Iteration Cycle Hierarchy
CitizenBrain
CitizenBrain
Research first, design second, code third Collaborate closely with business owners Collaborate closely with developers Have a meeting with designers, developers,
and business owners in one room to… …prioritize features based on user needs,
business goals, and technical feasibility Users and customers are represented by
designers and product managers
Some Guidelines
CitizenBrain
More Guidelines Document the design Keep design documentation current Start coding when you know what you’re
building Let designers and/or researchers talk to
customers and users Re-evaluate your process periodically. Make it better Let me know what works for you
CitizenBrain
Daniel JaegerInteraction Design & Strategy206.334.2500daniel@citizenbrain.comwww.citizenbrain.comTwitter: CitizenBrain
CitizenBrain
?