Page History

Nicole “Nikki” (HQR/Adhoc)

Currently manage submissions process for HQR, exploratory work.  Problems with nebulous work and putting in to Jira.  Successes: Working on comm why ux work looks and is different.

Problems: tryin to fit in to workflow, advocate to opportunities for HCD to impact highest level, needs to be in the ground floor. Slow progressions tying in high level needs building understanding across all teams. Set up Usability labs within PI planning to showcase what they do.

Content sensitive help content for pages.  Whole team was agile and then safe and then found running to keep up.  Switched to Kanban = taking pressure off = successful. Want to push more ahead faster. Problem: client changes priorities often.

Lovemore (EQRS / Beliese)

Hubstuff for eqrs, trying to envision full vision of project, issues trying to fit into safe environment; dual-tracking (track 2 vision – trying to sell fully featured strategy piece) – need visual to explain.  Communication issues. Need someone at CMS to advocate what we need; formally and informally.

7 HCD projects for PoP involving different folks from initiation, to prototyping to hospice, hospital.  Completed 2 projects last year now turning in ot reality. Prototype and hopefully user testing soon.  Journey maps for OIT.  Deliverables this week.  Nice to see externally customers.

Successfully deployed HARP, account recovery, auth workflows. iQies – scheduling feature, plan and schedule reports in the future. Application built on react, almost mimicking outlook scheduling meetings to be able to schedule date and time to report features.

Upcoming Events

• theiaconference.com  - IA (info Arch) Summit – March 13-17 2019 in Orlando Fl.

Integrating UX into Agile (Discussion)

• Lean UX book – Jeff Gothelf and Eric Ries –

  Who is on product team? QA, UX, PO, ENG, BA?

  • EQRS (Lovemore) – This was us pre-safe, QA, BA, PO.  Now only considered a shared team across 4 or 5 teams, support service so outside sprint teams. Can find things in there and say when UX needs to be involved so include us during weekly backlog refinements /  planning. By doing weekly, shortens feedback loop.  Come in to support initiators.
    
    
  • HQR – 3 UX designers, one ux developer, 4 ux researchers (with AdHoc); Team as a whole interfaces with 12 sprint teams; front end and back end teams. Talking more and more to backend teams.  Things that trickle up that need UX involvement; argues UX provides vision at level and breaks down at user stories. Product visioning first.  MAJOR THINGS: Need for exploratory time. Depends on what we find out to know what can do within 2 weeks.  AND try to guide the vision with the PO.  Part of Backlog refinement.  How wording is written implies how things will be solutioned within the user story; user story for file deletion – so narrowly scoped without thinking how edit or share or post files. Need part of feature intake meetings.
    
    
  • If has UX architect role, can do holistic lens that can have perspective of work and provide holistic connection.  The sooner it happens the better it is.
  • Findings are challenging how legacy has the architecture and concepts.
  • UX workers aren’t supposed to just validate ideas, but imagine how it could be.
  • Set the standard for future ideas.
  • Put up stories in PI planning to see where the user is along the way so others can see what they are working on and how it affects the end users. All about way to frame it.
  • (RF) Artifact of journey map is to show the business how the user connects to the whole picture. Helps to show the value of what we do.
  • Goal to unpack dense info, same info grouped together but relevant, and reorg and devs worried doesn’t fit current data model. Was easier to communicate to dev team, how this is relevant.
  • Itterations are what make it best. Can’t do that if save UX till the end.  Critical path is have customer invlolved.
    
    • What roles make up UX team?
    • Visual Designer, UI Engineer, Usability Reesearcher, Technical Writer, Interaction Designer / Info Architech
      
      
      • Do you support more than one team? What do sprints look like?
      • Research, testing, thought process;  only committing to what we can do.
      • Came up with workflow from early knowledge kickoffs to devs to pick up so can look at and know where they are. (Strategic vs Production = Dual track.)  Reseaarch needs exploratory to know how to formulate strategic visioning. Production: Need Version 1 and Version 2 wireframes.
      • Systemized regular communication with sprint teams. Look at what we’re working on, no pressure; devs get to say what could be a challenges. Apart from normal cadence. Helps devs to avoid Technical Debt – plan 1 point in your sprint planning for that time.

Need point person from each UX Team for PRA.

• December Topic: TBD
• Next Meeting: December 20, 2018