<p>LATTE Steering Committee November 2015</p><p>Charge The Latte Steering Committee will inform the strategic development of LATTE by providing guidance and governance on a range of issues related to the LMS. These issues include, but are not limited to, policies/procedures, configuration, access, prioritization and selection of new features/functionality, analytics, communications, documentation, training, and support.</p><p>Leadership The Committee will be co-chaired by Karen Muncaster, Vice President for the Rabb School, and Josh Wilson, Associate CIO for Academic Technology (LTS). </p><p>Membership The Committee will be composed of representatives from Arts & Sciences, the Heller School, IBS, and the Rabb School; staff from Library & Technology Services; a graduate student; and an undergraduate. Membership for 2015-16: Rick Alterman, Chad Bergeron, Dawn Skorczewski, Ro Etlinger, Jim LaCreta, Jim Lambert, Adam Lipkin, Jennifer Livengood, Karen Muncaster, Brian Salerno, Emily Scharf, Rise Singer, Aimee Slater, Steve Van Hooser, Josh Wilson.</p><p>Logistics The Committee will convene for two focused 90-minute meetings each semester.</p><p>Proposed Topics, AY 2015-2016 Overarching Question  How should LATTE develop in 2015-2016 and beyond to best serve the University? </p><p>Specific Critical Questions  How are decisions made about what changes are made to the configuration? Who decides which features/functionality are added or which supplemental tools can be integrated into the core configuration? Who should and what should that process look like? Who funds these changes?  What is the cycle for upgrades and version changes? How is this decision made and communicated? Should we follow the recommended rollout of CLAMP?  Who decides what level of access individual community members should receive? How is that decision made?  Who resolves policy issues for the use of the LMS? How should this happen?  What backend processes might be created to improve efficiency/effectiveness and reduce manual operations? How are these changes prioritized and implemented?  What documentation and training currently exists for technical, design, and pedagogical support? Where are the gaps? How can these gaps be addressed?  What communication plans are in place to inform the community about features, services, training etc.? Are there gaps? Are there variances across units that might be addressed?  Based on the answers to the above, do we need more than one instance of LATTE? If so, what resources would be necessary for that to happen?</p>