Thread:Sections that make up a charter (4)

1.	We have a statement of Aims and objectives -- so that's covered (Great.)

2.	We have the roles of convenor specified including the option to co-opt co-convenor(s). By nature wiki's are self-organising. For example -- you are not listed as a participant of this group, but your inputs are contributing to the refinement and quality of this group :-) (Perhaps this is an issue of semantics, but if “convenor” means one who facilitates the process of achieving group goals, then fine. At first I took the term “convenor” to mean simply one who assembles meetings. I think this facet of a charter is essential because without it, the workgroup is more likely to work in a less-productive way.

3.	mmmm -- yes I think we need to be more focused on the listing of participant skills as they pertain to the task of the workgroup. Perhaps the subheading of required skills should be placed before the listing of participants? (Ok, but I think we should focus on articulating the skills needed to achieve the objectives first and then simply have members sign up if they feel they have or wish to develop those skills. I don´t feel that including the experience/skills of each member in the charter is a material factor in whether group objectives are met.  If someone wants to know the background of the members, they go to their respective user page.)

4.	As an open community I'm not sure whether we should go down the path of defining categories of members -- this risks excluding the range of volunteers on which our community depends. Ultimately --- its the quality of the outputs which count, not the qualifications of the participating members. Here I see that the Community Council has a responsibility in assessing whether policy guidelines are logical, will contribute to the development of WE taking into account the skills and experience of the workgroup participants. If the proposed guidelines are of poor quality they should be referred back to the work group. (I agree, this facet could probably be removed.)

5.	We have a section which considers resources -- so that's covered (ok)

6.	Regarding timelines -- I think milestones and corresponding dates should be specified in the charter. These time frames need to be determined by the workgroup taking into account the scheduled meeting dates of Council. (Ok, just to clarify though…I´m proposing a charter framework that can be used for all types of WGs. When you mention “Council”, are you referring to all types of WGs?)

7.	Regarding the questions of workgroup process -- I think the workgroup should decide these parameters -- After all the work group is responsible for getting the work done :-) (Exactly, that’s why I´m advocating that it be part of the charter. What I´m proposing is not that we develop one particular charter that is to be applied by all, only the sections of the charter (i.e., objectives, workgroup facilitator(s), skills/experience that will contribute to achieving objectives, resources required, boundaries, process, resolving conflict, project plan, and evaluation). The point is that each workgroup is expected to fill out this (or some other) format with the hopes of achieving a greater level of success.

8.	Securing equal commitment -- well that depends on the individuals involved -- wiki's typically rely on the efforts of volunteers and its been my experience in WikiEducator that the majority of participants act in good faith in the interests of the project. (I agree, but I think articulating this within the charter and within the context of meeting particular objectives promotes a higher level of obligation and communication on the part of its members. If I enter into a new workgroup and I look at their commitment statements I have a good feeling as to whether I would like to be a part of that WG or not.  It’s not a contract, it’s just communicating one’s own commitment level to the group.  It also helps in addressing group expectations that if aren´t met later on, can cause conflict.) – segue…

9.	Resolving conflict --- the WP guidelines on consensus provide a solid foundation to work from --- that said, I think that we should think about the refinements that are necessary and appropriate for our community. (I agree, and perhaps this section could include a link to the WP guidelines. But there is something about having members communicate how they will resolve conflict before the conflict exists.  We can just tell members to read the guidelines, but I don´t think it carries the same weight or importance.)

10.	Yip -- we need to work on developing a clear project plan with corresponding milestones and ideally specify this in the guidelines. I think that it’s also important to think about reasonable and achievable targets. This relates to your earlier comment about the ability of members to contribute. (Yes, it’s related but this section is more specific, as when teams use a Gantt chart to organize work. And again, I´m only proposing that this be a section in the charter where group members decide themselves)

11.	Evaluation and reflection is very important -- I think we have this heading, but haven't spent time populating this section yet. (ok. Probably in this same section would include the process of how to update the charter itself as well.)

Again, my main point here is that we reach a consensus on a common charter framework that this and all subsequent workgroups are to follow. Each group may populate their respective charters in different ways, but that each section should be important enough to make it a requirement to be filled out or included as a link.