Reference

Retros

OtherEvergreenPublic
  • Formulary
  • TabsHeader default alignment and text casing
  • Consistent use of the design system / CSS custom properties (variables)
  • More thoughtful typography scale
  • Include RichTextEditor styles for previewing the style
  • Include initial content Container layouts
  • Populate initial content with configured defaults
  • Have sample component reference or style guide
  • Have FRD, project numbers, designs defined and final before starting. Agree upon the Source of Truth to eliminate ambiguity.
  • Understand limitations, constraints, compromises and work-arounds
  • Weekly Fast track style updates very helpful
  • You don’t know what you don’t know.
  • Daily connects and Steve’s JIRA expertise provided needed guidance and management
  • Establish / define layering z-indexing system. Safety bar, modals, absolutely positioned elements/ components
  • Continue to be responsive and welcome all questions, concerns with a focus on the total UX for all.
rowidRow IDIssueDescriptionTypeResolutionPriorityStatusLinkTagsProcess IssueProcess Fix
0MAV-Retro_002Scaling BreakContent was not scaling properly across supported and unsupported device sizesNova FunctionalityRefactor existing scaling script in templateCriticalIn Progresshttps://btsjira.abbvie.com/browse/ISAAP-935Caused by Process
Hack Fix
Product BugReceived input of additional sizes needing to be supported outside of existing support matrixStandardize Support Matrix
1MAV-Retro_003Safety Bar place hold sizeCollapsed Safety bar size check is inconsistently checking and setting before fonts are rendered, causing height discrepancies due to variable line breaksNova FunctionalityPlace font ready checks prior to size check and setCriticalReviewedHack Fix
Product Bug
2MAV-Retro_004Active Navigation ButtonActive highlighting on "Main Navigation" only supports 1:1 relationship. There is business case for there to be multiple slides associated to a top level "main nav" ex. 2 "sibling slides" that are both "safety slides". Safety "main nav" item should be active when a user is on eitherNova FunctionalityCreate the ability to associate slides togetherHighReviewedhttps://btsjira.abbvie.com/browse/ISAAP-933Caused by Process
Hack FixGap Analysis MissImprove Gap Analysis
3MAV-Retro_005Feature Support MissesThere were multiple features that were missed in gap analysis, causing time critical fire drills and downstream impactProcess OptimizationMore in-depth gap analysis as well as earlier POC validation on anything that is agreed to be an "Authoring Workaround"CriticalIn ProgressCaused by ProcessGeneral mishandling of gap analysisBetter standardize Gap Analysis Process
4MAV-Retro_006*Modals Within ModalsThere was a business requirement in which a modal was required to be opened from within a modal and persist the existing modalNova FunctionalityEnhance XF component to allow a modal to be opened from within a modal without closing the existing modal. Triggered 2nd modal should close the existing modal if it is authored as a sibling, otherwise if authored as a child, existing modal should persist and 2nd modal should have relative placement to parent modalMediumJira Tickethttps://btsjira.abbvie.com/browse/ISAAP-907Caused by Process
Hack FixGap was identified, authoring workaround was decided but not POC'd causing last minute hack fixes and workaround codeIf gap is to be addressed through authoring, POC should be completed with ample time to pivot to product update if needed
5MAV-Retro_007Linking to Veeva Approved ISAThere was a business case to provide the ability to link to a Veeva Approved "Flashcard ISA" from a linkNova FunctionalityMediumJira Tickethttps://btsjira.abbvie.com/browse/ISAAP-964Caused by ProcessGap Analysis Miss
6MAV-Retro_008Formulary Print & Email Button segregationThere was and has been a business requirement to be able to separate the formulary print and email buttons from the formulary component itself, allowing for these buttons to be integrated within additional content authored around the Formulary ComponentNova FunctionalityIntroduce additional fields to button and or other linking components to support email and print (partially integrated) as well as a key tie back to the relative formulary componentMediumTo Review
7MAV-Retro_009Design Content Delivery TimelineThe creative handoff timing was very scattered and delayed.Process OptimizationAlign and reinforce handoff timing and downstream impact caused by delays.MediumTo ReviewCaused by ProcessTight deadlines with delayed input handoffs caused scramble to pivot.Better communicate and align where possible realistic turnaround times with delayed handoff impacts considered.
8MAV-Retro_010Source of truth for Design should remain tied to Design SystemDue to scattered and expedited timing, decisions were made at times to go direct to aux styles rather than feed back through the design upon misses or design updatesProcess OptimizationIdentify and update Helium to continue to fill the gaps between exported styles and needed styles.MediumTo ReviewCaused by Process
Product BugAll styles that can be centralized to Design System should be driven from design systemIdentify and update Helium to address gaps discovered
9MAV-Retro_011Support MatrixUpon submission and marketing review it was brought to our attention there may be additional iPad sizes and types that may need supportNova FunctionalityAlign between BCo & ADL on standard support matrixCriticalTo ReviewCaused by ProcessAlignment on iPad size support was unclearStandardize Support Matrix
10MAV-Retro_012Formulary Channel DataChannel Selection for formulary only allowed Commercial, Managed Medicaid, Medicare. Business requirement to support Commercial + HIX, MedicaidNova FunctionalityUpdate available channels to be a config rather than hardcoded optionsHighJira Tickethttps://btsjira.abbvie.com/browse/ISAAP-956Caused by Process
Hotfix(Gap Analysis) Understanding of brand specific channel filtering was not identified ahead of timeClearly define Formulary Channel needs
11MAV-Retro_013Formulary reCaptchaProxy endpoint for Formulary lookup was updated in the admp sites codebase (owner) to require reCaptcha tokenNova FunctionalityADMP Sites reverted code, NOVA POC in progress to pass reCaptchaCriticalIn Progresshttps://btsjira.abbvie.com/browse/ISAAP-951Caused by Process
HotfixADMP Sites updated their code unknown to NOVA to resolve a security flagged issue requiring recaptchaBetter communication on shared platforms, endpoints and systems between teams
12MAV-Retro_014Design Content FormatBase size of design handoff matched no existing ipad sizeProcess OptimizationUpdate mandated base design sizeCriticalTo ReviewCaused by ProcessHanded off design was not to spec for ratio to be developedUpdate standard design ratio to 12.9/13"
13MAV-Retro_015Formulary Email Button not specified to instanceFormulary Email Plans button was sending data from the first Formulary component on the page. In Mavyret's case there were 3 Formularies on the page, needing to operate independentlyNova FunctionalityUpdated to target the relative formulary componentCriticalCompleteHotfix
Product Bug
14MAV-Retro_016Swipe transitions were brokenBy default disable swipe was enabled in veeva meta data, causing ISA to not be able to navigateProcess OptimizationIdentify and standardize when swipe should and should not be disabledLowTo Review
15MAV-Retro_017Tab Container Name Allowing SpacesContainer name authored in Tabs component is used to drive html id of container. If spaces are used technically output is invalid HTMLNova FunctionalityConvert spaces to "_"LowJira Tickethttps://btsjira.abbvie.com/browse/ISAAP-954
16MAV-Retro_018Links were directing to null slidesUpon clicking of links, user was navigated to blank page, due to logic put in around handling pdf links in text componentNova FunctionalityPlaced more checks in so code no longer hits a use case in which redirect url can be nullCriticalCompleteProduct Bug
17MAV-Retro_019Email button template and fragment id requirementsThe handling of the authored template & fragment ids caused a gap in functional support to generic email buttonNova FunctionalityUpdated email button functionality to handle formulary, generic and template configuration optionsCriticalCompleteCaused by Process
Product BugGap Analysis
18MAV-Retro_020