{"id":1938,"date":"2024-08-10T02:44:36","date_gmt":"2024-08-10T06:44:36","guid":{"rendered":"http:\/\/sites.bu.edu\/marcom-team\/?page_id=1938"},"modified":"2025-09-03T17:02:00","modified_gmt":"2025-09-03T21:02:00","slug":"github-roles-responsibilities","status":"publish","type":"page","link":"https:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/github-smartsheets\/github-roles-responsibilities\/","title":{"rendered":"GitHub Project Roles &#038; Responsibilities"},"content":{"rendered":"<h2><strong>Roles &amp; Responsibilities<\/strong><\/h2>\n<h5><strong>Table of Contents<\/strong><\/h5>\n<ul>\n<li>Introduction<\/li>\n<li>Project Team Responsibilities\n<ul>\n<li>All team members with GitHub access<\/li>\n<li>Creative directors<\/li>\n<li>Designers<\/li>\n<li>Developers<\/li>\n<li>Project Managers<\/li>\n<li>Content and SEO Team Members<\/li>\n<li>Account Management, Strategy, and Analytics Team members<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<hr \/>\n<h2>Introduction<\/h2>\n<p><strong>The roles &amp; responsibilities outlined here are specifically related to how we work together in GitHub<\/strong>, separate from the <a href=\"http:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/project-process-and-project-team-responsibilities\/\">Project Process &amp; Project Team Responsibilities.<\/a><\/p>\n<h2><\/h2>\n<h4><strong>All team members with GitHub Access<\/strong><\/h4>\n<ul>\n<li>Can create or modify issues during a project. See <a href=\"http:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/working-together-to-manage-our-work-github-and-smartsheet\/github-and-smartsheet-workflow\/\">GitHub and Smartsheet Workflow<\/a> for details on common ways the team does this by project phase.\n<ul>\n<li>This includes making subtasks for yourself as a contributor.<\/li>\n<\/ul>\n<\/li>\n<li>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.<\/li>\n<\/ul>\n<hr id=\"toc-creative-directors\" style=\"border: none !important;\" \/>\n<h4><strong>Creative Directors<\/strong><\/h4>\n<ul>\n<li aria-level=\"2\">Ensure the Github Project board is set up and maintained by the team throughout the entirety of the project<\/li>\n<li aria-level=\"2\">Guide the work from a global creative and technical perspective, including:\n<ul>\n<li aria-level=\"3\">Determining repository direction in coordination with team:\n<ul>\n<li>Whether to create a new theme, or revise current theme<\/li>\n<li aria-level=\"3\">Responsive Framework version, if applicable (2 or 3)<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Ensuring the GitHub Repository is created, either by themselves or a developer<\/li>\n<li aria-level=\"3\">Ensuring the GitHub Project is <a href=\"https:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/working-together-to-manage-our-work-github-and-smartsheet\/github-project-configuration\/\">configured correctly<\/a><\/li>\n<li aria-level=\"3\">Leading the set up of GitHub Issues from the estimation sheet\n<ul>\n<li aria-level=\"3\">Cloning default issues from ID Github setup repo<\/li>\n<li aria-level=\"3\">Creating Feature issues for issues requiring discussion or custom development<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Ensuring the GitHub workflow follows <a href=\"https:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/working-together-to-manage-our-work-github-and-smartsheet\/github-and-smartsheet-workflow\/\">the established process<\/a>, including that team members have added required information to issues<\/li>\n<li aria-level=\"3\">Managing assignment of issues to sprints and releases throughout the project<\/li>\n<li aria-level=\"3\">Maintaining a vision for the project, and assisting in decision-making related to that vision<\/li>\n<li aria-level=\"3\">Answering questions and providing review and feedback as needed to empower designers and developers in creating design and technical decisions<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<hr id=\"toc-designers\" style=\"border: none !important;\" \/>\n<h4><strong>\u00a0Designers<\/strong><\/h4>\n<ul>\n<li>Maintain and guide the specifics of the work from a detailed design perspective in alignment with project goals, including:\n<ul>\n<li>Creating GitHub issues\n<ul>\n<li>Child issues of Features with custom development<\/li>\n<li>Any remaining items on the estimation sheet not covered by the default issues and the previous bullet<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Documenting business and front end requirements<\/li>\n<li aria-level=\"3\">Managing issues on the Current Sprint Board\n<ul>\n<li aria-level=\"4\">Moving cards between columns as work is begun, reviewed, and completed<\/li>\n<li aria-level=\"4\">Updating labels and assignments<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Communicating with the developer and creative director about an issue in the comments<\/li>\n<li aria-level=\"3\">Documenting decisions made (such as from comments or in meetings) in the Issue Description<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<hr id=\"toc-developers\" style=\"border: none !important;\" \/>\n<h4><strong>\u00a0Developers<\/strong><\/h4>\n<ul>\n<li aria-level=\"3\">Maintain and guide the specifics of the work from a detailed technical perspective in alignment with project goals, including:\n<ul>\n<li>Creating GitHub issues\n<ul>\n<li>Child issues of Features with custom development<\/li>\n<li>Any remaining items on the estimation sheet not covered by the default issues and the previous bullet<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Documenting technical and back end requirements and decisions (how something should be built &#8211; this is determined during estimation meetings)<\/li>\n<li aria-level=\"3\">Managing issues on the Current Sprint Board\n<ul>\n<li aria-level=\"4\">Moving cards between columns as work is begun, reviewed, and completed<\/li>\n<li aria-level=\"4\">Updating labels and assignments<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Communicating with the designer and creative director about an issue in the comments<\/li>\n<li>Documenting decisions made (such as from comments or in meetings) in the Issue Description<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<hr id=\"toc-project-managers\" style=\"border: none !important;\" \/>\n<h4><strong>Project Managers<\/strong><\/h4>\n<ul>\n<li aria-level=\"3\">Guide the work from a global timeline and resourcing perspective, including:\n<ul>\n<li aria-level=\"3\">Using GitHub to <strong>view<\/strong> the current sprint board and confirm:\n<ul>\n<li aria-level=\"4\">Understanding of functionality<\/li>\n<li aria-level=\"4\">Assignments<\/li>\n<li aria-level=\"4\">Status<\/li>\n<\/ul>\n<\/li>\n<li aria-level=\"3\">Developing Smartsheet Project Schedule using planned releases<\/li>\n<li aria-level=\"3\">Creating Smartsheet Project Backlog using estimation sheet details<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<hr id=\"toc-content-seo\" style=\"border: none !important;\" \/>\n<h4><strong>Content and SEO Team Members<br \/>\n<\/strong><\/h4>\n<ul>\n<li aria-level=\"3\">Can be given access to GitHub when needed<\/li>\n<li aria-level=\"3\">May need to review requirements for certain functionality<\/li>\n<\/ul>\n<hr id=\"toc-others\" style=\"border: none !important;\" \/>\n<h4><strong>Account Management, Strategy, and Analytics Team members<br \/>\n<\/strong><\/h4>\n<ul>\n<li aria-level=\"3\">Do not require access to GitHub<\/li>\n<li aria-level=\"3\">Work directly with project managers and creative directors to understand particulars of implementation<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<ul><\/ul>\n<ul><\/ul>\n<h2><strong>Project Meeting Structure and Attendees<\/strong><\/h2>\n<p>See GitHub &amp; Smartsheets Workflow.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Roles &amp; 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 &amp; responsibilities outlined here are specifically related to how we work together in GitHub, separate from the Project [&hellip;]<\/p>\n","protected":false},"author":12906,"featured_media":0,"parent":1856,"menu_order":10,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/1938"}],"collection":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/users\/12906"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/comments?post=1938"}],"version-history":[{"count":6,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/1938\/revisions"}],"predecessor-version":[{"id":2851,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/1938\/revisions\/2851"}],"up":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/1856"}],"wp:attachment":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/media?parent=1938"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}