Step 2: UX Scoping and Initial Design

Step 2: UX Scoping and Initial Design


    • Storyboard
      • Use of story telling to quickly visualize/share a solution to specific requirements making use of personas and their behaviors, stories and any known constraints.
      • Who does it? The Team (engage the client if you can) – you don’t need to be good at drawing.
      • Key Benefits:
        • Help us think about the problem in a creative way
        • Facilitates focused communication
        • Affordable and easy to do

    • Sketchboard
      • It’s like story boarding but with sketches, almost like a biomap o the system you are building or about to build.
      • Who does it? Team with UX/designer’s help
      • Key Benefits:
        • Provides Big Picture using initial design ideas
        • Very iterative and highly collaboratively
        • Very focused requirement discussions
    • Elevator pitch
      • Short summary used to quickly and simply define a product and its value proposition.
      • For [target customer]
      • who [statement of the need or opportunity]
      • the [product name]
      • is a [product category]
      • that [key benefit, compelling reason to buy].
      • Unlike [primary competitive alternative]
      • our product [statement of primary differentiation].
      • Who does it? The Team
      • Key Benefits:
      • Provides Business relevance and context
      • Forces to agree on killer feature(s)
    I personally like focus on the Value Proposition angle of the Elevator Speech.
    • User Stories
      • Software system requirement formulated in one or two sentences in everyday or business language that makes explicit the user’s need. Example:
        • As a [type of user] !
        • I want to [perform some task] !
        • so that I can [reach some goal]!
      • Who does this? The team (dev, tester, doc or UX)
      • Key Benefits:
        • Provides a thinking template; token for a conversation
        • Description of why the product needs to do what it does

    • Story mapping
      • Board with organized and prioritized system functionality (user stories)
      • Who does this? The team with Product Owner (Business person)
      • Key Benefits:
        • Provides the high-level vision of the system, which includes workflow or value chain as well as hierarchy information
    Jeff Patton is a big fan of mine I saw him in Øredev 2011 and again in Agile 2012. I have read his blog an think of him as one of my guiding persons. 

    Well at Agile 2010 I attended a session by Pascal Van Cauwenberghe that also show that user story mapping can be used for figuring out business Value, flow description, clicking way though / Journey maps, adding Feelings and moods of different users and so fort. User Story mapping is a GREAT tool for modeling the users interaction and hereby get more and better visualized understanding of the users expectation.
    • “Agile schedule”
      • Visual project schedule/plan on butcher paper containing:
        • Milestones
        • Design and layout info
        • User stories with due dates
        • “Non-functional” requirements
        • Any high-level task that needs to be tracked and completed
      • Who does it? Ideally, the team; at least Project lead with UX
      • Key Benefits:
        • Provides shared understanding and current status to the whole team
        • Provides context and layout information
        • Deadlines are made explicit

    • BDD
      • A set of techniques to use in conversations which help the team explore the intended behavior of the system and the problems it solves, then carry the conversations and language into the code.
        • Given some initial context (the given)!
        • When an event occurs!
        • Then some outcomes should occur
      • Who does it? Ideally a threesome (dev, tester and business)
      • Key Benefits:
        • Deliberately discovering key misunderstandings and uncertainty
        • Makes it easier for technical and business people to communicate
        • Accelerates learning

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>