Giter Site home page Giter Site logo

name-examination's Introduction

Name Examination

Service BC Name Examination System

Documentation

For further documentation about the project for developers, see the developer documentation.

Setup

Make sure to install the dependencies:

npm install
# or with pnpm:
pnpm install

Setup Environment Variables

cp .env.example .env

You will need to fill in the Firebase variables for the project to run.

Development Server

Start the development server on http://localhost:8080

npm run dev

Testing

npm run test

name-examination's People

Contributors

agehlers avatar argush3 avatar bolyachevets avatar cameron-eyds avatar eportman avatar ericminio avatar eve-git avatar flutistar avatar johnamlane avatar katiemcgoff avatar kialj876 avatar ljtrent avatar madhavkapoor28 avatar megwhetung avatar ozamani9 avatar ozamani9gh avatar perkinss avatar pwei1018 avatar rajandeep98 avatar rarmitag avatar repo-mountie[bot] avatar sameer0422 avatar scottrumsby avatar semmatti avatar severinbeauvais avatar shaangill025 avatar thorwolpert avatar varekboettcher avatar vysakh-menon-aot avatar waltermoar avatar

Stargazers

avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

rarmitag varekboettcher johnamlane katiemcgoff kialj876 ennisd2 ericminio perkinss thorwolpert pwei1018 mengdong19 chrisdmac scottrumsby ljtrent bcdevlucas severinbeauvais lmallika86 jordiwes vysakh-menon-aot cameron-eyds andrepestana-aot argush3 ozamani9 bolyachevets madhavkapoor1 semmatti rajandeep98 eve-git ozamani9gh shaangill025 flutistar sameer0422 rstens stevenc987 eportman

name-examination's Issues

Recruitment for User Research

Email blurb to use in outlook meeting request for internal staff [replace my name and role with yours if you're sending it out]:

I’m Meg Whetung, Service Design Specialist, Government Communications & Public Engagement, reaching out from the project team researching improvements to the Names Examining process. You have been recommended as a valuable person for us to gain insights and feedback from.
We'd like to meet you for an informal interview to hear about your experiences and needs related to Names Examining:

  • Where: at your office (your workstation if possible)
  • What to expect: an interview and observation of how you interact with the names examining application

We hope this proposed time works for you – please let us know ASAP if we need to reschedule for a more convenient time. And if you have any questions about this project please get in touch, we're happy to clarify.

Thank you in advance for your time - we're really looking forward to hearing your perspective and feedback to inform improvements to the names examining application.

Email blurb to use in initial contact email to external stakeholders:

The GCPE-GDX Service Design Team is working in partnership with Service BC to redesign the existing mainframe application for names examination, to create a better user experience for names examiners, leverage modern technology and enhance the client experience.

You’ve been identified as a key person for the research team to talk with to help identify user challenges and find opportunities to improve the names examining process.

We'd like to meet you for an informal interview to hear about your experiences and needs related to Names Examining:

  • Where: at your office (your workstation if possible)
  • What to expect: a one-hour session including an interview and observation of how you interact with the names examining application

We’re scheduling interviews for the week of February 5-9. Please let us know if you are willing to meet with us during this time. We will then follow up with a meeting invite.

Thank you in advance for your time. Your input and feedback are a valuable component of this project. If you have any questions about the project or the interview process, feel free to contact Meg Whetung, Service Designer, at 250-893-1170.

Book AGILE 101 Training

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Find a date to have the Agile 101 training at the lab. This is for the whole team.

Sprint Goal

The AGILE process and methodology supports all sprints.

Acceptance Criteria

-When the date is booked.
-Outlook Invite has been sent to all team members attending.

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Defined 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description
Sprint Goal
Acceptance Criteria
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Complete 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Determine and Document Architecture

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Plan and document architecture

Sprint Goal

Supports all sprints.

Acceptance Criteria
  • Varek approves
  • Draft a document in markdown (12 to 20 pages)
    Will include:
  • logical architecture
  • guiding principles
  • technical architecture (pieces of the application)
  • non-functional requirements
  • security
  • application architecture (back-end APIs, RESTful API)
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Defined 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Agile 101 training

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

The team is to have the one day agile 101 orientation to working the lab and become familiar with the agile process, roles and ceremonies.

Sprint Goal

Supports overall goals of becoming AGILE not a single sprint goal.

Acceptance Criteria

-Everyone attends the session who has not attended it before.

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Defined 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Create Research Plan Document

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Turn Research plan canvas into a document.

Sprint Goal
Acceptance Criteria
  • Word doc with all of the sections from the Research Plan Canvas, for future reference re: research approach taken for this project
  • detail all research activities done to date as well as those planned for future stages
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Complete 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Document the Way the Team Will Work

Document the principle that the team will determine how to proceed and communicate to executive under the premise that we will continue until such time the executive determine we must make a change.

STRA

For the project.

Complete User Research Analysis

Review the user research and come up with some conclusion that will drive the design of the UI and business requirements.

Book Three Sessions with Tim

Book three half day sessions with Tim to interview him to gather valuable names examination knowledge and workflow.

Name Request Screen Design

Epic

Detailed Description

As an examiner I want to be able to see all name request information in an organized manner so that I can assess the next steps to resolve the request..

Inputs
Outputs
Impacts
Users
Epic Definition of Done (any pipleine)
  • Detailed Description*
  • Rough Inputs*
  • Rough Outputs*
  • Impacts
  • Users
  • Priority Label
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application

Story

User Story (As a I want a so that .)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (*-Mandatory to add to the Backlog, **-Mandatory to add to the Sprint Backlog)
  • User Story*
  • Priority Label*
  • Story Label*
  • Linked EPIC*
  • Linked Scenarios**
  • Inputs(Data)*
  • Outputs(Data)*
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN ... AND ... WHEN ... THEN ...)
Definition of Done (*-Mandatory to add to the Backlog, **-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code**
  • Estimate**
  • Priority Label*
  • Scenario Label*
  • Assignee**
  • Linked Story*

Task(Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description
Sprint Goal
Acceptance Criteria
Definition of Done (*-Mandatory to add to the Backlog, **-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Complete
  • Estimate
  • Priority Label
  • Task Label
  • Assignee
  • Sprint Goal (in line with the goal of the sprint)

PIA

PIA for the project.

Define Team principles and Document

Collaborate as a team to develop a list of guiding principles for the names examination project. Print and post principles in the lab as well as upload team Principles document to SharePoint and store on GitHub repo.

Servive Design 101

Conduct a service design 101 workshop to orient the team to service design.

Set up Dev to QA CI/CD Pipeline

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Set up Jenkins pipeline

Sprint Goal

Supports the goal to be able to demonstrate development through to TEST deployment on Feb. 15th.

Acceptance Criteria
  • Demonstrate the pipeline with a sample app.
  • Deployment from Dev to Test through to QA is automated
  • includes build of front end, back end, database, tests (unit, BDD, security)
  • the dev team members can make a change and it gets deployed to dev & test
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Defined 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Conduct Research Interviews

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Interview examiners to see how they interact with the system as well as the types of issues they encounter and some of their wish list items and pains to be resolved.

Sprint Goal

Required to complete conduct the opportunities workshop and prepare epics, stories and scenarios for development.

Acceptance Criteria
  • conduct interviews
  • Take notes and record audio/video
  • conduct interview with Jill and Kaine regarding Appeals and legislation/policy.
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Defined 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Define Suggested Developer Desktop

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Define the standard developer desktop and tool suite.

Sprint Goal

Supports the goal to be able to demonstrate development through to TEST deployment on Feb. 15th.

Acceptance Criteria
  • Varek approves
  • Create document in markdown
  • List suggested tools for development and where to locate them
  • Describe setup and configuration of each tool
  • Acceptable formats or link to separate document
  • Sample boilerplate licencing file
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Acceptance Criteria Defined 1️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Task Label 1️⃣
  • Assignee 2️⃣
  • Sprint Goal (in line with the goal of the sprint) 2️⃣

Epic

Detailed Description
Inputs
Outputs
Impacts
Users
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • Detailed Description 1️⃣
  • Rough Inputs 2️⃣
  • Rough Outputs 2️⃣
  • Impacts 2️⃣
  • Users 2️⃣:
  • Priority Label 1️⃣
  • Attached Journey Map(s)
  • Attached Relevant Screen Shots from the Existing Application 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)
Inputs(Data)
Outputs(Data)
User Research Test Results
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • User Story 1️⃣
  • Priority Label 1️⃣
  • Story Label 1️⃣
  • Linked EPIC 2️⃣
  • Linked Scenarios 2️⃣
  • Inputs(Data) 1️⃣
  • Outputs(Data) 1️⃣
  • Attached Sketch/Mock-up
  • User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")
Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)
  • BDD Pseudo-Code 2️⃣
  • Estimate 2️⃣
  • Priority Label 1️⃣
  • Scenario Label 1️⃣
  • Assignee 1️⃣
  • Linked Story 1️⃣

Determine and Build Solution Architecture

Determine the overall architecture and principles and select frameworks, languages and tools for both front-end and back-end development that support the architecture.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.