Middlebury

Difference between revisions of "LIS Website"

Line 7: Line 7:
 
=== 2009:  June 24  ===
 
=== 2009:  June 24  ===
  
Present:&nbsp; Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin.<br>
+
Present:&nbsp; Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin.<br>  
  
 
1.&nbsp; Questions for the team - Jim and Carrie<br>  
 
1.&nbsp; Questions for the team - Jim and Carrie<br>  
  
*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
+
*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  
 
*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>
 
*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>
  
<br>
+
<br>  
  
 
2.&nbsp; Decide on a platform to facilitate documentation and communication&nbsp; <br>  
 
2.&nbsp; Decide on a platform to facilitate documentation and communication&nbsp; <br>  
  
*What will we use this for?&nbsp; Communication within the team and with our users/constituents.
+
*What will we use this for?&nbsp; Communication within the team and with our users/constituents.  
*What are our options?&nbsp; Basecamp, Microsoft Project, Groove, MediaWiki, Wordpress, Drupal (not yet)
+
*What are our options?&nbsp; Basecamp, Microsoft Project, Groove, MediaWiki, Wordpress, Drupal (not yet)  
*We discussed the merits and drawbacks of the options.
+
*We discussed the merits and drawbacks of the options.  
*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 our users/constituents to Wordpress.&nbsp; We may use email to communicate within the team about mundane matters like absences at meetings.&nbsp; We can revisit this decision in the future by adding it to a meeting agenda.
+
*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 our users/constituents to Wordpress.&nbsp; We may use email to communicate within the team about mundane matters like absences at meetings.&nbsp; We can revisit this decision in the future by adding it to a meeting agenda.  
 
*Ian created this Wiki category and our blog ([http://blogs.middlebury.edu/liswebsite/ LIS&nbsp;Website Project]).
 
*Ian created this Wiki category and our blog ([http://blogs.middlebury.edu/liswebsite/ LIS&nbsp;Website Project]).
  
 +
<br>
 +
 +
3.&nbsp; Team Protocols<br>
 +
 +
*Team protocols that were agreed upon during team training were listed:<br>
  
 +
a. Meet weekly meeting - adjust frequency as needed if there are no/more agenda items.
  
3.&nbsp; Team Protocols<br>
+
b. Set agenda ahead of time
  
*Team protocols that were agreed upon during team training were listed:<br>
+
c. Shared responsibility to generate agenda items, agenda facilitated by team leader
  
a. Meet weekly meeting - adjust frequency as needed if there are no/more agenda items.
+
d. Agenda items will have specific time and sponsor
  
b. Set agenda ahead of time
+
e. Time keeper
  
c. Shared responsibility to generate agenda items, agenda facilitated by team leader
+
f. Note taker
  
d. Agenda items will have specific time and sponsor
+
g. Use shared platform for communication and development of documentation
  
e. Time keeper
+
h. Timely (define?) posting of meeting notes
  
f. Note taker
+
i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda
  
g. Use shared platform for communication and development of documentation
+
j. If unable to attend, responsible for getting caught up
  
h. Timely (define?) posting of meeting notes
+
k. Open honest dialogue (with tact)  
  
i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda
+
l. Simple majority rules
  
j. If unable to attend, responsible for getting caught up
+
m. Agreement - to ensure success (from training)
  
k. Open honest dialogue (with tact)
+
n. Authentic and candid dialogue  
  
l. Simple majority rules
+
o. Honest - with tact
  
m. Agreement - to ensure success (from training)
+
p. Open to others - come to agreement
  
n. Authentic and candid dialogue
+
q. Make the decision and move on - or fix it and move on
  
o. Honest - with tact
+
r. Depersonalize and on board
  
p. Open to others - come to agreement
+
s. Participate, engage, share point of view 1X
  
q. Make the decision and move on - or fix it and move on
+
t. Focus on and value time over story
  
r. Depersonalize and on board
+
u. Informed, fast decisions
  
s. Participate, engage, share point of view 1X
+
v. Confidential
  
t. Focus on and value time over story
+
w. Take notes
  
u. Informed, fast decisions
+
x. Take responsibility
  
v. Confidential
+
y. Volunteer, be willing
  
w. Take notes
+
z. Right to expect candor and openness
  
x. Take responsibility
+
aa. Own it
  
y. Volunteer, be willing
+
bb. Be present
  
z. Right to expect candor and openness
+
<br>
  
aa. Own it
+
3.&nbsp; Vision Statements
  
bb. Be present
+
*Team will meet on Th Aug 25 to develop vision statement<br>
 +
*Team members will submit draft vision statements to our blog ([http://blogs.middlebury.edu/liswebsite/ LIS Website Project])<br>
  
 +
<br>
  
 +
4.&nbsp; Future agenda item
  
3.&nbsp; Vision statements
+
*Other potential team protocols were mentioned in casual 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 discuss additional team protocols in a future meeting.<br>
  
 +
<br>
  
 +
5.&nbsp; Action items<br>
  
4.&nbsp; Future agenda 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 <br>
 +
*Ian will create a blog and a mediawiki page -- done!
 +
*Team members will submit draft vision statements to our blog (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)
  
*Other potential team protocols were mentioned in conversation prior to the start of the meeting.&nbsp; It was suggested that these potential protocols be discussed during the meeting.&nbsp; The allotted time for the meeting came to an end before protocols were discussed.&nbsp; Therefore, perhaps we should discuss additional team protocols in a future meeting.<br>
+
<br>
  
 
== [Add other sections here] ==
 
== [Add other sections here] ==

Revision as of 16:05, 24 June 2009

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


Meeting Notes

2009:  June 24

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

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 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 our users/constituents to Wordpress.  We may use email to communicate within the team about mundane matters like absences at meetings.  We can revisit this decision in the future by adding it to a meeting agenda.
  • Ian created this Wiki category and our blog (LIS Website Project).


3.  Team Protocols

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

a. Meet weekly meeting - 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

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


3.  Vision Statements

  • Team will meet on Th Aug 25 to develop vision statement
  • Team members will submit draft vision statements to our blog (LIS Website Project)


4.  Future agenda item

  • Other potential team protocols were mentioned in casual 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 discuss additional team protocols in a future meeting.


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!
  • Team members will submit draft vision statements to our blog (LIS Website Project)
  • 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)


[Add other sections here]


Powered by MediaWiki