Comments for Superdeluxesam http://superdeluxesam.com freelance visual & interaction design for the web Fri, 17 Sep 2010 15:35:39 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on My new design; feedback please! by Graham http://superdeluxesam.com/2010/09/16/my-new-design-feedback-please/comment-page-1/#comment-106 Graham Fri, 17 Sep 2010 15:35:39 +0000 http://superdeluxesam.com/?p=248#comment-106 Loving the new design. Loving the new design.

]]> Comment on Contact by Superdeluxesam » My new design; feedback please! http://superdeluxesam.com/contact/comment-page-1/#comment-100 Superdeluxesam » My new design; feedback please! Thu, 16 Sep 2010 12:47:05 +0000 http://superdeluxesam.com/#comment-100 [...] Contact [...] [...] Contact [...]

]]> Comment on Advocacy and agile ux by David Fox http://superdeluxesam.com/2010/08/05/advocacy-and-agile-ux/comment-page-1/#comment-67 David Fox Sat, 07 Aug 2010 02:49:22 +0000 http://superdeluxesam.com/?p=215#comment-67 Hello all If you are interested I am publishing my Master's thesis on agile user-centered design methodology integration. It should be available by late August at the University of Calgary. It addresses the upfront resource allocation that differs greatly between the agile and UCD methodologies and how these differences are overcome in industry today. Hope this is of some value to you. David Fox Hello all
If you are interested I am publishing my Master’s thesis on agile user-centered design methodology integration. It should be available by late August at the University of Calgary. It addresses the upfront resource allocation that differs greatly between the agile and UCD methodologies and how these differences are overcome in industry today.

Hope this is of some value to you.

David Fox

]]> Comment on Advocacy and agile ux by admin http://superdeluxesam.com/2010/08/05/advocacy-and-agile-ux/comment-page-1/#comment-65 admin Fri, 06 Aug 2010 19:35:03 +0000 http://superdeluxesam.com/?p=215#comment-65 Hi Dimitry; You make a couple of good points there. I don't personally believe ux is tied to waterfall either, but the traditional approach, as espoused by Jesse James Garrett most certainly is. I guess what I was really driving at was that improving processes in general is a central part of agile and working out how user experience fits in should be part of that discussion. Thanks for the links by the way, they look really useful. Hi Dimitry;

You make a couple of good points there. I don’t personally believe ux is tied to waterfall either, but the traditional approach, as espoused by Jesse James Garrett most certainly is.

I guess what I was really driving at was that improving processes in general is a central part of agile and working out how user experience fits in should be part of that discussion.

Thanks for the links by the way, they look really useful.

]]> Comment on Advocacy and agile ux by Dmitry Nekrasovski http://superdeluxesam.com/2010/08/05/advocacy-and-agile-ux/comment-page-1/#comment-64 Dmitry Nekrasovski Fri, 06 Aug 2010 15:56:05 +0000 http://superdeluxesam.com/?p=215#comment-64 Sam, I agree that the team needs to have a commitment to UX in order to be able to incorporate it within the process they follow - regardless of whether it's agile or waterfall. But, I disagree that UX is somehow tied to a waterfall process, or that incorporating it into an agile team's work is as simple as having the team recognize the importance of UX. Some advocacy and thinking about what works and what doesn't is definitely required. Some agile practices work well with UX methods, while others need to be tweaked. Conversely, some UX methods work well within an agile process, while others need to be tweaked. You may want to take a look at a talk I recently presented on this topic: http://www.slideshare.net/dmitryn/surviving-and-thriving-as-a-ux-professional-in-an-agile-development-organization and this list of resources on how to make the UX-Agile integration work: http://delicious.com/prettyusable/agile-ux Sam, I agree that the team needs to have a commitment to UX in order to be able to incorporate it within the process they follow – regardless of whether it’s agile or waterfall.

But, I disagree that UX is somehow tied to a waterfall process, or that incorporating it into an agile team’s work is as simple as having the team recognize the importance of UX. Some advocacy and thinking about what works and what doesn’t is definitely required.

Some agile practices work well with UX methods, while others need to be tweaked. Conversely, some UX methods work well within an agile process, while others need to be tweaked.

You may want to take a look at a talk I recently presented on this topic:

http://www.slideshare.net/dmitryn/surviving-and-thriving-as-a-ux-professional-in-an-agile-development-organization

and this list of resources on how to make the UX-Agile integration work:

http://delicious.com/prettyusable/agile-ux

]]> Comment on Advocacy and agile ux by Chris http://superdeluxesam.com/2010/08/05/advocacy-and-agile-ux/comment-page-1/#comment-63 Chris Fri, 06 Aug 2010 15:37:50 +0000 http://superdeluxesam.com/?p=215#comment-63 Hi In all honesty I would say that everyone from stakeholders to developers, and also marketing need to have UCD awareness. the Agile approach isn't a do or don't you can take different approaches that suit your needs. I prefer a gap between each sprint that allows for developers and designers to markup and comment properly, also allow a proper guage of realistic sprint goals going forward. Use this gap to take what you have outside of the team and show some candidate users if you can, the feedback is proper user feedback, not just team members with a generic idea of who users are. Hi

In all honesty I would say that everyone from stakeholders to developers, and also marketing need to have UCD awareness.

the Agile approach isn’t a do or don’t you can take different approaches that suit your needs.

I prefer a gap between each sprint that allows for developers and designers to markup and comment properly, also allow a proper guage of realistic sprint goals going forward. Use this gap to take what you have outside of the team and show some candidate users if you can, the feedback is proper user feedback, not just team members with a generic idea of who users are.

]]>