Download to read offline
More Related Content
Similar to Lessons learned integrating ux into agile teams.2012.08.with notes
Lessons learned integrating ux into agile teams.2012.08.with notes
- 1. LESSONS LEARNED INTEGRATING UXINTO AGILE TEAMS Brian Sobus
- 2. About Me I aman Agile Methodologist & Practitioner, a Software Developer, and a Software Director based in Raleigh, NC. In these roles and a few others, I’ve helped guide companies, teams, and individuals in their development, careers, and decisions. I am President and Principal Developer for Snowglobe Software Development, Inc. and the Director of Interactive for Centerline Digital in Raleigh.
- 3. UX versus Usabilityversus UI http://www.wired.com/magazine/2012/01/ff_ux/ Copyright Wired Magazine
- 4.
- 5. Cross-Functional Team Legacy Dev Dev UX Product Dev Dev UX New Product Dev Dev UX 2 One Product Dev Dev
- 6. I Know itAll Now! http://www.flickr.com/photos/jainbasil/4889471879/
- 7.
- 8. Really Make itan Agency Sprint Team A Other UX and Sprint Priorities Usability Team B Sprint Team C
- 9. As for me,all I know is that I know nothing. -- Socrates I can't go back to yesterday because I was a different person then. -- Alice
- 10. http://www.flickr.com/photos/possumgirlpics/5284813529/ Agile is About Team
- 11.
- 12.
- 13.
- 14. The Mad Hatter:Have I gone mad? Alice: I’m afraid so. You’re entirely bonkers. But I’ll tell you a secret. All the best people are.
- 15.
- 17. How do youintegrate UX? • No one answer • But I do have an inclination
- 18. THANK YOU FORCOMING brians@snowglobesoftware.com
- 19. Session Notes At theend of the session, I asked the audience what they have seen work when it comes to integrating UX into Agile teams. The group shared a lot, and we looked at a number of different models. In the end, for many companies, I think a hybrid model could work best. In the hybrid model, the teams would always have a UX member, and these teams would pull research, look-ahead work, and long running work as part of an Agile process. However, in order to ensure a shared vision across all teams, the UX members would meet as part of a larger Scrum of Scrums-like meeting/group that would discuss the body of work as a whole, and maintain brand integrity. The following slides contain the raw comments that were shared…
- 20. The Raw Data •Kanban seems to work better. Scrum • UX as a pig caused the team to slow down. seems to force work ahead. UX as a chicken caused them to become a • Limit the amount of research space and stakeholder. Now, the team moves faster look-ahead and the Product Owner decides what UX • Having Architects be coupled to UI work goes into the team. produces better design. • Pig and Chicken is BS because it creates • Story – Tactical and Incremental (Little). an artificial divide within the company. Design – Strategic (Big) • No Hand-offs! • Better Done-ness Criteria! • Look at Salesforce’s Office Hours concept • Virtual Agency (Center of Excellence), but for their UX teams. UX is still a part of their team. • When scaling, a hybrid needs to exist • Goal is to study and experiment. Create a which creates a Distributed but Governed more centric focus. Every Friday, do a model. study. • Empower and trust the developers. Open • Make sure you are solving the RIGHT up early work for everyone. problems in User Stories. Create a UX- • Look at a release planning “Cycle”: Vision focused Cross-Functional team. (Paper Prototypes), Communication and • Remove the divide between documentation Collaboration throughout, Joint Designs. and collaboration (ex, take wireframes • Too many cooks can create a design-by- away). committee feel. To avoid, you need a • Working with UX on a team makes things champion role. more relaxed.