Define SDLC Pipeline for the Assets Team

[Bryce13Reid]

Process looks like:

REQUIREMENTS

• Colin captures Business Stakeholder requests in Zenhub
• Colin writes short three-word summary user story (Placeholder for a future conversation)
• PO priortizes the story in collaboration with the team (Refinement meetings)
• For priority stories, Colin reviews BC Online, Regs, and other documentation related to the story
• Colin meets with Barb to establish how the current Green Screen and BCOL processes work
• Colin drafts the user story
  • Include form field validation
  • Include Questions or Positions regarding direction based on the regs
• Maybe review draft story with Kevin (If it's complicated)
• Colin reviews the story with Liv, Justin and Sandra to discuss ROI for excluding or including certain system behaviour
• Document the solution direction (behaviour in the story)
• If Sandra didn't attend initial ROI session, Colin reviews the solution direction with Sandra
• If there's reg impact Sandra accepts the story knowing/accepting the risk associated with the Regs
• Colin(Accountable), documents the reg changes in the official legislative track documentation (TBD)

  WIREFRAMES

• Liv Creates a wireframe version 1 (With support of Janis and Barb)
• Colin, Walter, or Bryan, or :star: Janis Liv (TBD) collaborates with Liv and UI devs to establish common components used :star:by other teams.
• Liv/Janis reviews draft wireframe version 2 with Sandra, Kevin, and dev/test team members for team feedback on Effort/Value
• Kevin acknowledges Reg change is required and double checks Legislative Track document is reflective
• Liv/Janis posts wireframes requesting feedback from Scott and Jeremy, or attends UX meeting to request feedback
  • Purpose is two-fold 1. solicit idea feedback 2. solicit common component(vuetify) and/or design(css) reuse
• Colin captures applicable feedback in the User Story
• Liv/Janis updates low res wireframe version 3
• TBD screen captures existing layout and design on coop (entities) or bc reg account(relationships) team's pages.
  • TBD annotates sections to be used in PPR design.
  • TBD includes URL to pages and makes sure username and passwords are available so the developer can easily navigate to investigate CSS
  • TBD may be Liv, Colin, or Janis
  • If existing design does not exist then go to DESIGN

    DESIGN

• TBD Provides Designs for wireframes
  • Prototype UI including CSS is ideal Actual approach is TBD

    DEVELOPMENT

    TEST

    CLOSE

[colinanderson-cgi]

Looks good

[Bryce13Reid]

• [ ] Add stakeholder engagement