The title pretty much says it all. After working for a while now in an agile development model. I’ve discovered several disturbing things that really cause a loss of sanity. The agile development cycle is quite fast. Depending on your team it has different lengths. Most iterations seem to be 1 week long. During that week developers develop working software. Notice I said working software and not “USABLE.”
The primary prescribers to the agile method believe that the UI should pretty much just be slapped on at the end. I paraphrase but something to the likes of “Leave The UI out until the last possible moment.” I find this to be extremely scary. Especially when the thought process behind the agile development methodology is to think of the end user. So to put this all into perspective. We have one side of this method that says leave out the UI until the end but keep the user in mind when creating the story (feature). I know when I first heard this I was a bit shocked by the contradictory nature. So like any process I attempted to make it my own and mold the process to my own needs.
more to come…
Twitter is a great way to share new and exciting resources with all our viewers. Each day I provide links and commentary on all things UI. You can find UI resources, UI design examples, new techniques, and a lot more by Following @UIDESIGNGUIDE on Twitter.

The idea for this design blog first came about two years ago at SXSW Interactive.
Currently UI Design guide is in its fourth redesign. This site takes quite a bit of time to maintain as well as write the content. Just like UI Design this site is a passion that keeps evolving.
Inside, I cover articles on many topics icluding: lessons, prototyping methods, agile UX methods, design reviews, design challenges, application features, and of course design experiences, just to name a few.
With all the blogs out there you may be asking yourself who are you to give advice? That's a fair question. If you have a moment feel free to read about my design history.