Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Agile & UX: How to make it work

Summary of the discussion/workshop about Agile & UX hosted by Anders Ramsay & Claudia Oster at the UXcamp Europe 2011 in Berlin.

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

Agile & UX: How to make it work

  1. 1. Discussion<br />Anders Ramsay & Claudia Oster<br />UXcamp Europe 2011<br />Agile & UX: How To make it work<br />
  2. 2. Anders Ramsay<br />www.andersramsay.com<br />@andersramsay<br />Claudia Oster<br />usabilitytalks.blogspot.com<br />@usabilitytalks<br />Anders & Claudia<br />
  3. 3. Our experiences<br />
  4. 4. Card STorming & Clustering„What are the Challenges you are facing?“<br />
  5. 5. No experience with agile<br />Design befor development starts<br />Half-baked UX<br />Scrum vs. UX<br />Challenges - 1<br />
  6. 6. Roles<br />Involving Devs in UX<br />Waterfall vs. Agile<br />Transitions into Agile<br />Challenges - 2<br />
  7. 7. Dev-Centric<br />Not enough time for user testing<br />Agile Philosophy<br />Challenges - 3<br />
  8. 8. Discussion<br />
  9. 9. Sprint 0: 3 weeks - Developers are doing research on the technology and the Designers are doing the upfront analysis and design.<br />UX design is involved in creating the product vision: Actively engage the Developers in the design process (Collaborative Sketching, ... ) Devs have solutions that the UX designer wouldn't think of. This also can relate to a close relationship<br />Spreading competency of UXteam to Devs and vice versa should be part of the process<br />Topic 1Design before Development starts<br />
  10. 10. Problem of proper planning: Product Manager need to take ownership and needs to share the goal of what should be the result at the end of the sprint/project. <br />Each team member should have a broader view of what problems they are solving. The product manager should communicate it. Instruments:<br />Send all the material to everybody in the project.<br />Requirement gathering session with the whole team to get the input<br />Write down user stories and make the plan<br />Present again to the team and get feedback<br />Topic 1Design before Development starts<br />
  11. 11. Each team member should explain in the standup exactly what they are doing and what problem they are solving and not using the daily standup as a high-level meeting. > Better understanding, communication in the team and commitment.<br />The team need to have the trust in what they are doing and what they should deliver.<br />Inside the team you need to get rid of the feeling of "guilt" and "failure„. The team need to be confident about the problem and the possibilities of improving.<br />The Scrum Master should take care of the tranisition and he should have knowledge of how to do that.<br />Topic 2Transitioning into Agile(UX coming late in the project/process)<br />