Onboarding Issues

Page Purpose

• Document any issues you have when on-boarding
  • Where is clarity needed in the process
  • Where do we need to add new steps to the process
  • What needs changing in general?

How to get these changes made

• Discuss the issue with co-PMs and make an issue on our project management board to define the problem.
  • This serves 3 purposes: practicing making issues, keeping the PMs on the same page, and tracking updates about our process and why changes were made

Hack For LA's Guide on Creating Issues

How to Document

1. Edit this page and create a section below "Documentation Log" using your name in the h3 tag (### [Your Name]).
2. Make a list of issues describing the problem and where you found it.
   • Please use links wherever you can when referencing pages, information, or documentation
   • Please describe the problem and explain how it can be re-created so that this can easily be fixed and turned into an issue
3. Once you have documented any issues, please contact a PM to have them review your notes and begin implementation
   • The PM may then ask you to practice making issues by converting these problems into issues that can be tracked on the Project Board so you can get acquainted with the process for the future

Documentation Log

Briana

1. As a PM, I need to be trained on how to also onboard other members. There should be documentation on how to add people to different systems.
2. The good first issue for product is just a filter for issues assigned to pm. Is this intentional?
3. It would be helpful to know what to do as a PM on this project.

Vance

1. Github Board unusable. 556 issues in in the done column is the reason. Removing these issues from the board will fix this. No sprint board could handle this.
   • "Done" issues moved to a new project board here
2. I Don't know who to talk to about ops for the site or site deployment.