GitHub Tracker Roles & Responsibilities - PHACDataHub/Wiki GitHub Wiki

Category Role Role Definition
-- Product Owner Develop, communicate and manage product goal. Create and communicate Product Backlog items (This can be done in discussion with the team). Order and prioritize backlog items. Ensure transparency and clarity of Product Backlog. Product Owner will work with the Architects and create Epics in the GitHub repository. Create the required Features belonging to the epics, in discussion with the teams, architects as applicable
-- Scrum Master/Agile Coach Coach team members in self-management. Assist development team focus on creating. Increments adhering to the Definition of Done. Help with removal of impediments impacting Scrum Team’s progress. Enable Scrum events and ensure they are time boxed. Assist Product Owner with Product Backlog management. Facilitate collaborations as requested/needed
Management Director Establishes the corporate view for the data infrastructure for the Agency. Collaborates with Health Canada’s CIO and directs the development and enhancement of the information management/information technology (IM/IT) cloud-based data infrastructure Directs the Data Enablement Division: sets objectives, budgets and work plans; establishes human resources strategies; ensures the development of a learning culture within the Division; manages, assesses performance and determines training required for personnel; directs and controls activities and projects.
Management Manager Responsible for the delivery of the work assigned to the stream. Accepts and approves creation of new Product.
Management Team Lead Responsible for development and delivery of the work assigned to the team. Supervises and motivates the team.
Team Architect Liaising with internal and external entities on best practices. Provide direction on infrastructure and security, provide guidance on security and data framework. Develop, scale and lead best practices in security, privacy respecting back-end development and APIs. Develop and implement a modern, reliable, and flexible infrastructure, with secure network access and secure collaborative storage. Works with the Manager in creating the projects i.e. Epics for the team
Team Developer Plan for the Sprint, create and manage the Sprint Backlog Estimate Tasks, Features Ensure work adheres to Definition of Done Delivers a usable Increment at the end of each Sprint. Developer will create and manage the User Story, in discussion with the dev team, Team Leader, manager, Architects as applicable
Team Operations / Site Reliability Engineering Establish uniformity and precision in data to achieve suitable quality assurance. Provide reports on up-to-date initiatives. Monitor and support team members with GitHub project related questions Aim for continuous improvement via feedback provided from user(s). Reconcile and maintain project tracker database. Create centralized location for FAQs and informative hub. Seek method(ss of automation, if applicable to reduce admin task time. Adhere to ad-hoc requests.

RACI Matrix

Category Director Manager Team Lead Product Owner Architect Team Member Scrum Master/Agile Coach
Approve Product/Service A R C C C C I
Create PBI (Epic, Feature, User Story) I I C R A A I
Maintain GitHub Repository I I C R C C C
Update PBI's I I I C R R I
Manage Sprint Backlog I I C C R R I
Estimate Work Items I I I C R R I
Create & manage Tasks I I I I R R I
Liaise with Other Entities I I R C R C I
Provide Architectural, Security Guidance I C I I R C I

RACI Legend

RACI Role Definition
R = Responsible Does the work to complete the task.
A = Accountable Delegates work and is the the last one to review the task or deliverable before it's deemed complete.
C = Consulted Provides input based on how it will impact their project work or their domain of expertise on the deliverable itself.
I = Informed Needs to be kept in the loop on project progress, rather than roped into details of every deliverable.

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

Under Development

  • This wiki and the documents being developed under it are living documents.
  • They are all pre-decisional.
  • Some of these documents were generated using chatGPT or were developed by other organizations for reuse and adaptation.
  • Some of the documents in this wiki are in early early drafts, they make reference to things that do no exist or to process not yet being used.
  • The Center of practice(COP) is best effort and will be developed iteratively. This includes the technology supporting the COP
  • At the early stages of the COP expect change; short life cycles and rapid changes. Plan accordingly.
  • Stability in the COP will materialize over time.
  • For immediate reference engage your COP support channel, use the documentation as a secondary source.
  • There is reference to the COP and PDCP in the documentation, these are the same entity. We haven't picked a name yet :)

All of the pages in this wiki should be considered draft, underdevelopment and needing review. None of these pages are official documentation. All of the pages are a work in progress and discussion is encouraged via the GitHub issues mechanism.

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

⚠️ **GitHub.com Fallback** ⚠️