Download - User Centered Agile

Transcript
Page 1: User Centered Agile

User Centered Agile (Ability)

#ShibuyaUX 26/04/2011 Kazumichi Sakata (@sprmari0) Information Architect at Rakuten Inc.

Page 2: User Centered Agile

俊敏 (Agile)

Page 3: User Centered Agile

ソフトウェア開発におけるアジャイル開発プロセス。Scrum、XPなどの方法論を提唱している人たちが2001年に集まって名前を付けました(アジャイルマニフェスト)。現在、世界的に普及したり検討されている方法論に、Scrum, XP, Lean/Kanban などがあります。

via http://sites.google.com/site/agileucdja/

Page 4: User Centered Agile

•良いものを(Quality)

•素早く(Speed)

•繰り返し改善して(Modification)

Page 5: User Centered Agile

POINT 1

ユーザの要求を随時取り入れる (Incorporate user's request at any time)

Page 6: User Centered Agile

POINT 2

実際に動作するプログラムをより短いサイクルでリリースする (Shorter cycle to release a program that really works)

Page 7: User Centered Agile

水流 (Waterfall)

Page 8: User Centered Agile
Page 9: User Centered Agile

Business Site

Objective

Content Requirement /

Functional Specifications

User &

Scenario

Usability

Test

Interaction

Design

Visual Design

Usability

Test

Analysis

Strategy Information Architecture Design Check

SEO Information

Design

Wireframe

(Interface)

楽天のUCD

Page 10: User Centered Agile

事業/BU

(Stakeholder)

開発/DU

(PRO/ENG)

Business Site

Objective

Content Requirement /

Functional Specifications

編成/CWD

(DIR/DES)

User &

Scenario

Interaction

Design

Information

Design

Wireframe

(Interface)

Business Site

Objective

Content Requirement /

Functional Specifications

楽天のUCD

開発/DU

(PRO/ENG)

編成/CWD

(DIR/DES) PRJ

事業/BU

(Stakeholder)

Page 11: User Centered Agile

要件(要求)が既に決まっていて検証の余地がない… (There was no validation because requirement has been already

decided…)

妥当性のある仮設を導き出せず、PDCAを廻せない… (Cannot make PDCA in action without any hypothesis…)

Page 12: User Centered Agile

ペルソナが生きない。 (Persona is dead)

Page 13: User Centered Agile

ユーザ中心設計の概念をプロジェクトの上流に持ち込みたい! (Want to introduce user-centered design concepts at upper

stream of the project)

Page 14: User Centered Agile

ユーザ&コンセプトドリブンで妥当かつ一貫性のある要件を定義したい! (Want to define suitable and consistent requirements in user /

concept driven process)

Page 15: User Centered Agile

出会 (Contact)

Page 16: User Centered Agile

アジャイル開発に注目していた開発部もユーザの要求定義に興味を持ち始めていた。

開発と編成の距離を縮められる良いチャンスかもしれない。 DU had interest toward user’s requirement definition due to introduction of Agile

development process. This was a chance to bring DU and us(CWD) together.

Page 17: User Centered Agile

提案 (Approach)

Page 18: User Centered Agile

API開発要件も含めることが前提。 (Assume definition of API requirements are included as well)

コストはすべて編成が持つ。

(CWD will hold all the costs of project)

Page 19: User Centered Agile

実行 (Action)

Page 20: User Centered Agile

事業/BU

(Stakeholder)

開発/DU

(PRO/ENG) Business Site

Objective

Content Requirement /

Functional Specifications

編成/CWD

(DIR/DES)

User &

Scenario

Interaction

Design

Information

Design

Wireframe

(Interface) …

UCA

編成/CWD

(DIR/DES)

開発/DU

(PRO/ENG)

事業/BU

(Stakeholder)

PRJ

Page 21: User Centered Agile

Task

Output

Page 22: User Centered Agile

大夢 (BPUF)

Page 23: User Centered Agile

BPUF(Big Picture Up Front)でゴールイ

メージの設定 。 (Setting up goal image by BPUF)

コンセプトや戦略の立案。

(Planning concepts and strategies)

Page 24: User Centered Agile

物語 (Story)

Page 25: User Centered Agile

ストーリーボードを使ってシナリオを描く。

(Draw user scenarios by storyboard)

Page 26: User Centered Agile

サービスの利用シーン(ストーリー)をシナリオにブレイクダウンして機能要件に落と

す。 (Breaking down service usage scenarios into stories to define

functional requirements)

Page 27: User Centered Agile

反復 (Iteration)

Page 28: User Centered Agile

シナリオをイテレーションに別けて開発。

(Breaking down scenario into iterations)

イテレーション単位でユーザテスト。

(User tests by iterations)

Page 29: User Centered Agile

User-Centered Design

(ユーザ中心設計)

Agile Development

(アジャイル開発)

Wireframe (ワイヤーフレーム)

UI Design (UIデザイン)

Impl’tn (API結合)

Usability Test

(ユーザビリテスト)

Usability Test

(ユーザビリテスト)

User-Centered Design

(ユーザ中心設計)

Agile Development

(アジャイル開発)

Wireframe (ワイヤーフレーム)

Usability Test

(ユーザビリテスト)

UI Design (UIデザイン)

Impl’tn (API結合)

Scenario 1

Scenario 2

Page 30: User Centered Agile

振返 (Overview)

Page 31: User Centered Agile

•全員参加 / 共通言語化 (Full participation / Common Language)

•期間短縮 (Schedule has shorten)

•User Centered “Design”

User Centered Agile? Agile UCD?

Positive

Page 32: User Centered Agile

•コスト変動 (Opacity of cost)

•能力&リソース依存 (Depends on ability and resources)

Negative

Page 33: User Centered Agile

Project Methodology Integration of

User Experience

Satisfaction

with the Method

Waterfall 2.5 2.9

Agile 3.1 3.7

via http://www.useit.com/alertbox/agile-user-experience.html

Clearly, Agile is considerably better than the old Waterfall method.

Good riddance to that one. However, the professionals in our new study

still felt that Iterative Design was marginally better than Agile; there's

still work to be done to make Agile projects more user-driven.

In better news, the latest data provides some evidence that we're

moving beyond "them and us" — overall, developers were more bullish

than UX people on a couple of key UX opinion metrics.

Page 34: User Centered Agile

Top Related