3 Methods to Master Agile UX Testing | UserZoom Webinar

Editor's Notes

• #7: - Engages the customer and listen to what they have to say - Agile Manifesto created by a group of software developers in 2001 who wanted to find a better way to create software
• #8: Waterfall – linear, sequential process of design, intense planning and documentation, more difficult to enact change, feedback occurs later in the development process, - Testing at the end of development, too late to make significant changes to design Agile – build software incrementally rather than all at once at the end Projects are broken into delivering functionality called user stories and delivering them in short cycles called iterations (or sprints) Evaluate quality at per sprint basis, be more responsive, be more flexibility
• #10: Allows for change More flexible Adapt to evolving business requirements Allows for projects to adjust accordingly Better risk management Feedback from customers to better meet expectations Improved quality Frequent testing makes it easier to identify problems earlier Critical bugs caught earlier Increased collaboration Collaboration between Developers, PM, Business Analysts, QA for better efficiency Better visibility and transparency Greater sense of ownership
• #11: Agile mainly focuses on the development and implementation UI and usability overlooked Address bigger picture with design spike http://www.smashingmagazine.com/2012/11/design-spikes-fit-big-picture-ux-agile-development/ Design spike – time-boxed period used for exploration and research, a time when design team can address UX issues within the constraints of scrum
• #12: Can do both small and larger sample sizes with remote testing No geographic constraints (not limited to the location of lab) If using remote testing, can obtain insights in as little as a few hours Sample UX agile metrics Task completion, time on task, # of clicks, task difficulty Automated reporting – obtain aggregated data with task success rates, time on task etc., already calculated Establishing a benchmark when iterating on designs - Currently seeing customers succeed using remote techniques in their agile environment, we’ll provide some use cases and examples later
• #17: Describe what it is and how it works Can be used for first click testing on wireframes, prototypes Can users quickly and easily find where to go to find the information they need? Research shows that if users’ first click is correct, 87% will eventually complete the task successfully Evaluate first impressions
• #18: First click testing – do users know where to click Confidence – Are they confident they clicked on the right area? If they’re highly confident but clicked on the wrong area, then you have a problem Impression – How do users feel about the design? Is it making the right impression? Is it consistent with your brand values?
• #19: Can show participants both versions or only one (between or within subjects design)
• #20: Case study: financial services company wanted to understand which product page design best display clickable links, Tested 3 different versions using SSCT and obtain answers within a day Case Study: blue chip software company who typically designs using PowerPoint mockups. Tested out the designs using a series of SSCT to evaluate and provide feedback on the design flow.
• #26: Also known as reversed card sorting, find items rather than grouping them and placing them into categories or a navigation structure Information on a site typically have a hierarchical organization of topics and subtopics Measure how effective the site structure is
• #28: Staples Example
• #34: It may not be possible to create or design subsequent page, but can build a ‘landing page’ or ‘gray page’. Have the message say that it’s outside of the scope of the task and click the browser back button to continue with the task
• #36: Case Study: Shop Direct (multi-brand retailer in the UK) – wanted to optimize the checkout process Goal improve conversion and ease of use Tested prototypes iteratively during agile development Ran a series of remote unmoderated task-based studies testing 2 competing HTML prototypes Collected task success, efficiency, satisfaction and behavioral metrics Uncovered and resolved 54 usability issues prior to release, resulting in greater conversion
• #42: Research 1-2 sprints ahead, validate designs and identify issues early Set up a parallel track for UX, gather information for upcoming iterations, RITE – for formative testinginsightful, low risk, similar to traditional usability studies, don’t wait until the end of the study to examine findings and make improvements, once issues are discovered by a few users the team iterates on the design, Fix as you go
• #44: Average of 880,000 website visits a day to their store brands Specifically annoyed with having to select
• #47: Research 1-2 sprints ahead, validate designs and identify issues early Set up a parallel track for UX, gather information for upcoming iterations,
• #48: RITE – for formative testinginsightful, low risk, similar to traditional usability studies, don’t wait until the end of the study to examine findings and make improvements, once issues are discovered by a few users the team iterates on the design, Fix as you go
• #49: Customer council – Autodesk webinar, article Developed an online customer council, post announcements, videos, surveys Council had 50 -75 users to start Recruit customers all over the world to participate Had a council for each specific initiative Recruited to each council based on specific need or interest Committed to testing a new build Keep them highly engaged