diff --git a/.github/ISSUE_TEMPLATE/contributing.md b/.github/ISSUE_TEMPLATE/contributing.md index c8aa9b00..333b12de 100644 --- a/.github/ISSUE_TEMPLATE/contributing.md +++ b/.github/ISSUE_TEMPLATE/contributing.md @@ -2,8 +2,9 @@ name: Contributing to the design system about: Template for new common component for VA mobile app title: 'Component: [Insert name of component here]' -labels: component-documentation, ux -assignees: +labels: ux +assignees: '' + --- # Contributing to the design system @@ -37,4 +38,4 @@ Include any research you have already conducted, or plan to conduct, on this com Include any existing code. ## Next steps -After filling out the issue template, post in the Design System slack channel to alert the team that you have filled out an issue. The team will reach out to you with any questions, feedback, and next steps. \ No newline at end of file +After filling out the issue template, post in the Design System slack channel to alert the team that you have filled out an issue. The team will reach out to you with any questions, feedback, and next steps. diff --git a/.github/ISSUE_TEMPLATE/epic-ticket.md b/.github/ISSUE_TEMPLATE/epic-ticket.md index 113d48b7..77435f8d 100644 --- a/.github/ISSUE_TEMPLATE/epic-ticket.md +++ b/.github/ISSUE_TEMPLATE/epic-ticket.md @@ -1,22 +1,21 @@ --- name: Epic Ticket about: Template for Mobile Design System Epics -title: "[Epic Title]" +title: DS - [Epic Title] labels: design-system, epic assignees: kellylein --- - - - # Project Status Overview ### Project Objective: - High level description of the project and what we are trying to solve - +### Product Brief: +- [link to GitHub Product Brief] + ### Current Dependencies / Blockers
Blockers @@ -30,23 +29,6 @@ assignees: kellylein
- -### Project Timeline -
-Milestones - -|Step | Timing | -|-------| ---------| -|Sprint 0 - Discovery | | -|Step 1 - Strategy | | -|Step 2 - Design | | -|Step 3 - Building / Implementing | | -| 100% Release | | -|Step 4 - Post Verification| | -
- - - ### Monthly Update for Stakeholders
Updates @@ -59,90 +41,6 @@ assignees: kellylein |Month Year|
-# Detailed Project Scope - -### Problem Statement - -### Current Veteran Experience -
-What the Veteran experiences today and its painpoints - -**Veteran Experience** - -**Veteran Painpoints** - -
- -### Assumptions - -
-Assumptions that need to be true for this project - - 1.) - - 2.) - - 3.) - - -
- -### Risks - -
-Risks identified and accepted by stakeholders - - 1.) - - 2.) - - 3.) - - -
- -### Definition of Done -
-Conditions that must be true in order to consider this project completed - -|Item | Completed | -|-------| ---------| -| | | -| | | - -
- -### Project Scope -
-Items in and out of scope - -|In Scope | Out of Scope| -|-------| ---------| -| | | -| | | - -
- -### Important Project Links -
-Links - -- Github Epic -- Github VA Mobile Page -- - Product Brief -- Product Canvas -- Design - - Discovery - - Mockups - - Final Design - - Figma File -- Research - - Research Plan - - Research Results and Findings --Analytics --Decision Log -
- ### Team Members
@@ -166,164 +64,4 @@ assignees: kellylein - **Mobile Teams that are involved:** Global, Health and Benefits, Design System, QA, API -
- -### OKR and Analytic Metrics -
-Analytic Information - -**What KPIs / OKRS are the focus of this project?** - -1.) - -2.) - -**The link to the project's analytical dashboard** - - - -|What we are measuring | Why | How / Event Name | -|-------| ---------| ----- | -| How will we determine this is a success? | | | -| How will we determine if this is not a success? | | | - -|Analytic Event| What is it measuring | How to use it to measure | -|-------| ---------| ----- | -| | | -| | | - -
- - -### Questions -
-Open Questions - - - How are we measuring success? - - - What is MVP and what is out of scope? - - - Has there been existing research or work done on this project before? - - - Is this work being done within the VA today (ex. web) - -
- -
-Closed Questions - -| Question | Answer | Owner | -|--------|----------|------| -| | | | -| | | | - -
- -### Change / Decision Log - -Product will need to create on in the Github folder and link it here. - - -# Checklist - -
- Toggle Product Checklist - -**Project Kickoff & Requirements Gathering** - - [ ] PM to create new Github epic and fill out accordingly (Type - Epic, Template - Epic Ticket - - [ ] Updated so it is seen in Mobile and External Github Boards - may need to view this epic in Github and not Zenhub - - [ ] PM to create new Github folder for feature or update existing - - [ ] Create a separate document for the project's decision log - link it here - - [ ] Project Kickoff session to review problem statement, Veteran experience, and goals with stakeholders - - [ ] Determine team roles, responsibilities, approvers with stakeholders - - [ ] Determine future cadance reviews with stakeholders - - [ ] Review dependencies - - [ ] Scope finalized or approved by Mobile POs - - [ ] PM to create and/ or link Product Brief - - [ ] Design work to update hi-res internal files - - [ ] Engineering created successful unit tests - - [ ] UX has completed visual QA - - [ ] Accessibility testing has been completed - - [ ] PM fills out and completes Epic's checklists - - [ ] Other: - -
- - -
- Toggle Design/UX Checklist - -- [ ] If QA testing needed, coordinate with QA agent and assign QA agent to the ticket -- [ ] Review problem/opportunity statement -- [ ] Add questions and assumptions to product brief -- [ ] Add research links to product brief -- [ ] Document high-level research/design plans -- [ ] Create lo/hi fi wireframes & user flows if applicable -- [ ] Add links to Epic & applicable GitHub folders -- [ ] Socialize designs -- [ ] Sign off received on finalized design - link to approval -- [ ] Design QA / Visual QA approval -- [ ] If QA testing needed, coordinate with QA agent -- [ ] Component review -- [ ] Accessibility review -- [ ] Design system review -- [ ] Update internal documents -- [ ] Other: - -
- -
- Toggle Content Checklist - -- [ ] If QA testing needed, coordinate with QA agent and assign QA agent to the ticket -- [ ] Review product brief and surface any questions, assumptions & risks -- [ ] Participate in project discovery and kickoff activities/ceremonies -- [ ] Complete comparative analysis/content research activities for net-new content -- [ ] Review current content and determine where app may need to differ and potential improvements to share with web -- [ ] Review past VA research and decisions documentation -- [ ] Support Research & UX Design in research sessions and synthesis -- [ ] Make content recommendations for lo-/hi-fi wireframes in collaboration with UX Design -- [ ] Collaborate with Sitewide Content team for alignment, improvements, and sign-off -- [ ] Participate in FE hand off -- [ ] Complete content QA -- [ ] Other: - -
- -
- Toggle Engineering Checklist - -- [ ] If QA testing needed, coordinate with QA agent and assign QA agent to the ticket -- [ ] Are UI designs/ specs available/ready? If yes, they should be attached to attach specs. (We are assuming the design specs have been approved) -- [ ] Are there any deadlines that need to be met? -- [ ] Do we want to capture analytics for this projects (i.e. update GA, add logs to grafana/datadog etc)?If yes, what metrics would we like to capture? -- [ ] Other: - -
- -
- Toggle QA Checklist - -- [ ] Team PM creates test plan and assigns to Team QA agent- Template: QA Test Plan -- [ ] QA agent to monitor and speak up on QA needs for the project -- [ ] Document decision in the descision log regarding QA -- [ ] Identify test data needs - - [ ] Determine and document test accounts used -- [ ] Test plan creation and resolution -- [ ] Successful testing on all MVP tickets -- [ ] Reviews open bug tickets pre-production -- [ ] Other: - -
- -
- Analytics Checklist - -- [ ] Discussion on what can and can't be measured pre-design -- [ ] Determine what analytics work is included in for MVP -- [ ] Document non-mvp analytic needs in Github -- [ ] Update Analytics section of this epic -- [ ] Determine if analytics can be tested by QA - if so coordinate with QA -- [ ] Other: -
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 786e2fe5..6d4062fb 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,4 +1,3 @@ - @@ -7,9 +6,6 @@ where Issue type = bug, feature, spike, CU (code upkeep), etc.--> '[Issue type]/[Issue #]-[Your name]-[Summary of issue]', where Issue type = bug, feature, spike, CU (code upkeep), etc.--> - -**[Ticket # ](https://github.com/department-of-veterans-affairs/va-mobile-app/issues/# )** - ## Description of Change + - Were there important sources to link? Examples: an open bug with a dependency project, an article of someone else solving the same problem that was partially or wholly copied, external documentation relevant to solution + --> + #### Testing Packages + ### Screenshots/Video + ## Testing