ux runway - agile ux - natalie warnert

Download UX Runway - Agile UX - Natalie Warnert

Post on 22-Jan-2017




0 download

Embed Size (px)


Agile UX Runway

Agile UX Runway

Natalie Warnert - Agile Coachwww.nataliewarnert.com@nataliewarnert

What is UX?

How a person interacts with a systemFlowPerceptionAccessibilityEase of useUnderstanding

Roles on UX Team

User ResearchersInformation ArchitectsVisual DesignersCSS DevelopersAccessibility

Centralized Vs. Decentralized UX TeamCentralizedOne UX team for an organization or departmentHigh role specializationResource distribution between projects shared services modelConsultingCan act as own Agile team

DecentralizedOne UX consultant on every Agile team (or project)Jack of all trades less specializationMore availability (?)Is involved in all team activities-----------------------------------------------------------Hybrid models

Why is it hard for UX and Agile to play nicely?UX needs to be integrated at all levels of planning and developmentIts a balance between delayed feedback and big design up front (BDUF)Teams must adhere to fixed timelines and varying scope, while managing desire to change and desire to design the best thingUX has to work closely with both dev and product and make compromises between the two

UXs Place in Product Development Portfolio LevelPerform user research activitiesDevelopment of user personas and use casesDevelopment of business case for productsMap high-level system interactions (BDUF)Work ahead on initial feature deliverables and design ideas for first iterations (as infrastructure is getting set up)

UXs place in Product Development Continued Involvement at Program/Team levelPrioritize and plans work: UX as Scrum/Agile teamWork with Product Owner to make wireframes, designs, and user flows to help:Drive conversations and directionWrite requirements, stories and tasks, acceptance criteriaAdhere to DoD and DoR criteriaConfer with developers to find solution optionsStyle pages appropriately & accessibly (CSS)

This leads to higher quality in the application and more customizable design and less re-work

How can all work be completed in one iteration?

It shouldnt be

UX Runway

UX Runway - Pulling work and quality forward in the process

UX Runway Pulling work and quality forward in the process

UX RunwayIterating ahead but on same cadenceJust in time (JIT) and set-based designJust enough detail provided for development team to start workMultiple options to choose, validate and refine as we gain more understanding doesnt limit end goal80-90% completion goal for UX deliverables at hand offContinuous collaboration and feedback from business and development to get best solution in allotted timePlanned room for UX changes and integration~10-25% capacity

Point-based vs. set-based designPoint-based design:Committing to detailed specifics at an early point in the development/design processMore empirical data will become available as the development proceedsDiscovery that design wont work is too late in the process opportunity cost is higher and it costs more to fixSet-based designMaintain multiple, higher-level, requirement and design options for longer (delay decision making to one option)Use empirical data to focus on final design optionsThis helps to assume variability and preserve optionsJust enough detail to move forward, not too much to lock into a hasty decision that will limit and bind us laterhttp://scaledagileframework.com/set-based-design/

Its a balanceMaintaining multiple options while not putting too much detail into each (save the detail for JIT)Frequent and early validation through prototyping, modeling, simulationSpecify interfaces and requirements (e.g. performance) not exactly how an element achieves its resultsFrequent integration and review pointsAdaptive planninghttp://scaledagileframework.com/set-based-design/

User Research (Features/Epics)Problem focused designGet out of the buildingRapid prototypingMinimum Viable ProductRapid feedback cycles

Information Architecture and Visual Design (epics/stories)Problem focused designIntegration of user research up frontSet based design to just in time designDesign standardsConsistent interactions and integrations10 25% overlap capacity rework if necessary, answer questions, address issuesConstant communication and collaboration with Agile team

Front-end UI/CSS/Accessibility (stories/tasks)Same cadence as development/it is developmentCentralized ownership of the stylesheetsBranding standardsCoding accessiblyOverseers of full circle qualityRaising up impediments and dependencies when opportunity cost is still relatively lowCoding to accommodate changing requirements, consistency, and scalability

Backlog grooming dependencies are identifiedUX backlog is developed, sized, and plannedWorking sessions with Product Owners and teamsFrequent reviews and feedback for collaborationDemos with development teamsDetermine if designs are not feasibleFinished UX work items help to drive work, collaboration, identify gaps, and INCREASE QUALITY without limiting options

How does it actually work?

Days 1-5: The designsDay 5: The rough draftsDays 5-7: The final touches and directionary decisions (set-based design decisions)Day 7: Hand-off to developmentDay 7-10: Last chance for adjustments during sprintDays 10+ (next Iteration): Start over and 10-25% JIT reactionary design capacity

UX Runway: Iteration Schedule (10 day) for product enhancement

Higher quality finished productFewer fire drillsLess development and UX re-work - more iterationFaster delivery time with higher visibility to allMore design flexibility/options without forced and disruptive adjustmentProduct consistency

Benefits of UX Runway

Books/ResourcesLean UXThe design of everyday thingsDon't make me thinkScaled Agile - Set Based Design

ResourcesNatalie's WorkUX Runway BlogIncorporating Agile UX Article -Methods and ToolsUX Runway in Practice (Sprinting)Def of Ready with Dependent Teams (e.g. UX)UX and BA - Lviv, UkraineVideo of Lviv, UkraineUX Runway at Agile2014UX Runway PodcastUX Runway Webinar XBOSoft