User Centered Agile

  • 3,220 views
Uploaded on

from #ShibuyaUX at 26/04/2011.

from #ShibuyaUX at 26/04/2011.

More in: Design , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,220
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
53
Comments
0
Likes
9

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. User Centered Agile (Ability)#ShibuyaUX 26/04/2011Kazumichi Sakata (@sprmari0)Information Architect at Rakuten Inc.
  • 2. 俊敏(Agile)
  • 3. ソフトウェア開発におけるアジャイル開発プロセス。Scrum、XPなどの方法論を提唱している人たちが2001年に集まって名前を付けました(アジャイルマニフェスト)。現在、世界的に普及したり検討されている方法論に、Scrum, XP, Lean/Kanban などがあります。 via http://sites.google.com/site/agileucdja/
  • 4. •良いものを(Quality)•素早く(Speed)•繰り返し改善して(Modification)
  • 5. POINT 1ユーザの要求を随時取り入れる(Incorporate users request at any time)
  • 6. POINT 2実際に動作するプログラムをより短いサイクルでリリースする(Shorter cycle to release a program that really works)
  • 7. 水流(Waterfall)
  • 8. 楽天のUCDStrategy Information Architecture Design Check Site User & Business Objective Scenario Content Requirement / Functional Specifications Information SEO Design Wireframe Interaction (Interface) Design Usability Visual Design Analysis Test Usability Test
  • 9. 楽天のUCD 事業/BU (Stakeholder) Site Content Requirement / Business Objective Functional Specifications 開発/DU (PRO/ENG) 編成/CWD Site Content Requirement / Business (DIR/DES) Objective Functional Specifications User & Information Wireframe Interaction … Scenario Design (Interface) Design 事業/BU 開発/DU 編成/CWD PRJ (Stakeholder) (PRO/ENG) (DIR/DES)
  • 10. 要件(要求)が既に決まっていて検証の余地がない…(There was no validation because requirement has been alreadydecided…)妥当性のある仮設を導き出せず、PDCAを廻せない…(Cannot make PDCA in action without any hypothesis…)
  • 11. ペルソナが生きない。 (Persona is dead)
  • 12. ユーザ中心設計の概念をプロジェクトの上流に持ち込みたい!(Want to introduce user-centered design concepts at upperstream of the project)
  • 13. ユーザ&コンセプトドリブンで妥当かつ一貫性のある要件を定義したい!(Want to define suitable and consistent requirements in user /concept driven process)
  • 14. 出会(Contact)
  • 15. アジャイル開発に注目していた開発部もユーザの要求定義に興味を持ち始めていた。開発と編成の距離を縮められる良いチャンスかもしれない。DU had interest toward user’s requirement definition due to introduction of Agiledevelopment process. This was a chance to bring DU and us(CWD) together.
  • 16. 提案(Approach)
  • 17. API開発要件も含めることが前提。(Assume definition of API requirements are included as well)コストはすべて編成が持つ。(CWD will hold all the costs of project)
  • 18. 実行(Action)
  • 19. UCA 事業/BU (Stakeholder) 開発/DU (PRO/ENG) Site Content Requirement / Business Objective Functional Specifications 編成/CWD (DIR/DES) User & Information Wireframe Interaction … Scenario Design (Interface) Design 事業/BU 編成/CWD 開発/DU (Stakeholder) (DIR/DES) (PRO/ENG) PRJ
  • 20. TaskOutput
  • 21. 大夢(BPUF)
  • 22. BPUF(Big Picture Up Front)でゴールイメージの設定 。(Setting up goal image by BPUF)コンセプトや戦略の立案。(Planning concepts and strategies)
  • 23. 物語(Story)
  • 24. ストーリーボードを使ってシナリオを描く。(Draw user scenarios by storyboard)
  • 25. サービスの利用シーン(ストーリー)をシナリオにブレイクダウンして機能要件に落とす。(Breaking down service usage scenarios into stories to definefunctional requirements)
  • 26. 反復(Iteration)
  • 27. シナリオをイテレーションに別けて開発。(Breaking down scenario into iterations)イテレーション単位でユーザテスト。(User tests by iterations)
  • 28. Scenario 1User-Centered Design Usability UI Usability Wireframe (ワイヤーフレーム) Test Design Test(ユーザ中心設計) (ユーザビリテスト ) (UIデザイン) (ユーザビリテスト)Agile Development Impl’tn (API結合)(アジャイル開発)Scenario 2User-Centered Design Usability UI Wireframe (ワイヤーフレーム) Test Design(ユーザ中心設計) (ユーザビリテスト ) (UIデザイン)Agile Development Impl’tn (API結合)(アジャイル開発)
  • 29. 振返(Overview)
  • 30. Positive•全員参加 / 共通言語化 (Full participation / Common Language)•期間短縮 (Schedule has shorten)•User Centered “Design” User Centered Agile? Agile UCD?
  • 31. Negative•コスト変動 (Opacity of cost)•能力&リソース依存 (Depends on ability and resources)
  • 32. Integration of SatisfactionProject Methodology User Experience with the MethodWaterfall 2.5 2.9Agile 3.1 3.7Clearly, Agile is considerably better than the old Waterfall method.Good riddance to that one. However, the professionals in our new studystill felt that Iterative Design was marginally better than Agile; theresstill work to be done to make Agile projects more user-driven.In better news, the latest data provides some evidence that weremoving beyond "them and us" — overall, developers were more bullishthan UX people on a couple of key UX opinion metrics. via http://www.useit.com/alertbox/agile-user-experience.html