Agile UX and waterfall enterprises: A love story

You’ve got a crack team, they're agile, work is getting done and everything is right in the world. If only the rest of the organisation understood how and why you work the wonderful way you do...

In enterprise organisations it's not always possible for everyone to work under one methodology as real world factors that require a high level of forward planning are often not best serviced by a highly lean or agile process.

So how do agile teams work alongside non-agile business units?

Transcript

1. Agile UX and enterprises A love story
2. Dave Calleja Experience Design Lead @ Isobar Jetstar Account UX Lead @davecalleja @isobarAU
3. The UX Design Spike and how it helped us improve our design process
4. Where are we using it? 4+ Agile scrum teams (~10 per team) 8 UX & UI Designers 20 websites 7 languages iOS, Android & web Multi-lingual, multi-location teams
5. What is it for? Allowing broad non-agile stakeholder engagement Engaging with subject matter experts outside the project Solving design problems which don’t fit into sprints Facilitating chunky testing and research in an agile process Providing an engagement model between teams
6. Who is this for? Not the time for preaching
7. So, why a new process? We needed an approach that...
8. Co-exist & educate
9. Reduce interruptions
10. What were the challenges? Executing our plans
11. Accessing the right minds
12. Educating newbies
13. So, some principles. Or rules for engaging the enterprise stakeholder The least amount of work required to obtain what’s needed to move forward Build confidence in the processes, engage early and report back Arm your product owners, they are not (usually) design professionals
14. Our process - UX Design Spike
15. Defining a spike
16. A design spike is
17. A design spike is not
18. Guiding the backlog
20. Spiking it
22. Delivering ticket babies into sprint
24. Outcome How did it help?
25. Non-agile benefits?
26. Agile benefits?
27. Looking back What did we learn?
28. Thank you!