Loading ...
Sorry, an error occurred while loading the content.

Re: [agile-usability] Re: UX roadmap development guidance for product owners

Expand Messages
  • Robin Dymond
    What is a UX road map? When I think of product road maps it is usually because a sales guy wants to know what we will be building in 2014 so he can go pitch
    Message 1 of 8 , Mar 4, 2011
      What is a UX road map?

      When I think of product road maps it is usually because a sales guy wants to know what we will be building in 2014 so he can go pitch the future to a customer. Except the future has a way of changing that seems to surprise customers who have been sold a vision of the future. After the rise of facebook, the decline of Nokia, the rise of Android, the decline of Windows Mobile, the rise of Twitter, the decline of Yahoo etc. etc. you would hope that people would start to understand that the future is rather unpredictable, in both a macro and micro scale.

      Robin Dymond, CST
      Managing Partner, Innovel, LLC.
      Americas: (804) 239-4329
      Europe: +32 489 674 366

      On Tue, Feb 22, 2011 at 7:53 PM, Jon Innes <jinnes@...> wrote:

      I've been following this thread. I have to agree with Hugh and others here about the importance of user stories not being "fiction".

      If you're in a B2B or IT space, I just got interviewed by a VC by the name of Bruce Cleveland. He was an exec and early employee at Oracle and Siebel and remains very active in Silicon Valley. We discuss the challenges you might face in your projects. You can read the interview at:


      --- In agile-usability@yahoogroups.com, "hughrbeyer" <beyer@...> wrote:
      > I just posted a reference to my monograph on UX and Agile (User-Centered
      > Agile Methods) which deals with this question in some detail. But here's
      > the short version:
      > Yes, UX work should be built into every sprint, so it's not an
      > independent activity from development. But that UX work is specific to
      > particular user stories--each user story that requires a UI requires
      > some UX time to design and validate that UI.
      > What goes on your roadmap is the other UX work. Before development
      > starts, you need some user research and conceptual design work to
      > organize the whole system. I think of this as teaching your
      > Customer/Product Owner what they need to know to guide the team. UX has
      > a primary role to play here, since they are generally the ones with the
      > field research skills to get the right data from users and pull out the
      > implications for design.
      > In a system of any complexity (i.e. requiring the coordinated work of
      > several development teams to deliver), you're likely to want to maintain
      > a UX stream in parallel. The role of this team is to maintain the
      > coherence of the user experience across the whole system. The people on
      > the team may not be full time--they're likely to be on individual Agile
      > teams as well--but keeping this a separate activity maintains it as a
      > focus.
      > Hugh Beyer
      > --- In agile-usability@yahoogroups.com, "pvancleve"
      > <paula.m.van.cleve@> wrote:
      > >
      > > Hi,
      > >
      > > Our IT organization is beginning to integrate user centered design
      > into our work practices including strategic capability roadmaps. We've
      > demonstrated that we can deliver valuable technology solutions but not
      > sure how to evolve our roadmaps more into ones focused first on desired
      > user experiences and then the software and hardware.
      > >
      > > Does anyone have key learnings or suggested training content that
      > could help guide our product owners and business partners as they start
      > to add the user experience dimension to our strategic roadmaps?
      > >
      > > Thanks in advance,
      > > ~Paula
      > >

    Your message has been successfully submitted and would be delivered to recipients shortly.