Versions Compared

Old Version 5

changes.mady.by.user Matthew Evert

Saved on

compared with

New Version Current

changes.mady.by.user Karen Jennings

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

https://fergusonprod.atlassian.net/browse/EDEX-801 - Jump to Work

Overview

Requested by Billy Colonna, Product Team on April 21, 2020

Description

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Maecenas facilisis orci ut luctus blandit. Vestibulum in urna a odio ornare rhoncus. Nam vestibulum odio eget ante luctus, ac pulvinar orci accumsan. Cras pretium placerat augue, ut lacinia turpis sollicitudin vitae. Sed ac pulvinar tellus. Pellentesque in pharetra quam. Phasellus eget lectus scelerisque, dignissim elit eget, laoreet dolor.

What is the problem?

How did you become aware of the problem?

Who is affected (customer, associate)?

What is the value to the business and/or customers?

Ideal outcome

Known constraints

People

UX

  • Laurie Allen Laurie Allen, Research Lead

  • James Corcoran, Researcher

  • Dan Flynn, Designer

  • Drew Palko, Checkout Design SME

profile

user5d5d4ca45a68ef0ca6256ac7

Product Team

  • Billy Colonna, Product Manager, Requestor

Stakeholders

Work

4/23/20 Week 1 - Research analytics 

Research

Discovery

???

Analysis

???

Design

Solutioning

???
Prototyping?

https://fergusonprod.atlassian.net/browse/EDEX-669

Testing

Test prototype
Create test plan

Pros:

  • Compact

  • Easy to edit and sketch out work

Cons:

  • May be redundant if we have to put information (dates for example) in two places, Jira and Confluence

Production

TBD

Research Timeline

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
jqlQuerykey = edex-808
serverId6f628555-4e88-3de1-a113-9682348a2f13

Test prototype

Pros:

  • Automated

  • Always up to date

  • Ability to show flagged tickets

  • Ability to pull in info straight from the ticket

Cons:

  • Tickets are sorted by Key only

  • can’t put info in between tickets, all lumped together

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,timeoriginalestimate,assignee,status,flagged
jqlQueryproject = "DXT" and ("Epic Link" = EDEX-801) AND labels = ux-research-analysis
serverId6f628555-4e88-3de1-a113-9682348a2f13

Production

  • Week 6

    • UI Design Begins

Evaluation

  • Week 7

    • Rollout Begins

  • Week 8

    • Design Evaluation Begins

Research Timeline

5/4-8/20 Week 2 - Recruit customers

5/11/20 Week 3 - Review prototype; design usability test

5/18/20 Week 4 - Conduct usability tests

5/25/20 Week 5 - Analyze and report results

Resources

Participant Spreadsheet: https://drive.google.com/drive/folders/1gv93bIDnxJYScMj3CcodwjsNDkVM4E6y

Study Plan: https://docs.google.com/document/d/1LC-BPgeqtKyr8OeLtzG0o0JbaoY3S8HZ0wP1ny4lRS4/edit#