This document outlines the roles/responsibilities for the Technical Committee coordination team, Testing team, Building Block leads, and software development team. It also outlines the standing meetings that are scheduled for those GovStack team members.
Roles and Responsibilities
Technical Committee Coordination Team
Coordinate work and oversee Jira backlog for the Technical Committee/cross-cutting work, as well as supporting BB leads in managing their Jira backlog
Provide support and allocate technical resources to BB groups
Attend TC meetings (weekly) and Sprint review/retro meetings (every other week)
Building Block Leads
Coordinate the development of BB specification documents
Manage the Jira backlog as well as writing and prioritizing tasks to be done by the Building Block team
Work with product committee to link use cases to technical specs and example implementations
Work with testing team on definition of APIs and automated testing processes
Attend TC meetings (weekly) and Sprint review/retro meetings (every other week)
Testing Team
Coordinate the development of automated testing processes to show DPG compliance with BB specifications
Prioritize work for the software development team in the implementation of automated tests
Attend TC meetings (weekly), Sprint planning/backlog grooming (weekly), and Sprint review/retro meetings (every other week)
Software Development Team
Implementation of automated testing platform
Work with BB teams to understand APIs to be tested and support definition of APIs as needed
Attend Sprint planning/backlog grooming (weekly) and Sprint review/retro meetings (every other week)
Meeting Cadence
The following standing meetings are used to coordinate the work of the Technical Committee. Note, the meeting schedule may be changed as needed to best facilitate our work
Technical Committee Meeting: Weekly on Thursdays at 3PM CET (60 minutes, but hold additional time in case needed)
Who: Technical Committee team, Testing team, and Building Block leads. Others may join as they have interest/availability
Focus: This meeting is used to discuss issues related to the GovStack process, technologies, formats of specifications, work of the various BB groups, testing and integration with the GovStack sandbox. Any TC or BB member may suggest agenda items. Esther Ogunjimi will provide agenda for the meeting on Wednesdays. Note: we will no longer do a standup/roundtable from the BB leads at this meeting but focus on specific technical or process issues that need to be discussed.
Sprint Review/Retrospective: Every other week on Fridays and 4PM CET (1 hour)
Who: Technical Committee team, Testing Team, BB leads, and software development team
Focus: This meeting is an opportunity for the BB leads and software development team to provide an update/review on the work that they have done over the past 2 weeks, including any blocking issues (30 minutes). The second half of the meeting will be a retrospective, gathering input from all participants on process improvements and how we can work better.
Sprint Planning/Backlog Grooming: Weekly on Fridays at 2PM CET (1 hour)
Who: Testing Team and Software Development Team
Focus: Every other week, this meeting will focus on backlog grooming for the automated testing process, planning tasks for the software development team. On the opposite weeks, the meeting will be used for sprint planning for the next sprint. Note: BB leads are not required for this meeting - we will reach out to individual BB groups with specific questions
Note: All work is planned using Jira - each Building Block working group has a Jira project and a separate Technical Committee project is used for cross-cutting work.