We all know about the wide-ranging dysfunction of a traditional document-centered UX practice, such as the impossible-to-maintain always-outdated big specification documents. Adopting an Agile approach to UX was supposed to make all that pain go away. But for many, it has instead only led to replacing old dysfunctions with new ones, such as “feeding the backlog beast,” “agilefall,” “sprint tunnelvision,” and the half-baked UI, to name a few. Why is this the case? And what can you do to replace it with a healthier, more holistic approach to integrating Agile and UX? In this session, we’ll first explain the sources of this dysfunction, such as the enterprise software origins of well-known Agile methods like Scrum and XP. We’ll then discuss how we can apply the same thinking that drove the creation of those methods toward developing our own UX-specific Agile methods, which, because they are based on the same thinking, also integrate seamlessly with the more delivery-oriented Agile methods. Examples of methods we’ll discuss will include collaboration-driven documents, ux stories, ux cadences, trailing documentation, and cross-functional pairing.

Half past 3 o’clock in the morning here….as the title suggests i don’t really sleep much these days…just updated some new tracks to myspace………my ipod won’t charge off my usb…….i wanted to listen to some greek mythology audio books to fall asleep…..mind you it doesn’t really help…i just end up followig the stories and staying awake……….have to get one those charger things ….you’d think they could have thrown that in (what do you mean it’s not included in the price!!)