Create a Mock Video to instruct common kanban tagging mistake

[pawan92]

Overview

We need a mock video of a person creating an issue and assigning the wrong tags.

More detail

According to the "How to use the Kanban board document", adding the front end tag to an issue because it will eventually need front end support is not the correct way to use a tag. Instead, the tag should be assigned once it is at that stage. This is helpful so that issues can be filtered and assigned quickly & accurately

Action Items

• Review "Common Kanban mistakes" in this document which this comment is addressing.
• Create a video of making an issue (using template below)
  • Add issue to the project board
  • Add labels to the issue in the video
    • p-feature label (p-feature: SDG page)
    • Size label (size: 1pt)
    • and all role labels (which is a no-no) and then reducing back to just the first role label required in the fake issue (role: product).
• Adapt cover page from Guide template to coverpage for video.
  • Get Bonnie to add you to the Guides Team figma
    • Use Guides team figma to store the coverpage
  • Add to video
  • Review with Product

Resources/Instructions

Text to copy for when you are writing your mock issue

### Overview
Create SDG page to be added to Hack for La website

### Action Items
- [ ] Product
   - [ ] ideate
   - [ ] define feature requirements
   - [ ]  make issues for UI/Development
      - [ ] Design
        - [ ] design the mockup
        - [ ] get feedback from Product
     - [ ] Front-end
        - [ ] develop according to Figma

### Resources
[Figma File](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website)

• Issue labels guidance google drive folder

[kristine-eudey]

I am self assigning this issue. ETA is Tuesday 10/26.

[nathan944]

Progress: First mock video draft is completed, now it only needs revision
Blockers: None
Availability: 12 hours this coming week
ETA: Sunday 25/22

[phuonguvan]

Johnathan's Video
This is for review with Bonnie so no further comments need to be placed.

[ExperimentsInHonesty]

Notes for changes to video

• Start the video with a Title page (instead of explaining)
• Don't use dark mode
• Use the regular issue creation tool, not this form based one
• Then paste in what you want to say in each section (have the part you want to copy off screen so it does not show up when you go to cut and paste)
• add the issue to the project board after you submit

[nathan944]

Progress: Third mock video draft is completed after feedback from the team was given and ready for revision
Blockers: None
Availability: 12 hours this coming week
ETA: Sunday 27/22

[phuonguvan]

• ask if we're supposed to use the cover page
• explain that frontend are developers
• explain that UI is designer
• copy the fixed spelling
• click submit the issue
• circle the roles (ex. product, UI, dev) for each time you're trying to explain the labeling of the correct roles

[nathan944]

Progress: Script completed, recording and editing need to be taken care of
Blockers: None
Availability: 2 hours this coming week
ETA: Sunday (9/4/22)

[bishrfaisal]

Please provide update

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.