tidal ux presentation from ux meetup

Hannah Grossman Experience Architect at The Nerdery

hannahgrossman.com // @landofdoors

An Enterprise-grown agile framework

TOPICS:Abitaboutme

Theneedforanewframework

Whatis“TidalUX”andwhyisitdifferent?

Productexample

Discussion/Q&A

I LIKE BIG, MESSY PROBLEMS

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

GETTING STARTED SOMETIMES FEELS LIKE THIS:

AND MANY OF US WOULD RATHER IT BE LIKE THIS:ORGANIZED, METHODICAL

AGILE UX Bothideaspriori-zeprovidingvaluetoourusers:

“Our goal is not to create a deliverable, it’s to change something in the world—to create an outcome.”

-JeffGothelf,“LeanUX”

…SO WHAT’S WITH THE “ICKY” FEELING?

BALANCING vision WITH ACTION IS HARD.

Thatcartoonthateveryoneknows.Unknownoriginalsource.

Tidal UX

THE BIG IDEAConcept:Anapptoreplacepaperformscollectedduringacourse

Value:Saves-me,beJerrepor-ng&analy-cs

Features:LoginandRegistra-on,CourseCrea-on,FormCrea-on,DataInput,Repor-ng

Constraints:Dataprivacy/security,trainingsessionon1/1/2017

ALIGNING ON VISION & RELEASEResearch&Validate:Weinterviewedcoursefacilitatorsanddataentryfolks.Wesatinonacourse.Turnsout,facilitatorshavespare-mebetweenperiods…mobile?!

Roadmap&ArJculate:Ourcharterstatesthatwewill,“Createaresponsiveformbuilding,dataentry,andrepor-ngapplica-on.”Thefirstpartiscollec-ngthedata.

Align:Together,wetalkedthrougheachofourusersandtheirjourneys.Thereseemedtobea“slice”ofvalue-addedfunc-onalityarounddatacollec-onandproposedanR1withhard-codedcourseforms.

BUILDING A BACKLOGReleasePlanning:Wemetandsequencedoutthework,movingbackwardfromour1/1/2017date.

Sprint0:WhiledevworkedonSPIKESaroundseangupenvironmentanddatamodel,UXSPIKEDonfullyunderstandingthesecurityrequirements,formdetails,logic,andhierarchicalstructureofcourses+facilitators.

TheFirstStory!:Wecameupwithrequirementsforlogin,andUXsketchedsomescreens!

SPRINTINGDecomposedDesign:DuringReleasePlanning,we’dbrokendownourworkintoEpics,whichlooselycorrespondedtoscreens.Acoresetofflowswerecreatedandtestedwithusers.

BacklogGrooming&SprintPlanning:Asscreens/designsweredesigned(orsketched!),theywerebrokendownintosubtasks,thenpulledintosprints.

WhataboutthoseExperiments!:Asthebacklogdwindled,byaJen-onturnedtowardsdatavisualiza-onsandrepor-ng,somethingthatwouldbecomingdownthepipeline(andhadlotsofroomfordesign!)

RELEASE & ITERATEUAT:OuruserswerebroughtinforUATthroughout(andweallQA’d),sowewereabletoaddahandfulofStretchGoalsforeasyenhancements.

Deployment:Ourfinalpushwentthroughanotherroundofend-to-endperformancetes-ng,whichwepiggybackedwithusertes-ng.

RetrospecJve&PlanningfortheNextRelease:Wemettotalkthroughwhatwentwell,whatdidn’t,anddiscussourbacklogforthenextrelease(revisi-ngourjourneys).

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

Thanks!hannahgrossman.com // @landofdoors