I participated in my first webinar recently, sharing some learnings from the Cars.com agile transformation. The webinar was sponsored by consulting firm ThrivingOrg and focused on what we learned during a 10-week series of pilot projects undertaken by several product teams. Here are some notes I prepared:
- Transition from waterfall to agile was difficult at first for user experience team members because most of the techniques used by classically trained user experience people came from the waterfall world. Things like wireframes, a fully designed user experience and flow, and pixel perfect Photoshop comps don’t work well within the context of two-week working sprints.
- Our profession needs to get better at using Lean UX approaches and shifting our work product to sketches, prototypes that can be used for documentation and user testing, and more lightweight guerrilla usability testing.
- Interactions between agile product team members are very different than in waterfall project teams. Developers and UX people are working much more closely and more often now (and that’s a good thing).
- Dedicated team co-location is essential. Having the product manager, UX and visual designers, and developers and testers near each other fosters frequent informal collaboration and reduces the number of structured meetings you need.
- Daily standup meetings and co-location should drive greater appreciation of the other roles on the team and the constraints they are working under.
- Failing is good. It shows you your limits and helps teach that an agile product team rises or falls together.
- When first transitioning to agile, start with easier to implement features or even a backlog of defects. This allows the team to learn the process first without also having to worry about designing and developing complex functionality.
If you are new to agile software development and Lean UX, these resources can get you started: