Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Integrating UX and Agile /SCRUM<br />A work in progress<br />
Agile Values<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documenta...
Agile Principles<br />Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable soft...
The most efficient and effective method of conveying information to and within a development team is face-to-face conversa...
Agile and UX start with the same problems:<br />Estimating scope is impossible<br />Deadline aren’t being met<br />Code ne...
Some things that neither UX nor Agile can Fix<br />Executives that change their mind every week<br />Poor judgment of peop...
Iteration Cycle Hierarchy<br />
Some Guidelines<br />Research first<br />Design second<br />Collaborate closely with business owners<br />Collaborate clos...
More Guidelines<br />Document the design<br />Keep design documentation current<br />Don’t code too soon<br />Don’t let de...
Daniel Jaeger<br />Interaction Design & Strategy<br />daniel@citizenbrain.com<br />www.citizenbrain.com<br />
?<br />
Upcoming SlideShare
Loading in …5
×

Integrating Ux And Agile

1,491 views

Published on

The slides from my presentation on integrating UX and Agile/SCRUM at InfoCamp 2009.

Published in: Design, Technology, Business
  • Be the first to comment

Integrating Ux And Agile

  1. 1. Integrating UX and Agile /SCRUM<br />A work in progress<br />
  2. 2. Agile Values<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Customer collaboration over contract negotiation<br />Responding to change over following a plan <br />
  3. 3. Agile Principles<br />Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software. <br />Welcome changing requirements, even late in development. Agile processes harness change for the customer&apos;s competitive advantage. <br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. <br />Business people and developers must work together daily throughout the project. <br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />
  4. 4. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. <br />Working software is the primary measure of progress. <br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. <br />Continuous attention to technical excellence and good design enhances agility. <br />Simplicity--the art of maximizing the amount of work not done--is essential. <br />The best architectures, requirements, and designs emerge from self-organizing teams. <br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. <br />
  5. 5. Agile and UX start with the same problems:<br />Estimating scope is impossible<br />Deadline aren’t being met<br />Code needs to be rewritten<br />Software is unusable<br />Users aren’t part of the equation<br />Budgets run over<br />Everybody is frustrated<br />Insert your favorite painpoint here<br />
  6. 6.
  7. 7.
  8. 8. Some things that neither UX nor Agile can Fix<br />Executives that change their mind every week<br />Poor judgment of people in control<br />Lack of corporate strategy<br />Inadequate skill set<br />Too many developers, not enough designers<br />
  9. 9. Iteration Cycle Hierarchy<br />
  10. 10.
  11. 11.
  12. 12.
  13. 13.
  14. 14. Some Guidelines<br />Research first<br />Design second<br />Collaborate closely with business owners<br />Collaborate closely with developers<br />Prioritize features based on user needs (research), business goals, and technical feasibility<br />Have a meeting with designers, developers, and business owners in one room<br />Users and customers are represented by designers and product managers<br />
  15. 15. More Guidelines<br />Document the design<br />Keep design documentation current<br />Don’t code too soon<br />Don’t let developers talk to customers<br />Re-evaluate your process periodically and see what works for you and what doesn’t.<br />Make it better<br />Let me know what works for you and what doesn’t.<br />
  16. 16. Daniel Jaeger<br />Interaction Design & Strategy<br />daniel@citizenbrain.com<br />www.citizenbrain.com<br />
  17. 17. ?<br />

×