Clash of the Titans: Agile and UCD

Agile software development has become fairly popular in the last few years, leaving many UX professionals wondering how user-centered design (UCD) can fit into an extremely fast-paced development process that uses little documentation. User-centered design can involve a variety of techniques that provide insights into users' wants, needs, and goals, including ethnography, contextual inquiry, contextual interviewing, usability testing, task analysis, and others. But all of these take time--time that an agile development process might not allow. There is hope, though. Agile and UCD methods are not completely at odds with each other--and in some cases, agile development can even enable a more user-centered approach. By taking the time to understand the differences and similarities between agile development and UCD, it's possible to devise a process that is both user-centered and agile.

Cecil, Richard F. UXmatters (2006). Articles>User Centered Design>Agile

Composition and Usability

Since the advent of the Web, we've seen a myriad of design schemas evolve--from the simple navigation/content style of site to the cluttered portal. And as this evolution has progressed, so did the war between UI designers and usability experts. On one side, there are usability experts who want to make every website look exactly like Yahoo because users know Yahoo and so they will automatically know how to use the site. On the other side, there are UI designers who want to design entire sites in Flash and Shockwave just because it's cool. Overly dramatic? Well, yes, maybe a little--but it's not entirely a false analysis. Many UI designers that work with usability folk complain that their creativity is hampered, whereas many usability gurus complain that designers are confusing a site's user with their visual semantics. But are the goals of UI designers and the usability folk that far apart?

Cecil, Richard F. Digital Web Magazine (2000). Articles>Usability>Web Design>Semantic

Designing the Mobile User Experience

Today, we're trying to understand how mobile devices--and by extension the mobile Web--can fit into and even enhance our day-to-day lives. As we do so, we should endeavor to avoid the mistakes we made before we understood the opportunity inherent in the Web.

Cecil, Richard F. UXmatters (2006). Design>Web Design>Wireless Web>Mobile

Documenting the Design of Rich Internet Applications: A Visual Language for State

Ajax and Rich Internet Applications (RIAs) have revolutionized the way users interact with Web sites. However, documenting the design of any page that uses Ajax is a challenge, because the page--and, more importantly, components on the page--can have different states, depending on how users interact with the page's components.

Cecil, Richard F. UXmatters (2007). Design>Web Design>Multimedia>Ajax

Communicating Customer and Business Value with a Value Matrix

What happens to the personas and scenarios once you’re ready to start requirements definition and design. Are you sure you’ve adequately communicated the type of system your users need to the Business Analyst and Interaction Designer on your team?

Cecil, Richard F. UXmatters (2008). Articles>Collaboration>User Experience>Assessment

Communicating Customer and Business Value with a Value Matrix

If you’re like me, you’ve always felt something was missing once you finished creating your personas and scenarios. They communicate the heart and goals of the user, but miss out on a lot of details. And while it’s the intent of both documents to do just that, neither personas nor scenarios succinctly communicates to your business what features a product or service should have and why it should have them.

Cecil, Richard F. UXmatters (2008). Articles>Business Communication>Assessment>Personas