Developer Onboarding Docs

Day One

Purpose:

  • Complete new employee onboarding paper work, company policies, and perform account setup for async communication platforms.
  • Introduce frontend developer to ID working process as it relates to SCRUM, digital tools, and GIT and other coding best practices.

Goals Setup the following:

Communication

  • Business Gmail (for Senior level devs.)
    • email
      • signature setup
    • calendar - share with team members
      • used for daily scrum meetings, weekly sprint reviews, quarterly meetings, etc.
    • access to company google drive for
      • IFS Projects (Senior Dev. have access and Senior level Designer)
        • Project one (Intern devs. have access to each project they’re assigned to)
        • Project two
      • Policies ( everyone has access)
  • Slack
    • Channels
      • Project (Intern devs. have access to each project they’re assigned to)
      • Dev. Resources
      • General
      • Random
  • LinkedIn
    • claim your position with IFS

Developer Services

  1. Intern creates Atlassian account for: Bitbucket
    1. Add intern to “interns team” in Bitbucket
    2. Add intern to the specific project team in Bitbucket
    3. Branching permissions and pull request permissions (read and write) Jira a. Add intern to project in Jira

Dev. Resource

  • Dev env. setup
    • Enforce Coding Standards by use of Linter(ESLint)
    • Implement pre-commit hooks
  • Git Best Practices

H.R.

  • setup payroll
  • read and sign company policies
    • NDA
    • Sexual Harassment
    • Online Etique
    • ect.

Front-end

Front-end - Day Seven

Purpose:

  • Have dev perform a dry run of sprints via SCRUM methodology on day two.
  • Explain how we service clients (Research Strategy Design Implementation*) and where their role exist
  • Explain how they will perform in the Implementation phase using SCRUM
  • Explain how they will communicate with fellow coworkers

Goals Complete SCRUM dry run in 7 business days

  • have dev complete dry run that includes submitted deliverables, completing milestones, testing code, understand central points, and communicating with teammates

Activity

  1. Implementation
    1. Design
    2. Build
      1. FE
      2. BE
      3. DevOps (Integrate, Test, Deploy)

2a. Performance Explain how they will perform in this phase using SCRUM and communicate with fellow coworkers, see flow chart. Also, make sure they are familiar with the ATOMIC design workflow.

2b. Tool and Services

  • Git
  • Slack
  • Email
    • calendar invites
  • Adobe XD
  • Google Drive
  • Jira
  • Nightwatch.js

2c. Deliverables (circle)

  • FE
    • Wireframes - HTML
      • test for responsiveness and dimensions
    • Cosmetics - CSS3
      • assets - icons, font family, ect.
      • sizing - REM, EM, ect.
      • pixel concentration per device
    • Functionality - JS
      • 3rd party services

2d. Handoffs (triangle)

  • UX/UI
    • provide FE team with wireframes, cosmetics, and assets
  • BE
    • provide FE with API Services
    • API documentation
  • devOps
    • provide environments to test code

2e. Testing (circle)

- Unit
- Integration
- Usability - QA
- Tools -
    - [Nightwatch.js](https://nightwatchjs.org/)
    - https://www.sitepoint.com/javascript-testing-unit-functional-integratio
  1. Setup the dry run environment

Front-end - Day Thirty

Purpose: Provide intern with a mentor and declare a learning track related to their discipline and dev resources items.

Todo:

  • create a performance review checklist or criteria

Back-end

Back-end - Day Seven

Purpose

  • Have dev perform a dry run of sprints via SCRUM methodology on day two.
  • Explain how we service clients (Research Strategy Design Implementation*) and where their role exist
  • Explain how they will perform in the Implementation phase using SCRUM
  • Explain how they will communicate with fellow teammates

Goals Complete SCRUM dry run in 7 business days

  • have dev complete dry run that includes submitted deliverables, completing milestones, testing code, understand central points, and communicating with teammates

Activity

  1. Implementation
    1. Design
    2. Build
      1. FE
      2. BE
      3. DevOps (Integrate, Test, Deploy)

2a. Performance Explain how they will perform in this phase using SCRUM and communicate with fellow coworkers, see flow chart. Also include the functional and technical SCRUM boards.

2b. Tools and Services

  • Git
    • pull request
  • Slack
  • Email
    • calendar invites
  • Jira

2c. Deliverables (circle)

  • BE
    • API Services
    • API document - Swagger

2d. Testing (square)

- Unit
  1. Setup the dry run environment

Back-end - Day Thirty

Purpose: Provide intern with a mentor and declare a learning track related to their discipline and dev resources items.

Todo:

  • create a performance review checklist or criteria

devOps

devOps - Day Seven

Purpose

  • Have dev perform a dry run of sprints via SCRUM methodology on day two.
  • Explain how we service clients (Research Strategy Design Implementation*) and where their role exist
  • Explain how they will perform in the Implementation phase using SCRUM
  • Explain how they will communicate with fellow teammates

Goals Complete SCRUM dry run in 7 business days

  • have dev complete dry run that includes submitted deliverables, completing milestones, testing code, understand central points, and communicating with teammates

Activity

  1. Implementation
    1. Design
    2. Build
      1. FE
      2. BE
      3. DevOps (Integrate, Test, Deploy)

2a. Performance Explain how they will perform in this phase using SCRUM and communicate with fellow coworkers, see flow chart. Also include the functional and technical SCRUM boards.

2b. Tools and Services

  • Git
    • pull request
  • Slack
  • Email
    • calendar invites
  • Jira
  • AWS

2c. Deliverables (circle)

  • devOps
    • infrastructure (CI/CD)
  • automated scripting follow scripting standards - link
  1. Setup the dry run environment

devOps - Day Thirty

Purpose: Provide intern with a mentor and declare a learning track related to their discipline and dev resources items.

Todo:

  • create a performance review checklist or criteria
Git Standards →