Comments on: UIEtips: 12 Best Practices for UX in an Agile Environment – Part 2 http://www.uie.com/brainsparks/2011/08/29/uietips-ux-agile-part2/ UIE\'s latest insights on the world of design Wed, 22 May 2013 18:03:42 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: Ruth http://www.uie.com/brainsparks/2011/08/29/uietips-ux-agile-part2/comment-page-1/#comment-164077 Ruth Tue, 30 Aug 2011 17:19:29 +0000 http://www.uie.com/brainsparks/?p=5259#comment-164077 I asked my manager for permission to attend this webinar. I wanted to back it up by pointing to Jeff's website - however, the content is three years (or more) old. In times of tight budgets, when everything must be justfified, it may be a hard sell to get funds to listen to an instructor who does not keep his website up to date. Even the blogs appear to be that old. And, BTW, UIE's contact page doesn't contain an e-mail for sending feedback of this type. I would have much rather broached the subject in a less public forum. I asked my manager for permission to attend this webinar. I wanted to back it up by pointing to Jeff’s website – however, the content is three years (or more) old. In times of tight budgets, when everything must be justfified, it may be a hard sell to get funds to listen to an instructor who does not keep his website up to date. Even the blogs appear to be that old.

And, BTW, UIE’s contact page doesn’t contain an e-mail for sending feedback of this type. I would have much rather broached the subject in a less public forum.

]]> By: Christian Manzella http://www.uie.com/brainsparks/2011/08/29/uietips-ux-agile-part2/comment-page-1/#comment-164058 Christian Manzella Tue, 30 Aug 2011 14:19:22 +0000 http://www.uie.com/brainsparks/?p=5259#comment-164058 This is a fantastic set of guidelines; one of the best I've seen yet speaking to UX in Agile. Two other items I think are worth mentioning: 1. Use the concepts applied as LeanUX by Jeff Gothelf. I've seen the most successful design come out of identifying what's needed to communicate the requirements and using only that. I don't believe in prototypes (only) as requirements, but I do believe in keeping artifacts & documentation to a level that's minimal and manageable, provided they clearly communicate what needs to be done. 2. Exemplary communication is a huge factor in the success of Agile, as a whole. While not necessarily a UX thing specifically, UX will often be the one to champion communication getting done effectively. The UX designer should welcome this responsibility (akin to the number 1 bullet) and remain engaged with the team. When a developer defaults to UX with a question, UX should turn around and pull the visual designer, business analyst, and others into the conversation. This is a fantastic set of guidelines; one of the best I’ve seen yet speaking to UX in Agile.

Two other items I think are worth mentioning:

1. Use the concepts applied as LeanUX by Jeff Gothelf. I’ve seen the most successful design come out of identifying what’s needed to communicate the requirements and using only that. I don’t believe in prototypes (only) as requirements, but I do believe in keeping artifacts & documentation to a level that’s minimal and manageable, provided they clearly communicate what needs to be done.

2. Exemplary communication is a huge factor in the success of Agile, as a whole. While not necessarily a UX thing specifically, UX will often be the one to champion communication getting done effectively. The UX designer should welcome this responsibility (akin to the number 1 bullet) and remain engaged with the team. When a developer defaults to UX with a question, UX should turn around and pull the visual designer, business analyst, and others into the conversation.

]]>