Agile vs. Fragile

Agile vs. Fragile

User Experience Design in Product Ownership (プロダクト・オーナーシップにおけるユーザエクスペリエンス・デザイン)

AgileUX のパイオニアである Jeff Patton 氏が弊社にて2日間に渡る「Product Ownership Training(プロダクト・オーナーシップ研修)」を開講してくださいました。アジャイル開発を推進するための目的として開催されましたが、プロダクト・オーナーシップ・チームを対象としたセッションということでユーザエクスペリエンスデザイナーとして参加してまいりました。

Lean Service Design Trilogy

Lsdt

Lean Service Design changes the way you think about business. No longer can companies focus their efforts on process improvements. Instead, they must engage the customer in use of their product/service rather than analyzing tasks for improvement. We no longer build and hope that there is a demand. We must create demand through our product/service and Lean Service Design is the enabler of this process. It changes our mindset of thinking about design at the end of the supply chain to make it look good and add a few appealing features (all within budget). Instead, it moves design and the user themselves to co-create or co-produce the desired experience to the beginning of the supply chain.

via Lean Service Design Trilogy

User-Centered Agile Development

Traditional

Ucd_context
Agileux

User-Centered Agile Development

For interactive systems in the 21st century, we must do more to understand how our users behave and what they need from our interactive solutions. Furthermore, these behaviors and needs must inform the design process without violating agile constraints (for example, no big design up front). To do this requires a few adjustments to a typical development process:

  1. Integration of usability and user experience expertise with the development team
  2. An appropriate amount of user research up front
  3. The distillation of the user research to a suitable form for design (personas)
  4. Parallel streams for interaction design and development

via User Requirements in the 21st Century

User-Centered Agile Development

For interactive systems in the 21st century, we must do more to understand how our users behave and what they need from our interactive solutions. Furthermore, these behaviors and needs must inform the design process without violating agile constraints (for example, no big design up front). To do this requires a few adjustments to a typical development process:

1. Integration of usability and user experience expertise with the development team
2. An appropriate amount of user research up front
3. The distillation of the user research to a suitable form for design (personas)
4. Parallel streams for interaction design and development

User Requirements in the 21st Century [pdf] (via socialuxd)

The Product Canvas

The Product Canvas is a powerful agile tool that facilitates the development of new products by describing the users with their needs and the product’s features.

The Product Canvas brings together the key pieces of information necessary to create a new product: the users and customers with their needs, the product’s functionality and design, and the user interaction. It’s intended to be a collaborative tool that helps you state your ideas and assumptions, test them, and integrate the insights you gain.

via THE PRODUCT CANVAS

Continuous Design & Continuous Delivery

Venn diagram of “Traditional UX” vs “Agile UX” vs “Lean UX”.

Venn diagram of “Traditional UX” vs “Agile UX” vs “Lean UX”.

What we’re doing is building a new kind of software and product development consultancy. We’re building a consultancy based on our belief that the best products come out of well-integrated teams, where development is not in service to design, or vice versa, but where the whole enterprise is oriented toward building the right thing for the market, and doing it quickly and iteratively.

{new context blog: Announcing the launch of New Context}