Middlebury

Difference between revisions of "LIS Website"

m
Line 1: Line 1:
This is the space that the LIS Website Team will use for documentation and note taking.
+
<p>This is the space that the LIS&nbsp;Website Team will use for documentation and note taking.
+
</p><p><br /> __TOC__<br />
 
+
</p><p><br />
Here are the some [[LIS Website Resources|resources that we are looking at]].
+
</p>
+
<h2> Team Vision  </h2>
+
<p>We are creating a web site with intuitive navigation, easy access to services and resources, inviting interfaces, and a workflow that allows simple maintenance.
 
+
</p>
 
+
<h2> Meeting&nbsp;Notes  </h2>
 
+
<h3> 2009:&nbsp; June 24  </h3>
__TOC__<br>
+
<p>Present:&nbsp; Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin, Barbara Merz.<br />
+
</p><p><br /> <br />
 
+
</p><p><br /> 1.&nbsp; Questions for the team - Jim and Carrie<br />
 
+
</p><p><br />
 
+
</p>
== Team Vision  ==
+
<ul><li>Jim had some questions about roles and communication methods.&nbsp; He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
 
+
</li></ul>
We are creating a web site with intuitive navigation, easy access to services and resources, inviting interfaces, and a workflow that allows simple maintenance.
+
<ul><li>Carrie shared what she'd done to get caught up on team training.&nbsp; She asks that team members tell her when she does something contrary to what the team learned/agreed to during training.<br />
+
</li></ul>
 
+
<p><br />
<br>
+
</p><p><br /> 2.&nbsp; Decide on a platform to facilitate documentation and communication&nbsp; <br />
<br>
+
</p><p><br />
+
</p>
 
+
<ul><li>What will we use this platform for?&nbsp; Communication within the team and with our users/constituents.
<br>
+
</li></ul>
+
<ul><li>What are our options?&nbsp; Basecamp, Microsoft Project, Groove, MediaWiki, Wordpress, Drupal (not yet)
 
+
</li></ul>
== Meeting&nbsp;Notes  ==
+
<ul><li>We discussed the merits and drawbacks of the options.
 
+
</li></ul>
=== 2009:&nbsp; June 24  ===
+
<ul><li>We decided by majority:&nbsp; At least in the beginning, we will use MediaWiki for meeting notes and documentation, and Wordpress for communication among ourselves and with our users/constituents.&nbsp; We may use email to direct users/constituents (and team members) to Wordpress.&nbsp; We may use email to communicate within the team about mundane or ephemeral matters like absences at meetings.&nbsp; We can revisit this decision in the future by adding it to a meeting agenda.
 
+
</li></ul>
Present:&nbsp; Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin, Barbara Merz.<br>
+
<ul><li>Ian created this Wiki category and our blog (<a href="http://blogs.middlebury.edu/liswebsite/">LIS&nbsp;Website Project</a>).
+
</li></ul>
 
+
<p><br />
<br>
+
</p><p><br /> 3.&nbsp; Team Protocols<br />
<br>
+
</p><p><br />
+
</p>
 
+
<ul><li>Team protocols that were agreed upon during team training were listed:<br />
+
</li></ul>
 
+
<p>a. Meet weekly - adjust frequency as needed if there are no/more agenda items.
+
</p><p><br /> b. Set agenda ahead of time
+
</p><p><br /> c. Shared responsibility to generate agenda items, agenda facilitated by team leader
 
+
</p><p><br /> d. Agenda items will have specific time and sponsor
<br>
+
</p><p><br /> e. Time keeper
+
</p><p><br /> f. Note taker-- I think this responsibility should rotate alphabetically.&nbsp; If someone can't take notes when it's his/her turn then that person can ask for a substitute.&nbsp; <a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 13:13, 30 June 2009 (UTC)<br />
 
+
</p><p><br />
+
</p><p>f1. Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting. [Barbara 6/26]
  1.&nbsp; Questions for the team - Jim and Carrie
+
</p><p><br /> g. Use shared platform for communication and development of documentation
+
</p><p><br /> h. Timely (define?) posting of meeting notes
+
</p><p><br /> i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda
 
+
</p><p><br /> j. If unable to attend, responsible for getting caught up
<br>
+
</p><p><br /> k. Open honest dialogue (with tact)
+
</p><p><br /> l. Simple majority rules
 
+
</p><p><br /> m. Agreement - to ensure success (from training)
+
</p><p><br /> n. Authentic and candid dialogue
+
</p><p><br /> o. Honest - with tact
+
</p><p><br /> p. Open to others - come to agreement
 
+
</p><p><br /> q. Make the decision and move on - or fix it and move on
<br>
+
</p><p><br /> r. Depersonalize and on board
+
</p><p><br /> s. Participate, engage, share point of view 1X
 
+
</p><p><br /> t. Focus on and value time over story
<br>
+
</p><p><br /> u. Informed, fast decisions
+
</p><p><br /> v. Confidential
 
+
</p><p><br /> w. Take notes
*Jim had some questions about roles and communication methods.&nbsp; He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
+
</p><p><br /> x. Take responsibility
 
+
</p><p><br /> y. Volunteer, be willing
*Carrie shared what she'd done to get caught up on team training.&nbsp; She asks that team members tell her when she does something contrary to what the team learned/agreed to during training.<br>
+
</p><p><br /> z. Right to expect candor and openness
 
+
</p><p><br /> aa. Own it
<br>
+
</p><p><br /> bb. Be present
+
</p><p><br /> cc. Be on time (late + good story = on time)
 
+
</p><p><br /> dd. Outlook calendars up to date (for scheduling purposes)<br />
<br>
+
</p><p>ee.&nbsp; Meetings will start on time.&nbsp; Team will wait no longer than 5 minutes for late arrivals. <a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 13:14, 30 June 2009 (UTC)
<br>
+
</p><p><br /> <br />
+
</p><p><br /> 3.&nbsp; Vision Statements
 
+
</p><p><br />
+
</p>
  2.&nbsp; Decide on a platform to facilitate documentation and communication&nbsp;  
+
<ul><li>Team will meet on Th Aug 25 to develop vision statement<br />
+
</li></ul>
+
<ul><li>Team members will submit draft vision statements to blog (<a href="http://blogs.middlebury.edu/liswebsite/">LIS Website Project</a>)<br />
 
+
</li></ul>
<br>
+
<p><br />
+
</p><p><br /> 4.&nbsp; Future agenda items
 
+
</p><p><br />
+
</p>
+
<ul><li>Other potential team protocols were mentioned in conversation as team members arrived at the meeting.&nbsp; It was suggested that these potential protocols be brought up during the time allotted for discussion of team protocols.&nbsp; Because we needed to plan for drafting a vision statement, we didn't have time to discuss protocols.&nbsp; Therefore, perhaps we should plan to discuss team protocols in a future meeting.
+
</li></ul>
 
+
<p>Other items on today's agenda for which we didn't have time (we had too many other important issues to resolve!):
<br>
+
</p><p><br />
+
</p>
 
+
<ul><li>Define measurements/metrics (10 min)<br />What does success look like?<br />What metric will define our success?
<br>
+
</li></ul>
+
<ul><li>Building Coalition - Creating a Marketing Plan (10 min)<br />Who do we need to engage early on?<br />We need to engage early for: information and understanding, input, resources (actual and potential)
 
+
</li></ul>
*What will we use this platform for?&nbsp; Communication within the team and with our users/constituents.
+
<ul><li>Action Plan to Achieve Key Deliverables (10 min)<br />Tasks to be accomplished?<br />Who is accountable?<br />Delivery Time?<br />
 
+
</li></ul>
*What are our options?&nbsp; Basecamp, Microsoft Project, Groove, MediaWiki, Wordpress, Drupal (not yet)
+
<p><br />
 
+
</p><p><br /> 5.&nbsp; Action items<br />
*We discussed the merits and drawbacks of the options.
+
</p><p><br />
 
+
</p>
*We decided by majority:&nbsp; At least in the beginning, we will use MediaWiki for meeting notes and documentation, and Wordpress for communication among ourselves and with our users/constituents.&nbsp; We may use email to direct users/constituents (and team members) to Wordpress.&nbsp; We may use email to communicate within the team about mundane or ephemeral matters like absences at meetings.&nbsp; We can revisit this decision in the future by adding it to a meeting agenda.
+
<ul><li>Jim had some questions about roles and communication methods. He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning <br />
 
+
</li></ul>
*Ian created this Wiki category and our blog ([http://blogs.middlebury.edu/liswebsite/ LIS&nbsp;Website Project]).
+
<ul><li>Ian will create a blog and a mediawiki page -- done!
 
+
</li></ul>
<br>
+
<ul><li>Team members will submit draft vision statements to our blog (<a href="http://blogs.middlebury.edu/liswebsite/">LIS Website Project</a>)<br />
+
</li></ul>
 
+
<ul><li>Liz will create Outlook group for LIS web team
<br>
+
</li></ul>
<br>
+
<ul><li>We will meet with our sponsor (Jeff) or sponsor-backup (Mary)
+
</li></ul>
 
+
<ul><li>We will meet elsewhere from time-to-time (Voter East, Music Library, Armstrong Library)
+
</li></ul>
  3.&nbsp; Team Protocols
+
<p><a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 19:48, 25 June 2009 (UTC)<br />
+
</p>
+
<h3> 2009:&nbsp; June 25<br /</h3>
 
+
<p>Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz<br />
<br>
+
</p><p>1. Updates<br />
+
</p>
 
+
<ul><li>Elin is updating Jeff R./Mary B. on team meeting highlights<br />
+
</li><li>Elin will create a post for LISt blog about existence of the LIS Website Project Blog.<br />
+
</li></ul>
+
<p>2. Vision Statement Work<br />
 
+
</p>
<br>
+
<ul><li>Discussion of bringing out common themes or words, creating a tagline (subtitle) for the blog, tags/keywords, discussion of what the statement really should be<br />
+
</li></ul>
 
+
<p>[asides]<br />
<br>
+
</p>
+
<ul><li>There’s a Wordle <a href="http://www.wordle.net/gallery/wrdl/967852/web_team">diagram</a> of our team vision statements on the blog; discussed what WORDLE is—what it represents and where it comes from: <a href="http://www.wordle.net/">Wordle</a> "Wordle is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text."<br />
 
+
</li><li>Discussed scheduling a projector room for future meetings<br />
*Team protocols that were agreed upon during team training were listed:<br>
+
</li></ul>
 
+
<p>[back to vision statement discussion]<br />
a. Meet weekly - adjust frequency as needed if there are no/more agenda items.
+
</p>
+
<ul><li>Discussed important components from each team members’ individual vision statements<br />
 
+
</li><li>Decided we’d wordsmith as a team, using 1 of the statements as a building block<br />
<br>
+
</li><li>Made a list of key terms/strong elements<br />
<br>
+
</li><li>Created a 3 sentence team vision (<a href="https://mediawiki.middlebury.edu/wiki/LIS/LIS_Website#Team_Vision">above</a> and on <a href="http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/">blog</a>)<br />
+
</li><li>Liz suggests getting Robert Keren's feedback on this (and Jeff R.'s as well)<br />
 
+
</li><li>Sense of accomplishment around the table!<br />
+
</li></ul>
  b. Set agenda ahead of time
+
<p>3. End of meeting discussion<br />
+
</p>
 
+
<ul><li>Jess will post <a href="http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/">vision</a> to blog<br />
<br>
+
</li><li>Elin will create agenda for next meeting and distribute<br />
+
</li><li>Team decides it is wise to meet twice a week for the forseeable future<br />
 
+
</li><li>Reminders to keep following/checking the blog and wiki! Experiment and explore. Check out the wiki <a href="http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet">cheat sheet</a> for help with editing! <br />
+
</li></ul>
  c. Shared responsibility to generate agenda items, agenda facilitated by team leader
+
<p><a href="User:Jessica Isler">Jess Isler</a> 17:13, 25 June 2009 (UTC)
+
</p><p><br />
 
+
</p>
<br>
+
<h2> Team Protocols  </h2>
+
<p>Team Protocols<br />
 
+
</p><p><br />
+
</p><p>Agreement - to ensure success (from training workshop)
  d. Agenda items will have specific time and sponsor
+
</p>
+
<ul><li>Authentic and candid dialogue (honesty - with tact)<br />
 
+
</li><li>Open to others<br />
<br>
+
</li><li>Depersonalize <br />
+
</li><li>Participation is required<br />
 
+
</li><li>Engage, share point of view (1X)<br />
+
</li><li>Taking action and achieving results<br />
  e. Time keeper
+
</li><li>Taking responsibility<br />
+
</li><li>Taking notes and communicating<br />
 
+
</li><li>Confidentiality<br />
<br>
+
</li></ul>
+
<p><br />
 
+
</p><p>Meeting Protocol:<br />
+
</p>
  f. Note taker-- I think this responsibility should rotate alphabetically.&nbsp; If someone can't take notes when it's his/her turn then that person can ask for a substitute.&nbsp; [[User:Carrie Macfarlane|Macfarlane, Carrie Miyoshi]] 13:13, 30 June 2009 (UTC)
+
<ul><li>Meetings will start on time and end on time; unless team decides otherwise<br />
+
</li><li>Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting<br />
+
</li><li>Meetings will start on time. Team will wait no longer than 5 minutes for late arrivals<br />
 
+
</li><li>Meet weekly - adjust frequency as needed if there are no/more agenda items<br />
<br>
+
</li><li>Agenda - set/communicated ahead of meeting; facilitated by team leader; team shares responsibility for agenda items; time assigned to each agenda item; allow time at beginning (5 - 10 min) to allow for brief updates, news etc.; allow for time at end (5-10 min) for discussion overflow, to wrap up and to suggest agenda items for the next meeting<br />
+
</li><li>Time keeper - rotate responsibility<br />
 
+
</li><li>Note taker - rotate alphabetically. If someone can't take notes when it's his/her turn then that person can ask for a substitute. Meeting notes posted to the wiki within X days; action items listed<br />
+
</li><li>Meeting location - varies to accomodate the work to be done (projection, white boards, etc) and member office locations
+
</li></ul>
+
<p><br />
 
+
</p><p>Misc.<br />
<br>
+
</p>
+
<ul><li>Be informed; make the decision and move on - or fix it and move on<br />
 
+
</li><li>Be on board<br />
f1. Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting. [Barbara 6/26]
+
</li><li>Focus on and value time over story<br />
+
</li><li>Take responsibility<br />
 
+
</li><li>Volunteer, be willing<br />
<br>
+
</li><li>Right to expect candor and openness<br />
+
</li><li>Be the solution<br />
 
+
</li><li>Be present<br />
+
</li><li>Team will use shared platform for communication and development of documentation<br />
  g. Use shared platform for communication and development of documentation
+
</li><li>Communicate schedule availability to team leader; take personal responsibility for staying informed<br />
+
</li><li>Simple majority rules<br />
 
+
</li><li>Be on time (late + good story = on time)<br />
<br>
+
</li><li>Keep Outlook calendars up to date (for scheduling purposes)<br />
+
</li><li>Share schedule/workload conflicts with team
 
+
</li></ul>
 
  h. Timely (define?) posting of meeting notes
 
 
 
 
<br>
 
 
 
 
 
  i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda
 
 
 
 
<br>
 
 
 
 
 
  j. If unable to attend, responsible for getting caught up
 
 
 
 
<br>
 
 
 
 
 
  k. Open honest dialogue (with tact)
 
 
 
 
<br>
 
 
 
 
 
  l. Simple majority rules
 
 
 
 
<br>
 
 
 
 
 
  m. Agreement - to ensure success (from training)
 
 
 
 
<br>
 
 
 
 
 
  n. Authentic and candid dialogue
 
 
 
 
<br>
 
 
 
 
 
  o. Honest - with tact
 
 
 
 
<br>
 
 
 
 
 
  p. Open to others - come to agreement
 
 
 
 
<br>
 
 
 
 
 
  q. Make the decision and move on - or fix it and move on
 
 
 
 
<br>
 
 
 
 
 
  r. Depersonalize and on board
 
 
 
 
<br>
 
 
 
 
 
  s. Participate, engage, share point of view 1X
 
 
 
 
<br>
 
 
 
 
 
  t. Focus on and value time over story
 
 
 
 
<br>
 
 
 
 
 
  u. Informed, fast decisions
 
 
 
 
<br>
 
 
 
 
 
  v. Confidential
 
 
 
 
<br>
 
 
 
 
 
  w. Take notes
 
 
 
 
<br>
 
 
 
 
 
  x. Take responsibility
 
 
 
 
<br>
 
 
 
 
 
  y. Volunteer, be willing
 
 
 
 
<br>
 
 
 
 
 
  z. Right to expect candor and openness
 
 
 
 
<br>
 
 
 
 
 
  aa. Own it
 
 
 
 
<br>
 
 
 
 
 
  bb. Be present
 
 
 
 
<br>
 
 
 
 
 
  cc. Be on time (late + good story = on time)
 
 
 
 
<br>
 
 
 
 
 
  dd. Outlook calendars up to date (for scheduling purposes)
 
 
 
 
 
<br>
 
 
 
 
ee.&nbsp; Meetings will start on time.&nbsp; Team will wait no longer than 5 minutes for late arrivals. [[User:Carrie Macfarlane|Macfarlane, Carrie Miyoshi]] 13:14, 30 June 2009 (UTC)
 
 
 
 
<br>
 
 
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
 
  3.&nbsp; Vision Statements
 
 
 
 
<br>
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Team will meet on Th Aug 25 to develop vision statement<br>
 
 
 
*Team members will submit draft vision statements to blog ([http://blogs.middlebury.edu/liswebsite/ LIS Website Project])<br>
 
 
 
<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
 
  4.&nbsp; Future agenda items
 
 
 
 
<br>
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Other potential team protocols were mentioned in conversation as team members arrived at the meeting.&nbsp; It was suggested that these potential protocols be brought up during the time allotted for discussion of team protocols.&nbsp; Because we needed to plan for drafting a vision statement, we didn't have time to discuss protocols.&nbsp; Therefore, perhaps we should plan to discuss team protocols in a future meeting.
 
 
 
Other items on today's agenda for which we didn't have time (we had too many other important issues to resolve!):
 
 
 
 
<br>
 
<br>
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Define measurements/metrics (10 min)<br>What does success look like?<br>What metric will define our success?
 
 
 
*Building Coalition - Creating a Marketing Plan (10 min)<br>Who do we need to engage early on?<br>We need to engage early for: information and understanding, input, resources (actual and potential)
 
 
 
*Action Plan to Achieve Key Deliverables (10 min)<br>Tasks to be accomplished?<br>Who is accountable?<br>Delivery Time?<br>
 
 
 
<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
 
  5.&nbsp; Action items
 
 
 
 
 
<br>
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Jim had some questions about roles and communication methods. He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning <br>
 
 
 
*Ian will create a blog and a mediawiki page -- done!
 
 
 
*Team members will submit draft vision statements to our blog ([http://blogs.middlebury.edu/liswebsite/ LIS Website Project])<br>
 
 
 
*Liz will create Outlook group for LIS web team
 
 
 
*We will meet with our sponsor (Jeff) or sponsor-backup (Mary)
 
 
 
*We will meet elsewhere from time-to-time (Voter East, Music Library, Armstrong Library)
 
 
 
[[User:Carrie Macfarlane|Macfarlane, Carrie Miyoshi]] 19:48, 25 June 2009 (UTC)<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
<br>
 
 
 
 
=== 2009:&nbsp; June 25<br>  ===
 
 
 
Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
1. Updates
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Elin is updating Jeff R./Mary B. on team meeting highlights<br>
 
 
 
*Elin will create a post for LISt blog about existence of the LIS Website Project Blog.<br>
 
 
 
2. Vision Statement Work<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
<br>
 
 
 
 
*Discussion of bringing out common themes or words, creating a tagline (subtitle) for the blog, tags/keywords, discussion of what the statement really should be<br>
 
 
 
[asides]<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
<br>
 
 
 
 
*There’s a Wordle [http://www.wordle.net/gallery/wrdl/967852/web_team diagram] of our team vision statements on the blog; discussed what WORDLE is—what it represents and where it comes from: [http://www.wordle.net/ Wordle] "Wordle is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text."<br>
 
 
 
*Discussed scheduling a projector room for future meetings<br>
 
 
 
[back to vision statement discussion]<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
<br>
 
 
 
 
*Discussed important components from each team members’ individual vision statements<br>
 
 
 
*Decided we’d wordsmith as a team, using 1 of the statements as a building block<br>
 
 
 
*Made a list of key terms/strong elements<br>
 
 
 
*Created a 3 sentence team vision ([https://mediawiki.middlebury.edu/wiki/LIS/LIS_Website#Team_Vision above] and on [http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/ blog])<br>
 
 
 
*Liz suggests getting Robert Keren's feedback on this (and Jeff R.'s as well)<br>
 
 
 
*Sense of accomplishment around the table!<br>
 
 
 
3. End of meeting discussion<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
<br>
 
 
 
 
*Jess will post [http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/ vision] to blog<br>
 
 
 
*Elin will create agenda for next meeting and distribute<br>
 
 
 
*Team decides it is wise to meet twice a week for the forseeable future<br>
 
 
 
*Reminders to keep following/checking the blog and wiki! Experiment and explore. Check out the wiki [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet cheat sheet] for help with editing! <br>
 
 
 
[[User:Jessica Isler|Jess Isler]] 17:13, 25 June 2009 (UTC)
 
 
 
 
<br>
 
<br>
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
== Team Protocols  ==
 
 
 
Team Protocols<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
 
 
 
 
 
<br>
 
 
 
 
Agreement - to ensure success (from training workshop)
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Authentic and candid dialogue (honesty - with tact)<br>
 
 
 
*Open to others<br>
 
 
 
*Depersonalize <br>
 
 
 
*Participation is required<br>
 
 
 
*Engage, share point of view (1X)<br>
 
 
 
*Taking action and achieving results<br>
 
 
 
*Taking responsibility<br>
 
 
 
*Taking notes and communicating<br>
 
 
 
*Confidentiality<br>
 
 
 
<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
Meeting Protocol:
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Meetings will start on time and end on time; unless team decides otherwise<br>
 
 
 
*Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting<br>
 
 
 
*Meetings will start on time. Team will wait no longer than 5 minutes for late arrivals<br>
 
 
 
*Meet weekly - adjust frequency as needed if there are no/more agenda items<br>
 
 
 
*Agenda - set/communicated ahead of meeting; facilitated by team leader; team shares responsibility for agenda items; time assigned to each agenda item; allow time at beginning (5 - 10 min) to allow for brief updates, news etc.; allow for time at end (5-10 min) for discussion overflow, to wrap up and to suggest agenda items for the next meeting<br>
 
 
 
*Time keeper - rotate responsibility<br>
 
 
 
*Note taker - rotate alphabetically. If someone can't take notes when it's his/her turn then that person can ask for a substitute. Meeting notes posted to the wiki within X days; action items listed<br>
 
 
 
*Meeting location - varies to accomodate the work to be done (projection, white boards, etc) and member office locations
 
 
 
<br>
 
 
 
 
<br>
 
<br>
 
 
 
 
Misc.
 
 
 
 
 
<br>
 
 
 
 
<br>
 
 
 
 
*Be informed; make the decision and move on - or fix it and move on<br>
 
 
 
*Be on board<br>
 
 
 
*Focus on and value time over story<br>
 
 
 
*Take responsibility<br>
 
 
 
*Volunteer, be willing<br>
 
 
 
*Right to expect candor and openness<br>
 
 
 
*Be the solution<br>
 
 
 
*Be present<br>
 
 
 
*Team will use shared platform for communication and development of documentation<br>
 
 
 
*Communicate schedule availability to team leader; take personal responsibility for staying informed<br>
 
 
 
*Simple majority rules<br>
 
 
 
*Be on time (late + good story = on time)<br>
 
 
 
*Keep Outlook calendars up to date (for scheduling purposes)<br>
 
 
 
*Share schedule/workload conflicts with team
 

Revision as of 11:09, 1 July 2009

This is the space that the LIS Website Team will use for documentation and note taking.




Team Vision

We are creating a web site with intuitive navigation, easy access to services and resources, inviting interfaces, and a workflow that allows simple maintenance.

Meeting Notes

2009:  June 24

Present:  Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin, Barbara Merz.




1.  Questions for the team - Jim and Carrie


  • Jim had some questions about roles and communication methods.  He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
  • Carrie shared what she'd done to get caught up on team training.  She asks that team members tell her when she does something contrary to what the team learned/agreed to during training.



2.  Decide on a platform to facilitate documentation and communication 


  • What will we use this platform for?  Communication within the team and with our users/constituents.
  • What are our options?  Basecamp, Microsoft Project, Groove, MediaWiki, Wordpress, Drupal (not yet)
  • We discussed the merits and drawbacks of the options.
  • We decided by majority:  At least in the beginning, we will use MediaWiki for meeting notes and documentation, and Wordpress for communication among ourselves and with our users/constituents.  We may use email to direct users/constituents (and team members) to Wordpress.  We may use email to communicate within the team about mundane or ephemeral matters like absences at meetings.  We can revisit this decision in the future by adding it to a meeting agenda.



3.  Team Protocols


  • Team protocols that were agreed upon during team training were listed:

a. Meet weekly - adjust frequency as needed if there are no/more agenda items.


b. Set agenda ahead of time


c. Shared responsibility to generate agenda items, agenda facilitated by team leader


d. Agenda items will have specific time and sponsor


e. Time keeper


f. Note taker-- I think this responsibility should rotate alphabetically.  If someone can't take notes when it's his/her turn then that person can ask for a substitute.  <a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 13:13, 30 June 2009 (UTC)


f1. Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting. [Barbara 6/26]


g. Use shared platform for communication and development of documentation


h. Timely (define?) posting of meeting notes


i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda


j. If unable to attend, responsible for getting caught up


k. Open honest dialogue (with tact)


l. Simple majority rules


m. Agreement - to ensure success (from training)


n. Authentic and candid dialogue


o. Honest - with tact


p. Open to others - come to agreement


q. Make the decision and move on - or fix it and move on


r. Depersonalize and on board


s. Participate, engage, share point of view 1X


t. Focus on and value time over story


u. Informed, fast decisions


v. Confidential


w. Take notes


x. Take responsibility


y. Volunteer, be willing


z. Right to expect candor and openness


aa. Own it


bb. Be present


cc. Be on time (late + good story = on time)


dd. Outlook calendars up to date (for scheduling purposes)

ee.  Meetings will start on time.  Team will wait no longer than 5 minutes for late arrivals. <a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 13:14, 30 June 2009 (UTC)




3.  Vision Statements


  • Team will meet on Th Aug 25 to develop vision statement



4.  Future agenda items


  • Other potential team protocols were mentioned in conversation as team members arrived at the meeting.  It was suggested that these potential protocols be brought up during the time allotted for discussion of team protocols.  Because we needed to plan for drafting a vision statement, we didn't have time to discuss protocols.  Therefore, perhaps we should plan to discuss team protocols in a future meeting.

Other items on today's agenda for which we didn't have time (we had too many other important issues to resolve!):


  • Define measurements/metrics (10 min)
    What does success look like?
    What metric will define our success?
  • Building Coalition - Creating a Marketing Plan (10 min)
    Who do we need to engage early on?
    We need to engage early for: information and understanding, input, resources (actual and potential)
  • Action Plan to Achieve Key Deliverables (10 min)
    Tasks to be accomplished?
    Who is accountable?
    Delivery Time?



5.  Action items


  • Jim had some questions about roles and communication methods. He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
  • Ian will create a blog and a mediawiki page -- done!
  • Liz will create Outlook group for LIS web team
  • We will meet with our sponsor (Jeff) or sponsor-backup (Mary)
  • We will meet elsewhere from time-to-time (Voter East, Music Library, Armstrong Library)

<a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 19:48, 25 June 2009 (UTC)

2009:  June 25

Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz

1. Updates

  • Elin is updating Jeff R./Mary B. on team meeting highlights
  • Elin will create a post for LISt blog about existence of the LIS Website Project Blog.

2. Vision Statement Work

  • Discussion of bringing out common themes or words, creating a tagline (subtitle) for the blog, tags/keywords, discussion of what the statement really should be

[asides]

  • There’s a Wordle <a href="http://www.wordle.net/gallery/wrdl/967852/web_team">diagram</a> of our team vision statements on the blog; discussed what WORDLE is—what it represents and where it comes from: <a href="http://www.wordle.net/">Wordle</a> "Wordle is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text."
  • Discussed scheduling a projector room for future meetings

[back to vision statement discussion]

3. End of meeting discussion

<a href="User:Jessica Isler">Jess Isler</a> 17:13, 25 June 2009 (UTC)


Team Protocols

Team Protocols


Agreement - to ensure success (from training workshop)

  • Authentic and candid dialogue (honesty - with tact)
  • Open to others
  • Depersonalize
  • Participation is required
  • Engage, share point of view (1X)
  • Taking action and achieving results
  • Taking responsibility
  • Taking notes and communicating
  • Confidentiality


Meeting Protocol:

  • Meetings will start on time and end on time; unless team decides otherwise
  • Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting
  • Meetings will start on time. Team will wait no longer than 5 minutes for late arrivals
  • Meet weekly - adjust frequency as needed if there are no/more agenda items
  • Agenda - set/communicated ahead of meeting; facilitated by team leader; team shares responsibility for agenda items; time assigned to each agenda item; allow time at beginning (5 - 10 min) to allow for brief updates, news etc.; allow for time at end (5-10 min) for discussion overflow, to wrap up and to suggest agenda items for the next meeting
  • Time keeper - rotate responsibility
  • Note taker - rotate alphabetically. If someone can't take notes when it's his/her turn then that person can ask for a substitute. Meeting notes posted to the wiki within X days; action items listed
  • Meeting location - varies to accomodate the work to be done (projection, white boards, etc) and member office locations


Misc.

  • Be informed; make the decision and move on - or fix it and move on
  • Be on board
  • Focus on and value time over story
  • Take responsibility
  • Volunteer, be willing
  • Right to expect candor and openness
  • Be the solution
  • Be present
  • Team will use shared platform for communication and development of documentation
  • Communicate schedule availability to team leader; take personal responsibility for staying informed
  • Simple majority rules
  • Be on time (late + good story = on time)
  • Keep Outlook calendars up to date (for scheduling purposes)
  • Share schedule/workload conflicts with team
Powered by MediaWiki