integrating ux and agile
Post on 26-Jan-2015
Embed Size (px)
DESCRIPTIONThe slides from my presentation on integrating UX and Agile/SCRUM at InfoCamp 2009.
- 1. Integrating UX and Agile /SCRUM
A work in progress
2. 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
3. Agile Principles
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.
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.
4. 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.
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.
5. Agile and UX start with the same problems:
Estimating scope is impossible
Deadline arent being met
Code needs to be rewritten
Software is unusable
Users arent part of the equation
Budgets run over
Everybody is frustrated
Insert your favorite painpoint here
6. 7. 8. Some things that neither UX nor Agile can Fix
Executives that change their mind every week
Poor judgment of people in control
Lack of corporate strategy
Inadequate skill set
Too many developers, not enough designers
9. Iteration Cycle Hierarchy
10. 11. 12. 13. 14. Some Guidelines
Collaborate closely with business owners
Collaborate closely with developers
Prioritize features based on user needs (research), business goals, and technical feasibility
Have a meeting with designers, developers, and business owners in one room
Users and customers are represented by designers and product managers
15. More Guidelines
Document the design
Keep design documentation current
Dont code too soon
Dont let developers talk to customers
Re-evaluate your process periodically and see what works for you and what doesnt.
Make it better
Let me know what works for you and what doesnt.
16. Daniel Jaeger
Interaction Design & Strategy