Integrating Ux And Agile PSSIGCHI Panel Discussion Oct. 22, 2009

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    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.

    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.

    You would think they’re a match made in heaven. But like any relationship, it is hard work to make it work.

    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. Right to left is time

    1 Favorite

    Integrating Ux And Agile PSSIGCHI Panel Discussion Oct. 22, 2009 - Presentation Transcript

    1. CitizenBrain
      Integrating UX and Agile /SCRUM
      A work in progress
    2. CitizenBrain
      UX And Agile Address 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
    3. 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
    4. CitizenBrain
      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.
    5. 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.
    6. 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.
    7. CitizenBrain
      Design Process (Cooper)
    8. CitizenBrain
      Product Development Process (Cooper)
    9. CitizenBrain
      Things That Neither UX Nor Agile Can Fix
      • 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
    10. CitizenBrain
      Iteration Cycle Hierarchy
    11. CitizenBrain
    12. CitizenBrain
      Some Guidelines
      • 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
    13. 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
    14. CitizenBrain
      Daniel Jaeger
      Interaction Design & Strategy
      206.334.2500
      daniel@citizenbrain.com
      www.citizenbrain.com
      Twitter: CitizenBrain
    15. ?
    SlideShare Zeitgeist 2009

    + Daniel JaegerDaniel Jaeger Nominate

    custom

    208 views, 1 favs, 0 embeds more stats

    The slides from my introductory presentation for th more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 208
      • 208 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 7
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories