GitHub Project Roles & Responsibilities

Roles & Responsibilities

Table of Contents
  • Introduction
  • Project Team Responsibilities
    • All team members with GitHub access
    • Creative directors
    • Designers
    • Developers
    • Project Managers
    • Content and SEO Team Members
    • Account Management, Strategy, and Analytics Team members

Introduction

The roles & responsibilities outlined here are specifically related to how we work together in GitHub, separate from the Project Process & Project Team Responsibilities.

All team members with GitHub Access

  • Can create or modify issues during a project. See GitHub and Smartsheet Workflow for details on common ways the team does this by project phase.
    • This includes making subtasks for yourself as a contributor.
  • Remember to alert the project manager and creative director if it is a new or unplanned change that may affect the scope of the project.

Creative Directors

  • Ensure the Github Project board is set up and maintained by the team throughout the entirety of the project
  • Guide the work from a global creative and technical perspective, including:
    • Determining repository direction in coordination with team:
      • Whether to create a new theme, or revise current theme
      • Responsive Framework version, if applicable (2 or 3)
    • Ensuring the GitHub Repository is created, either by themselves or a developer
    • Ensuring the GitHub Project is configured correctly
    • Leading the set up of GitHub Issues from the estimation sheet
      • Cloning default issues from ID Github setup repo
      • Creating Feature issues for issues requiring discussion or custom development
    • Ensuring the GitHub workflow follows the established process, including that team members have added required information to issues
    • Managing assignment of issues to sprints and releases throughout the project
    • Maintaining a vision for the project, and assisting in decision-making related to that vision
    • Answering questions and providing review and feedback as needed to empower designers and developers in creating design and technical decisions

 Designers

  • Maintain and guide the specifics of the work from a detailed design perspective in alignment with project goals, including:
    • Creating GitHub issues
      • Child issues of Features with custom development
      • Any remaining items on the estimation sheet not covered by the default issues and the previous bullet
    • Documenting business and front end requirements
    • Managing issues on the Current Sprint Board
      • Moving cards between columns as work is begun, reviewed, and completed
      • Updating labels and assignments
    • Communicating with the developer and creative director about an issue in the comments
    • Documenting decisions made (such as from comments or in meetings) in the Issue Description

 Developers

  • Maintain and guide the specifics of the work from a detailed technical perspective in alignment with project goals, including:
    • Creating GitHub issues
      • Child issues of Features with custom development
      • Any remaining items on the estimation sheet not covered by the default issues and the previous bullet
    • Documenting technical and back end requirements and decisions (how something should be built – this is determined during estimation meetings)
    • Managing issues on the Current Sprint Board
      • Moving cards between columns as work is begun, reviewed, and completed
      • Updating labels and assignments
    • Communicating with the designer and creative director about an issue in the comments
    • Documenting decisions made (such as from comments or in meetings) in the Issue Description

Project Managers

  • Guide the work from a global timeline and resourcing perspective, including:
    • Using GitHub to view the current sprint board and confirm:
      • Understanding of functionality
      • Assignments
      • Status
    • Developing Smartsheet Project Schedule using planned releases
    • Creating Smartsheet Project Backlog using estimation sheet details

Content and SEO Team Members

  • Can be given access to GitHub when needed
  • May need to review requirements for certain functionality

Account Management, Strategy, and Analytics Team members

  • Do not require access to GitHub
  • Work directly with project managers and creative directors to understand particulars of implementation

 

      Project Meeting Structure and Attendees

      See GitHub & Smartsheets Workflow.