Integrating Ux And Agile
Upcoming SlideShare
Loading in...5
×
 

Integrating Ux And Agile

on

  • 1,997 views

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

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

Statistics

Views

Total Views
1,997
Views on SlideShare
1,992
Embed Views
5

Actions

Likes
9
Downloads
40
Comments
0

1 Embed 5

http://www.slideshare.net 5

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • The work in progress actually refers to a lot of things – this presentation, my own approach to integrating UX and Agile and the general state of software development processes.
  • Agile and UX or interaction design really started with the same problems.
  • You would think they’re a match made in heaven. But like any relationship, it is hard work to make it work.
  • A lot of people seem to think that Agile / Scrum is the silver bullet to solve all these problems. Interestingly enough, nobody other than designers seem to think that interaction design or user experience is a silver bullet.
  • I believe for most products you can find a level of goals that don’t change over time or at lease only every 100 or 50 years. This is very general but it serves as an anchor for everything else.What changes is the technology.

Integrating Ux And Agile Integrating Ux And Agile Presentation Transcript

  • Integrating UX and Agile /SCRUM
    A work in progress
  • 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
  • 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.
  • 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.
  • Agile and UX start with the same problems:
    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
  • 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
  • Iteration Cycle Hierarchy
  • Some Guidelines
    Research first
    Design second
    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
  • More Guidelines
    Document the design
    Keep design documentation current
    Don’t code too soon
    Don’t let developers talk to customers
    Re-evaluate your process periodically and see what works for you and what doesn’t.
    Make it better
    Let me know what works for you and what doesn’t.
  • Daniel Jaeger
    Interaction Design & Strategy
    daniel@citizenbrain.com
    www.citizenbrain.com
  • ?