Thanks for the plug Itamar.
Jeff and I have used the design studio 8 times over the past year to put
design ahead of development and quickly explore design alternatives. We have
found it to be a great fit for Agile.
If anyone would like more details or has questions/comments - please feel
free to
I think that was a related post a while back in the list: there was
this really interesting talk during the IxDA Interactions '08
conference call "User Interface Design in an Agile Environment:
Enter the Design Studio".
The video of that talk has recently been made available at:
http://interaction
Hi Manish
I will try to answer your questions:
In my former organization I was the only designer within the agile
development team.
I was working on different project at the same time, some was interlinked.
The prototyping I would do my self using xhtml, css and basic JavaScript to
prototype UI
I've been working in Agile environments for about 2 years, and still
consider myself a noob. However, all that has been said I agree with,
and in my experience, it seems to be the best approach if you are
lucky enough to determine your approach.
It could be just my dumb luck, but in the two large
Reading this thread on this list has made me really happy! For a while
there I was thinking that I was the only person doing things this way,
and therefore it was either wrong, or totally radical! I am glad to
see its neither :)
I still don't think there are many people in the UK working like this
Well said Rich. I have been on Agile based projects for about 3 years now.
My thoughts on how a "start-up interaction designer" can use Agile to
his/her advantage:
1. Read about Agile and interpret it as a user centered design methodology.
2. Meet your client. Understand what they want to build,
Hi Rich
I totally agree with all the points you made, in my experience working
with UX/UCD and Agile things like making the methodology 'your'
methodology, as in whatever works for your organisation is fundamental
to success. Working one sprint/iteration ahead is a really good idea,
we always star
Hi Laura,
Regarding your last point, we're working with "Feature Driven Design" (FDD)
methodologies, (along with 3 or 4 other cobbled together methodologies ;).
FDD process embeds users/clients/engineers/QA/BA's (and a bunch of other
acronyms whom I'm not sure what they do), together in most desig
The Journal of Usability Studies had a great article on integrating
Agile/UCD, written by Desiree Sy last year:
http://www.upassoc.org/upa_publications/jus/2007may/agile-ucd.html
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/d
Hi,
Agile development offers new and interesting perspectives for interaction
designers and usability specialists(and great benefits : something to test
about every 4 weeks, continuous user feedback, focus on quality and
simplicity, lightweight but accurate format of "user stories", ...).
But they
I've worked as the UX application design lead within Agile processes for 9
or so years. I've experienced a few key initiatives which increase Design
success with Agile, and which make projects more successful in general.
Key Initiatives for Design success with Agile process:
1. Be flexible with t
Hi Loredana,
You can also check the previous threads for more of people's thoughts, as
there have been many interesting discussions on this subject:
http://ixda.org/search.php?tag=agile
Sebi
On Fri, Apr 18, 2008 at 3:09 AM, Loredana Crisan <[EMAIL PROTECTED]> wrote:
> What are your thoughts on
I think the conflict between design and agile development methods is best
understood by reflecting on the values conflict between the two
disciplines.
Here's a full list of the principles of agile development:
http://agilemanifesto.org/principles.html
These principles are ones I think designers
I have worked recently on a project that used the Scrum methodology
applied to UX, and it didn't work quite well. I think that the
reasons behind it was that the backlog wasn't properly laid out. I
would also advise you not to mix early stages of UX development with
implementation as it will really
I have used weekly user testings in an agile development environment. It
helped me, project managers and developers to keep focus on the users.
I had two kinds of prototypes for testing:
The prototypes also used to communicate with developers and project
managers.
And prototypes being very true to
>
> What are your thoughts on Interaction Design and the Agile Environment?
>
There's a Google Group focused on this exact subject, but a word of
warning—many of the list members are die-hard Agile purists, and offer very
little flexibility in adapted or "skewed" definitions of
Agile-with-a-capita
What are your thoughts on Interaction Design and the Agile Environment?
Here’s my experience of how extreme programming and design mix:
1) Product requirements are one thing today, another tomorrow, based
mainly on strategic (not user) feedback
2) Weekly iteration cycles allow 4-5 days for rese
17 matches
Mail list logo