LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
I’ve learned that sometimes you just
have to dive in.
SOMETIMES FEELS LIKE THIS:
AND MANY OF US
WOULD RATHER IT BE LIKE THIS:
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.”
- Jeﬀ Gothelf, “Lean UX”
…SO WHAT’S WITH THE “ICKY” FEELING?
BALANCING vision WITH
ACTION IS HARD.
That cartoon that everyone knows. Unknown original source.
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,
Constraints: Data privacy/security, training session on 1/1/2017
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 ﬁrst 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.
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
Decomposed Design: During Release Planning, we’d broken down our work into Epics,
which loosely corresponded to screens. A core set of ﬂows were created and tested
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!)
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 ﬁnal 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
IT’S DIVING DEEP, BUT COMING UP FREQUENTLY
TO KEEP AN EYE ON THE TIDES
(And to breathe. Don’t forget that.)