Webcredible Guest Blog: Integrating UX into Agile
7 March 2018 |
About a 6 minute read
Integrating UX into Agile
As AND Digital’s experience design partners, we at Webcredible know all about how to integrate great UX and UI design into an Agile process. We work with AND across numerous clients, making sure we’re launching products that the clients love.
There are 3 key stages for UX to integrate into the product development process:
Before you carry out a full technical specification, make sure what you’re designing and which features you’re prioritising are going to deliver the best ROI, and are in line with customer needs. You should:
- Engage with stakeholders, ideally in workshops to reach a consensus that everyone buys into – what’s the vision for the product, what customer problem does it solve and what does success look like? Be sure to focus on outcomes and not product features – don’t get designing or scoping just yet!
- Run research with target end users of the product to understand needs, goals and pain points. Don’t ask customers what they want (no one knows!) – instead, find out how your proposed product and its features might fit into their existing behaviour and what problems it might be solving.
Combine the findings from your stakeholder and customer engagement, creating a product strategy and prioritising features based on business goals, user needs and ease of implementation (the last being based on development time/complexity, culture, compliance etc.).
Stakeholder workshops should always be fun, interactive and outcome-focused
Lab-based research is great as your colleagues can watch it live – essential for getting their buy-in
Our research with our client, Dulux for example, has shown that arguments with your partner and fear of being judged are the 2 main reasons people don’t decorate their home when contemplating doing so. Off the back of our research, we envisaged and launched the Dulux Visualiser, an augmented-reality app that allows you to ‘paint’ your walls and put an end to the arguments and feelings of fear (thereby solving a genuine customer problem).
2. Sprint 0
Before cracking on with your Agile sprints… Stop! Everyone needs to have a shared vision of the final output so take the time to define and share this across the team. You won’t know the detail of what you’re delivering yet (this will come out in the sprints) but it’s really important to begin with the end in mind and get everyone aligned. You should:
- Create a very lo-fidelity design prototype for the end-to-end system
- Map out ideal user flows from an end user (not technical) perspective
- Create an initial pattern library to ensure design consistency across sprints (you’ll need to continually update this as you go along)
- Run usability testing with real customers (don’t just grab a few colleagues) to check the proposed product vision resonates with potential users and is in line with their mental models
…And all this before you get going with your sprints. This doesn’t need to be lost time either – depending on what you’re doing, sprint 0 should take 1-4 weeks and you can often be getting the core technical infrastructure in place during this time.
You should have UXers and UI designers working within sprint teams, continually feeding in designs and user flows for essential user journeys.
UXers and UI designers should take lead roles during sprint planning:
- Being the customer champion and pushing for the best possible experience for the sprint outputs
- Reminding everyone as to the bigger picture (i.e. Sprint 0 outputs) and how the current sprint fits into this
- Briefing the sprint team as to what the ideal customer experience is for that sprint
- Challenging developers’ thinking around how each feature should be built (and compromising where need be)
It’s important to have a healthy tension between UXers and developers, with the former pushing for the best experience and the latter pushing for the easiest possible build. Technical limitations rarely allow us to get the 100% best possible customer experience, but with good collaboration we can get close enough.
You should also run up to 2 rounds of usability testing during each sprint, ideally one after a few days (to verify you’re headed in the correct direction) and one towards the end of the sprint (to validate your work and make last minute changes). Larger changes from usability testing should be added to the backlog for future sprints.
Getting the whole sprint team to sketch out ideas (based on business goals and customer needs) is great for getting ideas to feed into usability testing, as well as getting everyone’s buy-in
On-site war-rooms are great for generating excitement and allowing stakeholders to feed in their requirements during sprints
When working with Confused.com, we wanted to include personalised recommendations and the option to remove results from the results page (our research showed these features supported users’ mental models). We sketched out lots of ideas for how this could all work at the start of the sprint, and then our usability testing helped us work out the best possible design and user experience (with some great results for Confused.com post-live).
Integrating UX into Agile isn’t particularly difficult – you just need to make sure you have UX and UI resource allocated to sprint teams.
You’ll also need a bit of extra headspace throughout, to be thinking about your customers’ needs and goals and not just cracking on with building the product and its features. But this is surely a good thing and a great way to end the age-old problem of the HiPPO effect.
This post was contributed by Trenton Moss, CEO of our amazing experience design partners, Webcredible.
Tech Lead (Reading)
Bring your expert tech knowledge to the table to influence the direction of projects, whilst coaching and your team through engineering best practices.I'm Interested
DevOps Lead (Reading)
Bring your delivery expertise to the table, leading the pack as ambassador on operational requirements, influencing and continuous development.I'm Interested
Programme Lead (Edinburgh)
Bring your expert project knowledge to the table to own delivery of all our initiatives being delivered out of our Delivery Engine.I'm Interested