Skip to end of banner
Go to start of banner

Punchout - Local Inventory

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Placeholder for epic.

Overview

Requested by Billy Colonna, Product Team on June 11, 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

  • Drew Palko, Designer

Product Team

  • Billy Colonna, Product Manager, Requestor

Stakeholders

Meeting Notes for Discovery Meeting - June 11

Attendees

  • Drew

  • Billy

Objective

  • Define problem statement and ideal solution

  • Capture questions and action Items required to begin discovery

  • Schedule follow up

record meeting

Work

Research

Discovery

???

Analysis

???

Design

Solutioning

Prototyping?

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

Testing

Test prototype

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

key summary type created updated due assignee reporter priority status resolution
Refresh

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

key summary timeoriginalestimate assignee status flagged
Refresh

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


  • No labels