13
SAFe & UX Beispiel aus der Praxis. Oder: Du darfst 3x raten wo UX sein soll… Angie Born @tripelle September 2019

SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

SAFe & UX Beispiel aus der Praxis. Oder: Du darfst 3x raten wo UX sein soll…

Angie Born @tripelle September 2019

Page 2: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Angie Born SAFe&UX 2019

SAFe bei der ANZ• Rund 500 Leute verteilt auf 10-40 Teams und

Support-Rollen (alle SAFe Ebenen)

• Entwickler*innen, Scrum Master, Business Analysts, UI Designer, Architects, Product Owners, Release Planner, etc…

• Entwicklungsprozess nicht überall Agil – Integrationen mit Waterfall Komponenten

Page 3: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,
Page 4: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Elements of UX

The Elements of User ExperienceA basic duality: The Web was originally conceived as a hypertextual information space;but the development of increasingly sophisticated front- and back-end technologies hasfostered its use as a remote software interface. This dual nature has led to much confusion,as user experience practitioners have attempted to adapt their terminology to cases beyondthe scope of its original application. The goal of this document is to define some of theseterms within their appropriate contexts, and to clarify the underlying relationships amongthese various elements.

Jesse James [email protected]

Visual Design: graphic treatment of interfaceelements (the "look" in "look-and-feel")

Information Architecture: structural designof the information space to facilitateintuitive access to content

Interaction Design: development ofapplication flows to facilitate user tasks,defining how the user interacts withsite functionality

Navigation Design: design of interfaceelements to facilitate the user's movementthrough the information architectureInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Functional Specifications: "feature set":detailed descriptions of functionality the sitemust include in order to meet user needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

Content Requirements: definition ofcontent elements required in the sitein order to meet user needs

Interface Design: as in traditional HCI:design of interface elements to facilitateuser interaction with functionalityInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Web as software interface Web as hypertext system

Visual Design: visual treatment of text,graphic page elements and navigationalcomponents

Concrete

Abstract

time

Conception

Completion

FunctionalSpecifications

ContentRequirements

InteractionDesign

InformationArchitecture

Visual Design

Information DesignInterface Design Navigation Design

Site ObjectivesUser Needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development)that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within auser experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.

task-oriented information-oriented

30 March 2000

© 2000 Jesse James Garrett http://www.jjg.net/ia/

Based on “Elements of User Experience” Jesse James Garrett

Visual Design

Information Design

Interaction Design & IA

Needs & Objectives

Functions & Features

Concrete

Abstract

Page 5: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Versuch 1

Requirements

Specification

Information Design

Interaction Design (Flows & IA)

Visual Design

Page 6: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Versuch 2

Requirements

Specification

Information Design

Interaction Design (Flows & IA)

Visual Design

Design Ops

Page 7: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Information Design

Interaction Design (Flows & IA)

Visual Design

Ging nicht, zu verteilt im Unternehmen

IA auf Portfolio Ebene

Page 8: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Versuch 3

Requirements

Specification

Information Design

Interaction Design (Flows & IA)

Visual Design

Design Ops

(UX) Architect

Page 9: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Angie Born SAFe&UX 2019

Die grössten Herausforderungen

• UX Reife innerhalb der Organisation: v.a. im Hinblick auf Verständnis der UX Rollen & Stellenwert der Benutzer*innen

• Einigkeit mit externen Partnern über UX Rollen

• Lean UX = Verwässerung und Deprofessionalisierung der UX Disziplin

• Kultur in den Teams extrem unterschiedlich (Programm und Portfolio OK)

• Research (inkl. Testing) kommt oft zu kurz

• Ressourcenkämpfe

Page 10: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Consumer Digital UX Team

Mapping UX to iDLC

�10

Analyse & Design Build & Test

Research

ImplementPlan

High level design & usability testing

Detailed design & usability testing

Specification

Information Design

Interaction Design & IA

Visual Design

Requirements

Business Case

Product Tracking

Page 11: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Consumer Digital UX Team

User-Centred Design process

�11 Hiser 2013

Define the Problem, Find possible Solutions

Decide on a Solution

Build the (MVP of the) Solution

Measure the Success, Create Feedback Loop

Page 12: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Angie Born SAFe&UX 2019

Was ich gelernt habe• Aufklären, Erklären, Vorleben.

Repeat.

• Erfahrung zahlt sich aus: Experten & Seniors engagieren. Qualitätskontrolle v.a. auch bei externen Partnern & Agenturen.

• Es gibt nicht einen Ort für UX. Es gibt nicht mal nur einen Ort für UX Research.

• “Mehr Leute” war keine Lösung.

Page 13: SAFe & UX - swissICT · Angie Born SAFe&UX 2019 SAFe bei der ANZ ¥ Rund 500 Leute verteilt auf 10-40 Teams und Support-Rollen (alle SAFe Ebenen) ¥ Entwickler*innen, Scrum Master,

Danke.Fragen?

Angie Born @tripelle

linkedin.com/in/angieborn

Buch Tipp: “Delta CX” von Debbie Levitt(Ende September)

Kurs Tipp: https://www.walkthewalk.ch/seminare/ux-und-safe/