agile ui design
This is the third article in my long running series on Agile and User Experience Design. I have a feeling this will generate quite a bit of discussion and as an experiment I will also post this on my Google + stream. Let’s get started shall we.
As a UX professional, agile is less about a methodology and more about adaptive design practices. It’s about taking all of your “UXPERIENCES” and squeezing them into a magic box and then pulling out the tool, item, or design pattern you need. It’s about taking business requirements and using an idea to formulate working models and design concepts. The tools are not the Swiss army knife, you are! The key to making Agile UX work for you is the ability to draw upon experiences and resources quicker and faster. You need to be able to filter what’s important and what isn’t.
I’ve been banging my head against a wall trying to figure this question out for some time now. Can existing in an agile development cycle truly create the best ui design? I’ve worked in Agile development environments. I’ve worked with structured project management. I’ve worked in locations where I am the project leader.
Welcome to my three part series (so far), delving into real world UI experiences in relation to Agile Development Methodologies. In these three parts I will explore solutions, problems, and suggestions for dealing with the various phases of an agile development cycle. More importantly, this will be from the point-of-view of a UI designer.