The document provides information about Experience Design Sprint Demos. It discusses how UX sprint demos are conducted to showcase work accomplished during a sprint, inform the dev team of what is ready for their next sprint, and keep stakeholders informed. It outlines the UX deliverable process, including design time, planning, visual design mockups and specs, development sprints, and reviews. It also provides recommendations for peer/PM/designer reviews using Glip conversation groups or meetings. Finally, it describes what is typically presented in a UX sprint demo, including Glip review outcomes, deliverables in JIRA, and design files uploaded to Google Drive.

1. Experience Design Sprint Demo
Creative Project Manager - Rachel Maple

2. ➔ To showcase what UX has accomplished during the sprint
➔ To inform Dev team what are ready for their next sprint
➔ The Project is assessed against the sprint goal
➔ Keep stakeholders informed and on the same page
➔ NOT a working session
Why We Do UX Sprint Demo

3. UX deliverable process

4. Sprint #1 Sprint #2 Sprint #3 Sprint #4
● Product Design
● Experience Design
Outcome:
● Reviewed with stakeholders
● Wireframe (IxD)
● Mockup (VxD)
● User story breakdown
● High level sprint
implementation plan
Design Time
Eng Planning
Visual Design (VxD) Visual Design (VxD) Visual Design (VxD)
● Mocks
● Spec
● Assets
● Mocks
● Spec
● Assets
● Mocks
● Spec
● Assets
Dev Sprint
demo
No design
Implementation
Bug Fixes OnlyUX design (IxD)
Design demo for S1
Visual Design (VxD)
Design demo for
the feature
Design demo for S2 Design demo for S3
Dev Sprint
demo
Dev Sprint
demo
User Story
XD Review XD Review XD Review
● Revised Spec &
assets
● Revised Spec &
assets
● Revised Spec &
assets
Bug Fixes (VxD)
● Mocks
● Spec
● Assets
Design demo for S3

5. PHON S1 PHON S2 PHON S3
UX S1 UX S2 UX S3 UX S4
PHON S4
Sprint 1:
● UI-1 → UIA → IOS → AB
● UI-2 → BDD
● UI-3 → PHON
● UI-4
Sprint 2:
● UI-5
● UI-6
○ UI-7
○ UI-8
● UI-9
● …...
UIA S1 UIA S2 UIA S3 UIA S4
iOS S1 iOS S2 iOS S3 iOS S4

6. Sprint 1
Sprint 2
Sprint 3

7. ➔ Design Peer reviewed - See peer review how2
➔ Design reviewed with by PM/PO and senior designer
◆ JIRA status = Resolved
◆ JIRA status = Closed
➔ Design artifact uploaded to JIRA & Google drive
◆ Wireframe, InVision Prototype, Mocks, Spec & Assets
UX Sprint “Udar” Readiness

8. Recommended peer/PM/designer review tools
➔ Glip conversation groups - Online review
◆ UX (SW) Service Web Review Group (TBC)
◆ UX Mobile Review Group (TBC)
◆ UX (GW) General Web Review Group (TBC)
◆ UX Spartan Review Group (TBC)
◆ UX RCC & RCV Group
➔ Meeting - Virtual face to face Review
◆ Arrange individual meeting with specific stakeholders
● PM/PO
● IxD & VxD
● UX Project manager
Preparation for Design Sprint Demo

9. (Tool) Review Group
➔ who involved or interested to the Glip Group
◆ For example “UX Mobile Review Group (TBC)”
● Must have: Ted, Bruce, Esther, Eliana, Girija, Igor, Wanning,
Sergey, Erik, Melissa, Rachel
● Nice to have: Jose, dev leader, Sophia, Helena
➔ Best practice:
◆ Use @mention for direct attention
◆ Create Glip task for specific action item to be conducted
● For example create a task for “Girijia to review Welcome
Screen-UI-1234.pdf by specify a date”
◆ Attached design artifact naming convention
● ios-User story-UI-xxxx

10. Google Drive Structure
➔ Level 1 Group - System
◆ [RC Mobile] iOS + Android
◆ [SW] Service Web
◆ [All] Email as user ID
◆ [Glip] iOS-Android-Desktop
➔ Level 2 Group - Feature within system
◆ [SW] Service Web
● [SW] Phone & Devices
● [SW] Add Devices
● [SW] Hot Desking
➔ Level 3 Group - Feature
◆ Wireframe & Flow sub-folder
● Sketch & PDF file
◆ Assets sub-folder
● PNG file ( Zip)
◆ Spec sub-folder
● Sketch and PDF file
◆ Mockups sub-folder
● Sketch & PNG file
◆ Working sub-folder
● All files that still in progress

11. Google Drive Folder Structure
Root - Level 1
Year - Level 2
Feature - Level 4
Global Product Design
2016 UX Projects
[SW] Service WebPlatform - Level 3
[SW] Phone&Devices
Spec
sub-folder
Assets
sub-folder
Working
sub-folder
Latest Sketch Files
Latest Mockup Files (PDF, PNG
and any other formats
Final Specification
Folder Prefixes:
[SW] - Service Web
[ALL] - feature to be implemented across all
platforms
[GW] - General Web
[RC Mobile] Ringcentral Mobile App
[Glip] Glip Mobile / Web App
[MMA] -
[DPW] - Developer Portal
[Spartan] - Ringcentral Desktop App
Everything that still in progress
Keep as daily upload, so distributed
team can always get latest version
Final Production Assets in ZIP

12. ➔ Latest design in following formats:
◆ PDF / PNG for mocks
◆ InVision for user follow or Hi-Fi prototype
➔ User Story is completed
➔ Ready to pass on to development team
What is presented in UX Sprint “Udar”

13. 1. Glip Review Group
a. Reviewed with dev to ensure design implementable
b. Peer Reviewed: reviewed among of designer community in Glip review
group
c. PM/PO Reviewed: All the requirement criterias are met; given “Go”
greenlight in the Glip review group
2. [Optional ] Executive reviewed and sign-off
3. Deliverable in JIRA
a. Design Artifacts are uploaded to JIRA user story
b. Latest design uploaded in the google drive
c. JIRA User Story Status = Resolved/Closed
UX Sprint “Udar” Checklist

15. UX Sprint “Udar” Invitation
➔ User story related stakeholders
◆ Executive/PM/PO
◆ Dev team
◆ UX designers
➔ Anyone interested to learn what design goes to next sprint

16. ➔ Discussion group - UX Sprint Group (TBC)
◆ Agenda
◆ Meeting minutes
◆ Action Items
➔ Meeting Structure
◆ Content will be communicated in the UX Sprint Group
◆ Frequency: per sprint ( every 2 weeks)
◆ Length: 1 - 2 hours (TBD per meeting)
◆ Meeting Type: RC Meeting (will be recorded)
◆ Suggested date on Tue or Wed or Thur PST
◆ Suggested time (TBD)
UX Sprint Meeting

17. Peer Review

18. Peer Review Outcome
● Building a communicative user-centered design community
● Design thinking process practice
○ Diverge to discover & research
○ Converge to develop & Deliver
● Bring design consistency across the products
● Bring stakeholders on the same page
● A qualitative feedback to up-bring design quality within the origination
● Deliver ONE awesome design for RC product

19. Path#1 Path#2 Path#3
(UX sprint Demo)
Audience Internal local UX designers UX, PM, Dev, User All Stakeholders
Design grade Draft Low-fi wireframe Hi-fi prototype/Mocks
Design artifact Multiple ideas/concepts 1 - 2 prototypes Wire, spec, assets
Outcome Action items to refine
design
A qualitative feedback
from the teams
Development
Candidate
Meeting Optional ( 1 hour) Optional(1 hours) 1 - 2 Hours+
Glip Group Review recommended recommended Glip - UX Sprint “udar”
Peer Review
Diverging Converging Deliver
*Executive review is optional and depends on the PM

20. q&aEmail : rachel.maple@ringcentral.com