I am finding it hard to figure out all the possible project groups that can exist and their purpose.
For example, there are steering groups, reference groups, assurance boards/groups, oversight groups, task and finish groups etc.
I was wondering if there is a list of all the different types of groups that can exist on projects and what the remit should be. I’ve seen a reference group and I think it should be a task and finish group by nature. I just don’t know how I could decide on names without a resource.
This is usually driven by the organization's PM policies and standards - if not, let the governance structure be dictated by the complexity and context of a given project.
Kiron Saving Changes...
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
I fear that if you compiled that list together and published it, many organizations would simply want to add to it. Saving Changes...
Anonymous
Thanks for your response.
My organisation does not have clear conventions for naming groups, I.e when the purpose is ‘x’ the group should be called ‘y’. We have governance processes that we need to follow, but this does not shed light on naming conventions for different groups that sit further down in hierarchy under the executive team (such as reference , working, steering, oversight groups)
So is there not best practice and a list of group / board names and what their role should be?
It would be good to see something that shows a list of group naming conventions and typical function within a governance hierarchy- if such a thing exists... Saving Changes...
Glenn ChundrlekProject Manager| BelcanLoveland, Oh, United States
Perhaps you could try looking at it the other way. What groups are needed? The name should be descriptive of the group's purpose and scope. Don't overthink it. Saving Changes...
Anonymous
Perhaps I can gerting too caught up in names? So Wihin an org, one team might use the term ‘steering group’ wheee another team may use ‘oversight group’ for a group that has the same purpose and scope? Saving Changes...
Orgs usually come up with their own nomenclature. From company to company and org to org, they vary widely. It's often a "branding" thing for managers who want to put their own flavor on things, to rename groups, boards, etc. as they see fit. I myself have been called a PM, Project Technical Leader, Project Integration Manager, Project Engineer, Change Manager, etc. but the work is the same. Saving Changes...
That's like finding a needle in a haystack. A group could be named anything and for any purpose. A lit of groups? Since their naming involves a qualifier (thousands available), try a dictionary ;-) Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Agree with the responses. This is specific to an organization. It can get pretty messy sometimes. Saving Changes...
