UX Stream

Best UX Advice from the Web
UX Stream > Topics > Technology > Design Processes > Design Studio and Agile UX : Process and Pitfalls | UX Magazine

Design Studio and Agile UX : Process and Pitfalls | UX Magazine

 

We are often asked how and when Design Studio should be used in a startup or enterprise whose product team embraces agile. We hope this article answers some questions about how to effectively use Design Studio (as well as variations on it), and to avoid potential pitfalls so those practicing some flavor of agile UX will be better armed to solve difficult problems in their work.

The description of Design Studio in The Design of Design Studio was meant to serve as the canonical example, and is best suited for the beginning of a significant series of projects focused around one theme, or a set of themes. The output of such a design studio session may span many iterations. There are, however, many variations of Design Studio that can be employed to good effect for the smaller problem spaces within agile processes. For example, a Scrum team may need to explore a more targeted problem space that they identify during iteration planning prior to a sprint.

 

 

This should not imply, however, that we use Design Studio during what is sometimes called “Iteration 0,” although there is no reason why it couldn’t be used then. We don’t happen to follow the “staggered sprints” model popularized by Desiree Sy and Lynn Miller at Autodesk. Instead, we solve problems as whole Scrum teams and bring the ideation, design, and development phases as close as possible to the same kickoff point so the concepts can inform story-gathering and estimation sessions.

Continue reading this article at: Design Studio and Agile UX : Process and Pitfalls | UX Magazine.