Communication

Owned by Former user (Deleted)
Last updated: Jun 01, 2007Version comment
2 min read

Communication

Summary

  • Keeping the Sakai community and each other informed of our ongoing activities and plans.
    • Response rate poor on keeping PC pages in your spaces current
      • Already reduced it to a single "update" from both a "status" and a "plans" view.
    • How can we better capture this information in a timely manner?
    • How can we better balance the need for some of us to work "privately" with open communication with our colleagues?
  • Is the Requirements Process/Jira Voting working for communicating community priorities and project team priority setting?

Requirements Process/Jira Voting

Email:

One of the sub-topics for discussion at the Amsterdam Project Coordination meeting – under improving Community-Project Team communication – is how to better connect and support communication of the desires of the Sakai Community and the setting of design and development priorities by the Project Teams. Currently we have both the Requirements Poll and Jira Voting as processes for the community to prioritize their input (and, to communicate back to the community, you can comment on the appropriate issues in Jira; for example, why you might choose not to work on something, or to let the community know you are going work on something.) As Project Leads, I would like to get your opinion on how you utilize these processes, and if they need improvement.

Poll Results:

  • Does your Project Team review the Requirements Poll results when they are publicized?
  • Does your Project Team make use of the Requirements Poll results in setting its priorities? If so, how? (Are they given equal weight as your local priorities?) If not, why not? (Are you too heads-down addressing local needs to be able to consider community needs?)
  • Does your Project Team periodically review the vote totals on Jira issues? If so, how often?
  • Does your Project Team make use of the vote totals for issues in Jira in setting its priorities? If so, how? If not, why not?
  • How does your Project Team determine the overall priorities for work on a given release?
  • If we opted to support only one of the above approaches, which would you prefer and why?
  • Is there a different process you would prefer to use for gathering and factoring community input into the design and development of Sakai?

Strawman Proposals

  • Other ideas for collecting and sharing Project Teams' status and planning informaiton with the community?