Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »

Statement of work

Working on the Transport Canada Security Information System (TSIS 2.0), the Technical Writer Level 3 responsibilities will include create and maintain key documents such as  procedures, forms, standard operating procedures and technical information in English and French. Working in conjunction with the stakeholders (e.g., product owners, end users), the technical writer, will strong organizational skills and ability to quickly learn new subject matter to create and maintain manuals and technical documents. This role requires someone who can be adaptable without sacrificing value. You will be required to quickly acclimate and learn new subject matter to accurately communicate information into policies, procedures and manuals with a strong focus on document that are easy to users to understand

Responsibilities of the Technical Writer may include but are not limited to:

  • Create and maintain all documents including procedures, forms, standard operating procedures and technical information in English and French for the TSIS 2.0 project

  • Assist other member of the team with creating and maintaining user documents e.g., manuals, standard operating procedures and technical information, .

  • Maintain and manage the technical library, including, updates and revisions

  • Review and edit business documents, memos and other communications for consistency and quality

  • Prepare, review, revise, and maintain technical documents, including software and systems engineering, system operations, testing, and user documentation

  • In collaboration with the subject matter experts (SMEs) e.g., product owners, inspectors, work with to produce high-quality documentation that is clear, concise, accurate and consistent

  • Keeping Product Owners apprised of status and getting their feedback to incorporate into current and future documents.

  • Other activities needed by the project

  • Collaborate, mentor and coach the Product Owner team in developing quality standard documentations.

The Technical Writer deliverables may include …. but are not limited to:

  • Produce high quality Regulatory Oversight Management (ROM) user manuals/user guides in both English and French

  • Develop documents including procedures, forms, standard operating procedures (SOPs), communications and technical information

  • Maintain and manage the technical library, including, updates and revisions.

  • Regularly contribute to team meeting such as scrum event, committees to gather information, understand environment so better create documents

  • Other documentations required by the project

Before Start Date

Team Lead

Scrum Master

  • Request User Account
  • Request IT Equipment
    1. Standard equipment is a tablet.
    2. Mouse, keyboard, bag, lock and docking station can be requested without additional cost.
    3. Employees can request 2 external monitors.
  • Request/Add DevOps Access

  • Invite to Scrum events (as applicable)
    • Daily Standup
    • Requirements gathering/discovery and alignment
    • Refinement
    • Sprint Review
    • Sprint Retrospective
    • Planning
  • Add to Microsoft Teams
    1. TSIS 2.0 Channel
    2. TSIS Project Team Chat Group

After Start Date

Team Lead

Product Owner

New Employee/Contractor

  • Request PS / BA tools (make request to Samantha Tim for financial code / RC code)
    • Figma
    • Lucid (?) - used by the Product Owner
    • Balsamic (question)
    • SnagIT
  • Provide introduction to RDIMS

Scrum Master

  • Provide an overview of scrum events and answer questions as to how events are run in TSIS 2.0 and the role of the Product Strategist / BA Reference Guide: Scrum
    • Daily Standup (optional)
    • Retrospective
    • Planning
    • Review
    • Refinement
    • Requirements gathering/discovery and alignment

Items in bold are to be actioned soonest

  • Product Owners meet with Tech Writer to bring up to date on their area; and, talk of ways of working well together
    • Michael Dunning(AvSec)
    • Jeremie Venne (ISSO)

Confirm access to the following:

to be updated:

  • Provide overview of upcoming UX features/ capabilities at sprint review
  • Set up a meeting with the dev team on how UX and developer work together
    • Joelah or Stephen to set up this meeting
  • Set up meeting with ISSO end users - facilitated with the POs
    • Invite to exiting meeting
  • Set up meeting with AvSec send users - facilitated with the POs
    • Invite to exiting meeting
  • Confirm access to Figma
  • Confirms receipt of instructions for setting up Figma account.
  • Confirms understanding that he will share Figma files as 'view only' to avoid Samantha Tim getting charged for additional licenses.

  • Confirm access completion of
    • myKEY
    • GCSRA

Documents

RDIMS

Aviation Security - Passenger Protect Program (PPP) - User Guide

16855856

Aviation Security International - User Guide

18012203

ISSO

RDIMS User Guide

5740317

Key contacts

Role

Michael Dunning

AvSec Product Owner

Jeremie Venne

ISSO Product Owner

  • No labels