Home > Articles > Programming

Interfaith Marriage: Experience Design Meets Agile Development, Part 1

Larry Constantine explains that when experience design is married with agile development, the results can be a crisis of faith on either or both sides. Unfortunately, it is usually experience design that is modified or mangled to fit into the particular agile method being performed. Can this marriage be saved?
Like this article? We recommend

Like a quarrelsome family of competitive siblings who are always ganging up two-against-one, the classic trio of project objectives—cheap, fast, and good—are locked in perpetual opposition. The old saying is that you can have any two out of three; the other is inevitably sacrificed or severely compromised. Agile methods make a valiant effort to bring domestic tranquility to the software project triplets through a clever mix of philosophy, techniques, and strategies that are aimed at delivering reliable code, on time, for less. Depending on to whom you listen and to what statistics you are prepared to grant credence, agile projects—at least up to some still-debated scale—have been generally successful in serving up some of each of the cheap-fast-good buffet.

By at least one metric, agile software development methods and techniques have been a virtually unqualified success. A steadily growing fraction of the industry is adopting—or at least claiming to adopt—some agile practices, in the process generating heated debate over what is truly agile and what is mere lip service. Teams risk criticism from peers if they fail to fully embrace the underlying tenets or are too selective in their observance of practices. Agility is, of course, more than just a tub of techniques. It is a philosophy, a movement supported by its own manifesto, and while stories abound and research on the effectiveness of its sundry components is beginning to accrue, for many practitioners, adherence to the true path is still mostly based on personal experience and conviction.

The same can be said of the user experience community. Papers challenging the canon of received wisdom and established techniques are vociferously attacked, even when written by such venerable elders of the field as Don Norman (“Human-Centered Design Considered Harmful”), who has been criticized for recanting the articles of faith of user-centered design, an amusing accusation considering that Norman is generally credited with having invented the term. My own similar heresy (“Beyond User-Centered Design and User Experience,” Cutter IT Journal, 17 (2), February, 2004) drew less flak, but then I’m not Don Norman.

When these two meet, when experience design is married with agile development, the results can be a crisis of faith on either or both sides.

Troubled Engagement

Unfortunately, agile approaches did not at the outset incorporate practices explicitly concerned with users and user interaction, or usability and user interfaces. Although Extreme Programming makes the so-called customer role central, customers are not, in most cases, the same as users, and the customer role is more focused on functionality than on usability. In their slight of users, the agile methods resemble most other software development methods, which have a long history of treating users, user interfaces, and usability as afterthoughts at best or at worst as irrelevant. I myself am guilty in this regard, having pretty much left users out of the equation in the now ancient techniques of structured design, a sin that I repented and for which I did penance by developing, with Lucy Lockwood, the body of techniques that came to be known as usage-centered design. (See the somewhat dated but still very usable Software for Use.)

At the same time as the agile methods were gaining market share, the marketplace in software applications and web sites and services was becoming more tuned in to the voice of users and to the issue of user experience. Customers were demanding applications and services that were easier to use, easier to learn to use, and more satisfying. And smart executives were moving from a superficial flag-waving allegiance to customer-centered business models and adopting a deeper commitment to design culture in which experience design and service design are at the core. Apple’s success story with iTunes and the iPod is a most visible example, but on a smaller scale, many companies have been embracing a whole-systems approach to service and product design built on a user experience foundation.

Many professionals on both sides of the aisle—Jeff Patton, Scott Ambler, Ron Jeffries, Thomas Memmel, Don Norman, and Jakob Nielsen, among others—jumped into the role of matchmakers, promoting a relationship or rapprochement between experience design and agile development. This has been a long engagement. I’ve been writing about user interaction design and agile methods since the turn of the century (are we allowed to say that now that we are in the second decade of the millennium?), and Jeff Patton’s agile-usability forum (agile-usability at Yahoo Groups) dates from 2004. But what really happens when the adherents of these disparate disciplines are pushed into a marriage of convenience in the name of better, cheaper, faster software development? Let the newlywed games begin!


The dialogue and spats have been rather public, not only in online forums but also at the various agile conferences and even at academic conferences like the ACM’s SIGCHI, as well as in a variety of print media. An interesting aspect of this speed-dating dialogue has been that, for the most part, nearly all of the narrative so far has been about experience designers accommodating to the dictates of agile methods and schedules. Hardly a word is printed or spoken about what developers might do to accommodate the agenda and practices of designers. Short stand-up meetings, test-first development, 2-3 week sprints, emergent requirements, avoidance of upfront analysis or design, pair-programming, rapid incremental development with re-architecting, the customer role with user stories—all the practices and paraphernalia of agile development tend to be assumed as fixed and given, while the practices and processes of experience design are modified or mangled to fit into the particular agile method being performed.

I have sat through panels, most recently at SIGCHI 2008 in Italy, in which not a word was said about what might be wrong with agile methods and what needed to be changed if they are to produce end products that are more usable and more useful. Even the mere suggestion that agile methods might be changed to better accommodate experience design has been the excuse for attacks, both online and off.

Compatible Coupling?

As a consulting interaction designer, I have worked on a number of agile development projects employing various methods under a variety of management models. Unfortunately, user experience and usability as key drivers for development are not a simple plug-and-play fit with most agile development processes. Many of the first groups that tried a force-fit learned that the partners in the shotgun marriage were often at odds. I have concluded that a number of things are needed if this marriage of agile development with experience design is to work well and last over the long haul.

There are many core incompatibilities in this couple. Agile methods employ rapid, iterative refinement, with short, incremental development cycles. The imperative is to produce executable code and deliver added functionality at each iteration right from the get-go. BDUF, for Big Design Up-Front, is a curse to be avoided at all cost. The single most important criteria, embodied in the test-first development approach, is that each increment of expanded code run to completion, executing correctly to produce the right output. Little or nothing is said about the usability of the results or of the means for the end-user to reach them. Test-first development does not include or address user testing, and it is arguable whether it should or even could.

User experience design, on the other hand, tends to front-load activities, often beginning with a fairly long lead-up devoted to field study and observation of users, analysis of user requirements, user modeling, prototyping, and visual and interaction design. User testing is often a fairly time- and labor-intensive activity that may sometimes be integrated with prototyping but is almost always heaviest late in a project when a beta or later version becomes available. In general, experience design assumes that a design will be completed in substantial detail before anything beyond a prototype is built, because user experience is usually shaped as much by subtle details and their precise interconnection as by overall structure and organization.

The agile approaches tend to favor a functionality-first, inside-out process, beginning with early and easy successes that deliver working—if limited—code. Experience design at its best and purest is an outside-in process that favors full, overall understanding before detail design or implementation even begins.

For a simple example that embodies some of the difference between a functionality-first approach and a user-experience perspective, consider the issue of establishing login credentials for new users of a website. The worse design from the standpoint of user experience is the classic and all-too-common one that forces the new user to pick an ID and password before they can do anything. To users, this experience is a barrier that gets in the way of merely getting on with what they want to accomplish. An outside-in interaction design approach considers, first and foremost, the whole of the user experience. That leads to a very different design in which, for example, the user who has already completed a purchase is offered, at the last moment, the chance to save already entered details with a user ID and password. This entails an incremental action that is experienced as an easy bonus, rather than an annoying barrier.

Given these deep philosophical differences and variance in practices, can this marriage be saved? Tune in to Part 2 for a counselor’s suggestions for a better marriage of methods.

Larry Constantine is an award-winning interaction designer, a pioneer in software engineering, and a novelist. Under his pen name, Lior Samson, his first novel, Bashert, has already been published and a second, The Dome, is slated for October release. Both are fast-paced political thrillers with technology twists—stories “to feed the inner nerd,” as one reviewer phrased it. They are available from Amazon and http://www.liorsamson.com. Constantine’s day job is as Institute Fellow at the Madeira Interactive Technologies Institute and as professor at the University of Madeira.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020