Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Tree
root@self
spacesCCP
startDepth1

Welcome!

Background:

The Modernization Acceleration team under the common components is relatively new. Arlen started in March 2022 with Joanne, Kaegan, Jacklynn, and Jeijiri joining in June/July 2022.

  • Through some team-forming workshops the team worked out some the why & how of their work together. (Mural board). But it will evolve and change as we work together.

Our Vision is to model sustainable digital transformation across product teams.

Our mission is to work together in ways informed by research to continuously deliver value to people in BC.

Roles

(alphabetical by first name)

Arlen Tees

Product Owner

Victoria

Tue-Thurs in-office

Jacklynn Pham (Deactivated)

UX & Service Design

Vancouver

9-5

Joanne Li (Deactivated)

UX & Service Design

Vancovuer

Monday flex days

Kaegan Mandryk

Full Stack Developer

Victoria

Monday flex days

Tejiri Emuveyan (Deactivated)

Scrum Master

Where we communicate:

Besides Confluence

  • By default, discord #mod-acc-general channel for general chat

  • Standups 9:30 daily

  • Jira board

Tools

  • Sharepoint folder 🔐

  • Mural Room

  • BC Gov RocketChat #common-components and #nr-common-services-showcase channels
    Panel
    bgColor#F4F5F7

    CHEFS = Common HostEd Form Service

    CHEFS Red TeamClient-focused. Responds to reported issues, improves and refines existing features.

    CHEFS Blue Team Future-focused. Research and Development. Explores and builds new features to extend the capabilities of Chefs.


    CHEFS Team Wish List

    We wish CHEFS would…

    Auto/Incremental Save if I want, with option to only save manually if preferred

    Status
    colourGreen
    titleYES
    & blocked

    Wish in-product and ex-product documentation/help was easier to find, navigate and generally be useful

    Status
    colourGreen
    titleYES
    ? ChatBot, Proactive Help

    Wish CHEFS had fewer ingress channels for users to ask for support (and those channels were searchable)

    Status
    colourYellow
    titleMAYBE
    need primacy/SLA of a channel to be obvious by experience & declaration (Bhuvanesh Pattanashetti (Unlicensed) agrees!)

    Wish components were laid out in a more user-centric / task oriented manner

    Status
    colourYellow
    titleMAYBE
    as long as the re-org is not disruptive (have two order options: alphabetical; easy mode)

    Wish CHEFS was more common-sense regarding the UX

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish CHEFS integrated into PayBC to make it easy to add a “Pay Now” button

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish CHEFS was more modular / loosely-coupled / ‘componentized’ / re-usable

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish CHEFS could accept input from outside of CHEFS

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish it had an events Notification System

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish it could be embedded into other web pages (in a seamless way)

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish it had server-sided form validation

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish it had pagination throughout the site

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish it had an “easy” mode for new users (and could easily be promoted to an ‘Advanced’ mode)

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Wish it were easier to edit forms without so many versions being created and that the upfront question / config were less heavy weight

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Had less counter-intuitive moments in the UX (e.g.: more appropriate icons, better precedence between “save” / “submit”)

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Would give me the SQL to create the database to store the form data

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Had more filtering options on “My Forms” (by date, etc)

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Notification indicator on the dashboard for submissions / tagged as reviewer / etc.

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Better documented and consistent API

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Had a ‘Shared With Me’ folder (or section), and a ‘My Own Forms’ folder (or section)… How can people manage their various forms and know which are which?

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Can we have a “Try It Out” Button or space where we can have a POC or test model running for people to try the tech in a safe, non public way.. to see how they’re using or IF they’re using it.

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Can we have an ‘Events notification System’? Where people can opt-in for notifications for particular ‘events’ or part of a form?

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Can we do specific and tailored components and libraries for each ministry? ie: Tailored headings / footers

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Can we have a better filtering option in search under My Forms? e.g.: by date.. name… ministry?

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    How can we let folks know there have been updates made, or new changes added, to a specific feature? Could be a notification they can check at their convenience as opposed to a pop up.

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    If a feature is in testing or beta, how do we let people know when it's out of testing and official? A badge, notification, colour change, state change?

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE

    Can we let people know, when they’re using a specific feature a lot, our AI (or a suggestion) pops up and says “Hey I see you use this feature a lot, there is another feature you may like as well… here it is”

    Status
    colourGreen
    titleYES
    Status
    colourRed
    titleNO
    Status
    colourYellow
    titleMAYBE