UX Activities within Project Lifecycle

UX Activity

Agile /Scrum

or F
Experience/Journey Map
A Journey map is a visual or graphic interpretation of the overall story from an individual’s perspective of their relationship with an organization, service, product or brand, over time and across channels. The main goal of a journey map is to better understand and identify ways to improve each of the touch points a user or customer has with our product.
Service Blue Print

A Service blue print is closely related to a journey map except it extends the visualization to the backend services and workflows that are needed to support the individual interactions a customer may have with a product or service. The critical role of a service blue print is that it identifies all of the dependencies required to provide a great user experience for the client.



Brainstorming can be a same day or several day activity in which mockups are the resulting artifact. Brainstorming can happen for a new project, new feature or during backlog grooming. Typically white-boarding will happen on one day with an action item assigned to the UX resource to capture the output of session in a set of mockups. Based on bandwidth and timelines mockups are typically delivered in 1 to 3 days. Mockups should be used to gather feedback among stakeholders to validate the proposed idea.

This can be an iterative exercise that has multiple brainstorming sessions with the goal to further refine the mockups.

User Research

User Research activities include any or all of the following: user interviews, business stakeholder interviews, ghosting, and baseline usability testing session.

Ghosting and user interviews is where the UX team physically goes out and sits with our users to understand what they do today and identify potential improvements.

Business stakeholder interviews help with mapping business requirements to business value. The key element from a UX perspective is finding the true business need vs. the business want.

Usability Testing

Usability testing can be done with proposed mockups or prototypes to validate the effectiveness of proposed solutions. This can also be done with applications in production to baseline overall effectiveness and identify pain points for the user.

Interactive Prototype

Interactive (clickable) Prototypes are typically used to show how a user or flow moves through multiple screens. A prototype can be used to gain alignment across all stakeholders on how a user should interact with a screen or flow. It can also be used for usability testing to validate the overall design and interactions. Interactive prototypes should not be used for Development or QA as they tend to only show a few scenarios vs. a complete set of requirements.


Mockups are used extensively as the primary visual artifact to gather feedback and validation of a concept or design. Mockups are typically static although some interactivity is common.

* – During sprint planning, existing mockups can require minor updates to better support sprint development but requesting new mockups within sprint planning is strongly discouraged.

UX/UI Standards & Recommendations

Both UX and UI Recommendations can be requested at any time. UX and UI standards are published but if there are any questions we are glad to jump in and provide guidance. For Sprint Reviews the UX team will review the UI and identify any non-standard UI issues.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s