1 / 54

Workplace studies with software teams

Workplace studies with software teams. Integrating Agile development with User Experience design Jennifer Ferreira jen.ferreira@ucalgary.ca Helen Sharp, Hugh Robinson. Outline. Integrating Agile development with UX design. Outline. Integrating Agile development with UX design

leora
Télécharger la présentation

Workplace studies with software teams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workplace studies with software teams Integrating Agile development with User Experience design Jennifer Ferreira jen.ferreira@ucalgary.ca Helen Sharp, Hugh Robinson

  2. Outline • Integrating Agile development with UX design

  3. Outline • Integrating Agile development with UX design • Problem?

  4. Outline • Integrating Agile development with UX design • Problem? • Workplace studies

  5. Outline • Integrating Agile development with UX design • Problem? • Workplace studies • Achieving integration

  6. Outline • Integrating Agile development with UX design • Problem? • Workplace studies • Achieving integration • Implications

  7. Intro Agile development + UX design

  8. Agile development XP Scrum FDD ASD

  9. *Design • interaction design [Patton 2002a] • usage centered design [Patton 2002b] • discount usability engineering [Kane 2003] • rapid contextual design [Beyer et al. 2004] • user experience design [Hodgetts 2005] • user centered design [Miller 2005] • scenario-based design [Lee and McCrickard 2007] • goal-directed design [Cho 2009]

  10. User Experience (UX) Design • ISO CD 9241-210 • “all aspects of the user’s experience when interacting with the product, service, environment or facility.”

  11. User Experience (UX) Design indicative of the collection of methods, tools, techniques, etc. for involving and maintaining focus on the end user in software development • - understand users • - design • - evaluate

  12. User Experience (UX) Design WORK indicative of the collection of methods, tools, techniques, etc. for involving and maintaining focus on the end user in software development • - understand users • - design • - evaluate

  13. Combination Agile development + UX design

  14. Debates • The place of UX design in Agile development • When what happens

  15. Debates • The place of UX design in Agile development • When what happens • - Up front • - In the Agile iterations

  16. Debates • The place of UX design in Agile development • When what happens • - Up front  BDUF • - In the Agile iterations

  17. Debates • The place of UX design in Agile development • When what happens • - Up front  BDUF • - In the Agile iterations BAD

  18. Debates • The place of UX design in Agile development • When what happens • - Up front  BDUF • - In the Agile iterations  too short BAD

  19. Debates • The place of UX design in Agile development • When what happens • - Up front  BDUF • - In the Agile iterations  too short BAD BAD

  20. Simplistic view comparisons of values and principles  process e.g. both Agile and UX are iterative and both focus on the customer/end user

  21. Simplistic view “The two-track organization is what we aimed for, although in reality it was a little more complex. Some designs needed longer than a single cycle to complete. For example, one particularly troublesome feature took us over 5 cycles before the design passed all of its goals.” Lynn Miller, "Case Study of Customer Input For a Successful Product," Agile Development Conference, pp. 225-234, Agile Development Conference (ADC'05), 2005.

  22. Workplace studies PhD thesis

  23. How are Agile development and UX design combined? • How is integration accomplished on a day-to-day basis? • Singer et al. “… little is known about how software engineers perform their work. In order to improve software engineering tools and practice, it is therefore essential to conduct field studies, i.e., to study real practitioners as they solve real problems.” • Janice Singer, Susan E. Sim, and Timothy C. Lethbridge (2008) Software Engineering Data Collection for Field Studies. Guide to Advanced Empirical Software Engineering. Forrest Shull, Janice Singer, Dag I.K. Sjøberg Editors. Pages 9—34, ISBN-13: 978-1-84800-043-8.

  24. How are Agile development and UX design combined? • How is integration accomplished on a day-to-day basis? • Only 4 of 23 empirical studies included observations of practice in work settings

  25. How are Agile development and UX design combined? • How is integration accomplished on a day-to-day basis? • Only 4 of 23 empirical studies included observations of practice in work settings •  Study practitioners in the workplace

  26. Workplace studies

  27. Workplace studies

  28. Same same but different • all three organisations • successful at delivering software • highly valued UX design • used Scrum different experiences of practice

  29. Same same but different • all three organisations • successful at delivering software • highly valued UX design • used Scrum different experiences of practice • the best way to create software

  30. How are Agile development and UX design combined? • Integration • On-going – negotiated, day-to-day, individuals • Achieved – variety of conditions: • Developers and designers were kept apart • Developers and designers were working closely together • Developer designers were trialling working closely together

  31. Integration as… • Expectations about acceptable behaviour • Mutual awareness • Negotiating progress • Engaging with each other

  32. Integration as… • Expectations about acceptable behaviour • Mutual awareness • Negotiating progress • Engaging with each other

  33. Expectations about acceptable behaviour • expectations about how the other group behaves • what developers expect • -- due to Scrum commitments • what UX designers expect • -- due to UX design commitments

  34. Expectations about acceptable behaviour “Could we have a meeting to give you some feedback?” “What kind of feedback do you want to give?” designers: expected to hand over designs and move onto the next project developers: expected to provide feedback as issues arose developers: expected designers to provide timely redesigns designers: not expecting on-going conversations Apart

  35. Expectations about acceptable behaviour “Which would be easier to implement?” “Either would be fine.” designers: expected developer to answer their questions developer: expected that the designers would have questions designers: expected that the developercould answer their questions designers: expected developer to have useful input Together

  36. Integration as… • Expectations about acceptable behaviour • Mutual awareness • Negotiating progress • Engaging with each other

  37. Mutual awareness • UX designers being aware of what constitutes work for Agile developers • Agile developers being aware of what constitutes work for UX designers • levels vary between the teams

  38. Mutual awareness “Are the designs ready?” “We're moving desks today.” Agile developers and UX designers seated on different floors rigid role boundaries Agile developers and UX designers on separate teams tense Apart

  39. Mutual awareness fluid role boundaries bonded team on-going conversations relaxed Together

  40. Integration as… • Expectations about acceptable behaviour • Mutual awareness • Negotiating progress • Engaging with each other

  41. Negotiating progress • Maintaining workflow under uncertainty • client expectations? (market, dependencies on other projects) • requirements • decision-makers are not always available • teams make progress in spite of this – they HAVE to

  42. Negotiating progress “Could we have a meeting to give you some feedback?” “What kind of feedback do you want to give?” reluctant phased formal a set of activities constrained Apart

  43. Negotiating progress “What do you remember from the client meeting?” “I think they wanted more pop.” on-the-fly informal agreed together Together

  44. Integration as… • Expectations about acceptable behaviour • Mutual awareness • Negotiating progress • Engaging with each other

  45. Engaging with each other • developers and designers do 2 types of work: • own • together • input • decision-making • expertise switch

  46. Engaging with each other “Could we have a meeting to give you some feedback?” “What kind of feedback do you want to give?” explicit require design expertise to proceed designers leading, developers releasing software developers approaching designers Apart

  47. Engaging with each other “What do you remember from the client meeting?” “I think they wanted more pop.” implicit status updates solution is negotiated clarifications Together

  48. Achieving integration • Systematic, separatist approach • walking around, finding • meetings, logistics • communicating via documents, up to date “Are the designs ready?” “We're moving desks today.” Apart

  49. Achieving integration • Subtle, on-going effort • shared awareness of design values and technical constraints • shared decision-making Together

  50. Findings • Not just about process • Teams are not isolated • Not just about seating the developers with designers (i.e. colocation) • Integration is shaped by organisational and team-level factors •  views on how best to create software

More Related