Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Meet employee/contractor in lobby. Bring access card form and get contractor’s ID created.

  • Take employee/contractor to Service Kiosk to pick up equipment.

  • Take contractor to his/her desk then introduce the employee/contractor to his/her “buddy”.

  • Buddies should help employee/contractor install any tools/products needed for development

    • Install from L:/12i/Developer_Software/SQL Navigator 6.4

    • Install from L:/12i/Developer_Software/Putty

    • Install from L:/12i/Developer_Software/Surround SCM Client (Seapine Software)

    • Install from L:/12i/Developer_Software Workflow Builder

    • Install from L:/12i/Developer_Software BI Publisher

  • Buddies should help the employee/contractor access:

    • DSD-Finance Confluence pages

    • through Confluence access Oracle Applications On-Line Documentation

    • Azure DevOps

    • Install and use MS Teams

    • Access Oracle Applications Software Development Environment

      • Query up purchase order T8080-190820

      • Navigate to the Distributions screen and provide an explanation of the financial distribution; specifically responsibility centre, line object, PI code, and allotment.

    • Load up Business Objects and run a GL Account Analysis by RC and Project for RC 1873 and project 65AA.

    • Load up SQL Navigator in the Oracle Applications Development environment and run the following SQL:

      • select count(*) from GL_CODE_COMBINATIONS;

    • Load up SMGS and access incident IM310120.

  • Introduce the employee/contractor to the team he/she will be working with at DSD-Finance

  • employee/contractor should be made aware of Fire/Evacuation Procedures

  • Contractor should be made aware of guidelines/process for leave and absences. Note: contractors are not paid for any leave and are not permitted to work from home (exceptions to this rule will be up to manager’s discretion).

  • Employee/contractor should be made aware of DSD-Finance employees and management contact names, numbers and e-mail addresses. Names of Importance can be found in the following DSD Hierarchy chart:

  • Employee/contractor should be told who to contact in case of emergency or issues that come up: Michel Brault RC Manager Applications Finance

  • Make sure employee/contractor has access to Policy on Information Management. All documents regarding Transport Canada Business are to be signed into RDIMS.

https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12742

  • Make sure employee/contractor has access to Transport Canada Policy on the Use of Electronic Networks RDIMS 8023159.

  • Make sure employee/contractor has access to Transport Canada Directive for System Development Life Cycle SDLC Methodology.

http://mytc.tc.gc.ca/tc-directive-on-system-development-life-cycle-sdlc-methodology-4266.html

  • Make sure employee/contractor has access to Organizational Chart Finance and Administration RDIMS 15193033.

  • Make sure employee/contractor has access to Oracle ERP User Manual System and Business Processes TP11906:

http://mytc.tc.gc.ca/tp-11906-oracle-erp-user-manual-system-and-business-processes-2225.html

  • Make sure employee/contractor has access to Financial Policy and PRocedures Manual TP117:

http://mytc.tc.gc.ca/tp-117-financial-policy-and-procedures-manual-2082.html

First Week

  • Employee/Contractor should continue to shadow a “buddy” for the first week. Focus should be on showing the employee/contractor the common tools and procedures used in DSD-Finance for application development and support.

  • One of DSD-Finance’s scrum masters should meet with the employee/contractor to give an overview of Scrum/Agile and how we work at DSD-Finance including a tutorial on creating and using PBI’s and tasks in DevOps.

  • Buddy should focus on showing the employee/contractor the tools and procedures used to work, including proper use of SMGS, DevOps (repos), proper coding standards, push and pull requests from Git, and how code reviews are done.

  • Proper use of databases and queries should be demonstrated to the employee/contractor with appropriate guidelines to prevent accidents from happening.

  • By the end of the first week, the employee/contractor should be able to be given a PBI, break it down into tasks, complete development, and submit for code review. In the case of a DATA fix, the contractor should be able to identify how the work was done and show that due diligence was followed in resolving the issue.

...