楽天の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
楽天の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)
要件（要求）が既に決まっていて検証の余地がない…（There was no validation because requirement has been alreadydecided…）妥当性のある仮設を導き出せず、PDCAを廻せない…（Cannot make PDCA in action without any hypothesis…）
アジャイル開発に注目していた開発部もユーザの要求定義に興味を持ち始めていた。開発と編成の距離を縮められる良いチャンスかもしれない。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.
Positive•全員参加 / 共通言語化 (Full participation / Common Language)•期間短縮 (Schedule has shorten)•User Centered “Design” User Centered Agile? Agile UCD?
Negative•コスト変動 (Opacity of cost)•能力＆リソース依存 (Depends on ability and resources)
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