Community collaboration is at the heart of the Foundation and every contribution makes a difference.
FinOps Foundation Working Groups (WGs) are small (think two-pizza team), cross-functional groups of people producing best practices for a specific FinOps capability or challenge. They operate in 6-8 week sprints and have their content published by the FinOps Foundation to contribute towards building the FinOps community, advancing FinOps practitioners in their practice and establishing FinOps best practices and standards.
Yes! Any member of the F2 community can submit an idea for a WG. Ideas will be reviewed and the F2 staff may follow-up with you for more information and to discuss your idea.
Ideas will be reviewed and the F2 staff may follow-up with you for more information and to discuss your idea.
If your idea is selected, then you will…
The fun part begins! As a WG, you all can gather, kick-off and start tackling the WG topic proposed to create a resource for the F2 community. Ideally, you’ll setup a weekly meeting cadence to stay in sync as a team while working on your deliverable for the current sprint.
During your WG sprint, you will..
Once your WG sprint wraps, you will…
No problem! If the project you’re planning to tackle requires multiple sprints, then plan to break it down so that each subsequent WG sprint…
Ultimately the goal is to ensure WGs are setup for success; each sprint should be independent (as possible), produce a helpful deliverable for the F2 community, and avoid scope creep/neverending meetings #gak!
A Working Group is made up of:
|F2 Community Practitioner Lead||at least 1 FinOps community member practitioner that leads the WG; up to a max of 3 community member practitioner leads.|
|F2 Community Contributors||F2 community members participating in the WG; community members can be a mix of practitioner-members, partner-members, vendor-members, and any TAC and GB members|
|F2 Staff Liaison||at least 1 FinOps Foundation staff member liaison for the WG|
|F2 TAC Liaison||at least 1 FinOps Foundation TAC member serving as the primary liaison for the WG|
This role must be held and performed by an active F2 FinOps Practitioner member (up to a max of 3 members). The WG Practitioner Lead(s) organize and lead the WG aligned to the scope and sprint timeline in order to produce the artifacts/resources described by their WG Proposal. This role is expected to chair the WG meetings, set the meeting agenda, capture meeting minutes and track/follow-up on actions captured/resolved. F2 practitioner members can volunteer to be a WG Practitioner Lead, or a practitioner may be nominated to the role by (i) the TAC Liaison and/or (ii) the WG members.
The WG Proposal template is intended to be a relatively short abstract of your idea and the corresponding deliverable the WG is hoping to produce for the F2 community. It consists of 8 sections. The current version of the template can be viewed here.
FinOps Foundation Special Interest Groups (SIGs) represent supplementary communities within the FinOps Foundation that are organized around industry, regions, or other topics of interest related to FinOps. SIGs provide opportunities for practioner connection, exploration of topics, and share knowledge between those involved. SIGs can host meet-ups to encourage members to come together. SIGs can also form their own WGs to create content for their area of interest or regionally adapt FinOps Foundation content their needs (for example: creating non-english content translations).
An Special Interest Group is made up of:
|SIG Owner(s)||at least 1 FinOps Foundation Practitioner member that owns or is working on the corresponding initiatives represented by the SIG; up to a max of 3 community member practitioner leads|
|TAC Contributor(s)||FinOps Foundation TAC non-voting member serving as the primary liaison for the SIG; attends SIG meetings as needed/requested; advises SIG WGs to drive action and engaging internally with community members as a FinOps SME|
|F2 Community||members of the FinOps Foundation community participating on SIG projects; help define SIG roadmap; form WGs and produce deliverables for the SIG|
A SIG Owner is recognized as an expert in the area of interest the SIG is being organized to explore, and for their ability to lead (or co-lead) the SIG to produce a SIG roadmap and the corresponding unbiased outputs. Each SIG can have 1-3 SIG Owners that are responsible for leading the SIG, collecting and compiling topics for their meeting agenda, chairing the meeting, ensuring that quality meeting minutes are published, and follow-up actions tracked and resolved. Additionally, SIG Owners are expected to actively encourage a diverse range of community members to participate as diversity is strongly encouraged within SIGs. A SIG Owner tenure last for 6 months but can be extended.
Yes. A SIG Owner (or designate) is expected to attend the TAC meeting and provide updates on their activities, road map, and resourcing needs
SIGs should only be created in combination with high-demand interest from the community about the intersection of FinOps and another area (like Public Sector, Industry, Policy, etc). A Conversation Space (aka a slack channel) is a great first step to gauge community engagement before creating a SIG.
A Conversation Space is a great first step to gauge community engagement before creating a SIG. SIGs should only be created only in combination with high-demand interest from the community about the intersection of FinOps and another area (Public Sector, Industry, Policy, etc).
As long as the SIG maintains an updated roadmap, is actively working on initiatives, has community engagement, provides updates to the TAC, and is following F2 policy/guidelines then the SIG can remain active indefinitely.
Yes. A SIG can bring forward any resources or deliverables they would like to have considered for publishing to the TAC meeting. the SIG Owner will work with the F2 Objective Group core team towards having the resource approved for publishing to finops.org
A SIG and it’s associated initiatives will be suspended including archiving of any corresponding Slack channel archived when…
If at a later date there is renewed support to reinstate a suspected SIG, the previous initiatives will need to be reviewed/adopted by the newly restarted SIG team.