A presentation deck explaining the custom enterprise agile UX framework "Tidal UX" created by Hannah Grossman

1. Hannah Grossman
Experience Architect at The Nerdery
hannahgrossman.com // @landofdoors
An Enterprise-grown agile framework

2. TOPICS:
A bit about me
The need for a new framework
What is “Tidal UX” and why is it different?
Product example
Discussion/Q&A

3. I LIKE BIG, MESSY
PROBLEMS

4. I’ve learned that sometimes you just
have to dive in.

5. GETTING STARTED
SOMETIMES FEELS LIKE THIS:
AND MANY OF US
WOULD RATHER IT BE LIKE THIS:
ORGANIZED, METHODICAL

6. AGILE UX
Both ideas priori-ze providing value to our users:
“Our goal is not to create a deliverable, it’s to change
something in the world—to create an outcome.”
- Jeff Gothelf, “Lean UX”
…SO WHAT’S WITH THE “ICKY” FEELING?

7. BALANCING vision WITH
ACTION IS HARD.
That cartoon that everyone knows. Unknown original source.

8. Tidal UX

10. THE BIG IDEA
Concept: An app to replace paper forms collected during a course
Value: Saves -me, beJer repor-ng & analy-cs
Features: Login and Registra-on, Course Crea-on, Form Crea-on, Data Input,
Repor-ng
Constraints: Data privacy/security, training session on 1/1/2017

11. ALIGNING ON VISION & RELEASE
Research & Validate: We interviewed course facilitators and data entry folks. We sat
in on a course. Turns out, facilitators have spare -me between periods… mobile?!
Roadmap & ArJculate: Our charter states that we will, “Create a responsive form
building, data entry, and repor-ng applica-on.” The first part is collec-ng the data.
Align: Together, we talked through each of our users and their journeys. There
seemed to be a “slice” of value-added func-onality around data collec-on and
proposed an R1 with hard-coded course forms.

12. BUILDING A BACKLOG
Release Planning: We met and sequenced out the work, moving backward from
our 1/1/2017 date.
Sprint 0: While dev worked on SPIKES around seang up environment and data
model, UX SPIKED on fully understanding the security requirements, form details,
logic, and hierarchical structure of courses + facilitators.
The First Story!: We came up with requirements for login, and UX sketched some
screens!

13. SPRINTING
Decomposed Design: During Release Planning, we’d broken down our work into Epics,
which loosely corresponded to screens. A core set of flows were created and tested
with users.
Backlog Grooming & Sprint Planning: As screens/designs were designed (or
sketched!), they were broken down into subtasks, then pulled into sprints.
What about those Experiments!: As the backlog dwindled, by aJen-on turned
towards data visualiza-ons and repor-ng, something that would be coming down the
pipeline (and had lots of room for design!)

14. RELEASE & ITERATE
UAT: Our users were brought in for UAT throughout (and we all QA’d), so we were
able to add a handful of Stretch Goals for easy enhancements.
Deployment: Our final push went through another round of end-to-end
performance tes-ng, which we piggybacked with user tes-ng.
RetrospecJve & Planning for the Next Release: We met to talk through what
went well, what didn’t, and discuss our backlog for the next release (revisi-ng our
journeys).

15. IT’S DIVING DEEP, BUT COMING UP FREQUENTLY
TO KEEP AN EYE ON THE TIDES
(And to breathe. Don’t forget that.)

16. Thanks!
hannahgrossman.com // @landofdoors