We’ve come a long way since 2004. That
year, one tech forecaster made the bold
prediction that "eventually up to one
third" of smartphones would include a
camera. He could hardly have imagined
the popularity of selfie sticks today.
That same year, the agile movement was
emerging, prompting some members
of the UX community to wonder about
its impact. Were agile and UX going to
form a dream team or an odd couple? To
answer this question, I interviewed UX
specialists about their initial experience
with agile and shared the results in an
Interactions article in 2005 [ 1].
Fast for ward to 2016, when I received
a notification from ResearchGate
that this article had been cited in 50
subsequent articles. At first, I was
astounded that so many articles had
been written on this topic. Then I
thought back to 12 years ago and
marveled at how things had evolved in
both the agile and UX communities.
Even the terms agile and UX have been
joined, and possibly superseded, by new
terms like lean and design thinking. Many
people I work with have only known an
agile lifecycle. Finally, I wondered: What
became of the people I interviewed in
2004? Had their perspective changed
after 12 years? I decided to find out and
share the results in this article.
When I reconnected with the people
interviewed in the original article
( Thank you, LinkedIn!), they were
all still working in UX roles and were
happy to share an update. Here’s what
they’ve been up to since 2004:
• MG has worked for multiple
organizations in generalist UX roles and
in both agile and non-agile teams.
WInsights → Agile makes collaborating with developers easier but provides inadequate opportunities to work with users. → While UX specialists like agile in theory, their satisfaction with actual projects is lower due to significant shortfalls in how teams implement agile practices. → Most important is that the project is well managed
and that developers are
attuned to UX.
Paul McInerney, IBM
After 12 Years