25
Building CSU System-Wide LMS Services using Moodle San Francisco State University Andrew Roderick, Technology Development and Support Manager CSU Chancellor’s Office Kathy Fernandes, Director of System-Wide LMS Initiatives John Whitmer, Associate Director of System-Wide LMS Initiatives

Building CSU System-Wide LMS Services using Moodle

Embed Size (px)

DESCRIPTION

This presentation from the US West Coast 2010 MoodleMoot discusses how the California State University is building coordinated LMS Services to reduce overall system costs and support unique campus needs. In particular, we discuss how the Moodle Learning Management System is being leveraged to reduce cost and increase resources provided for implementation, development, and user support. This presentation discusses the CSU Learning Management Systems and Services Initiative. The project started in 2007 with an RFP to select LMS applications, and has recently begun to provide systemwide LMS services that are offered through local campuses, the CSU Chancellor’s Office, and external providers. Currently there are 4 campuses with Moodle production systems, with 2 additional campuses in the process of converting to Moodle. This presentation will discuss the strategic plan for these services and progress to-date, including development of an ASP Moodle “safety net," a standardized SIS integration into Peoplesoft, a shared knowledge base, and a multi-campus Moodle Consortium. Participants will be asked to discuss their own experiences deploying LMS services, how these models apply to their campus, and identify additional ways that Moodle development and deployment costs can be reduced through consortial arrangements. Presenters:Kathy Fernandes, CSU Office of the ChancellorAndrew Roderick, San Francisco State UniversityJohn Whitmer, CSU Office of the Chancellor

Citation preview

Page 1: Building CSU System-Wide LMS Services using Moodle

Building CSU System-Wide LMS Services using Moodle

San Francisco State UniversityAndrew Roderick, Technology Development and Support Manager

CSU Chancellor’s OfficeKathy Fernandes, Director of System-Wide LMS InitiativesJohn Whitmer, Associate Director of System-Wide LMS Initiatives

Page 2: Building CSU System-Wide LMS Services using Moodle

PASTHistorical background of Moodle collaboration within the CSU system

Page 3: Building CSU System-Wide LMS Services using Moodle

CSU Demographicshttp://calstate.edu

23 campuses Approx. 433,000 FTE students 44,000 faculty and staff We are the largest, the most diverse, & one of the

most affordable university systems in the country We play a vital role in the growth & development of

California's communities and economy

Page 4: Building CSU System-Wide LMS Services using Moodle

About California State University (CSU)

• ~75,000 courses per semestero ~40% had online

components in 2009

Page 5: Building CSU System-Wide LMS Services using Moodle

About California State University (CSU)

• 28+ server installations of 10 different versions of 4 different LMS platforms in 2009

CE 4CE 6.1CE 6.2.3Vista 8

1.9.41.9.5

Bb 7.2Bb 7.3Bb 8Bb 9

Page 6: Building CSU System-Wide LMS Services using Moodle

Early adopter Moodle Campuses

Four campuses use Moodle asthe exclusive LMS:

• San Francisco State - 2007• Humboldt State - 2007• CSU Monterey Bay - 2009• CSU Maritime - 2009

Page 7: Building CSU System-Wide LMS Services using Moodle

San Francisco State University

• 1,500 faculty and 30,000 students• 2,400 courses• Branded as iLearn• Moodle 1.9.9 in Fall• Customized gradebook, course archive, file

system, custom integrations• Mature systems and code management

processes

Page 8: Building CSU System-Wide LMS Services using Moodle

Stages of CSU Moodle collaboration

• Competitive

• Cooperative

• Collaborative

CSU Moodle Coalition was the context for cooperation.

CSU LMSS is the step toward collaboration.

Page 9: Building CSU System-Wide LMS Services using Moodle

PRESENTOverview of CSU System-wide Learning Mgmt Systems & Services

Page 10: Building CSU System-Wide LMS Services using Moodle

CSU Campus LMS Usage (2010)

Page 11: Building CSU System-Wide LMS Services using Moodle

Overview of System-wide Processes

Perform LMS RFI and RFP (2008-2009) Define LMSS Strategy (2009-2010) Implement Governance (2010-2011) Create Collaborative Projects that Benefit

Multiple Campuses (2010-)

Page 12: Building CSU System-Wide LMS Services using Moodle

System-wide LMSS Strategy

1. LMS Futures Group (Provosts, CIOs, Faculty) prepared 4 documents (http://dat.cdl.edu):– LMS Critical Elements– External Scan of Market & Higher Ed Systems– CSU System-wide Recommendations– LMS Governance Recommendations

2. Organize stakeholders to implement recommendations, starting with Moodle

Page 13: Building CSU System-Wide LMS Services using Moodle

System-wide LMS Governance

Page 14: Building CSU System-Wide LMS Services using Moodle

Identified Project Areas for 2010

1. Governance implementation and revision

2. Common licensing (lms, integrations, etc.)

3. Common Moodle codebase (mixed hosting)

4. Integrations – library, MERLOT, web conferencing, lecture capture

5. Migration, training

Future: shared help desk / support And other activities that governance identifies …

Page 15: Building CSU System-Wide LMS Services using Moodle

CSU Moodle Collaborations

Page 16: Building CSU System-Wide LMS Services using Moodle

Stages of Adoption/Interest

Mature New Production Pilot LMS Assessment Moodle-curious

Page 17: Building CSU System-Wide LMS Services using Moodle

Moodle Common Interest Group (CIG)

Forming in Fall 2010 Informational/Community and

Production/Deliverables based Open Participation + Working Groups Steered by Governance (S&PG) Broad Stakeholders (IT, AT, ID, Developers, etc.) Balance local campus needs w/ economies of

scale, common development

Page 18: Building CSU System-Wide LMS Services using Moodle

Community Building is like Watercolor

Page 19: Building CSU System-Wide LMS Services using Moodle

It’s About Balance

Campus Needs vs. Central Opportunities Vendor Hosted + Self-Hosted Needs Based on Stage of Adoption Differences in Stakeholder Perspectives Differences in Campus Environments/Size Differences in Resources and Compentencies

Page 20: Building CSU System-Wide LMS Services using Moodle

Discovery

How do we work with each other? How do we work with other initiatives? How do we work with others (external

institutions)? How do we work with moodle.org (core)? How do we work with vendors?

Page 21: Building CSU System-Wide LMS Services using Moodle

Common Code Base

End goal is stable, effective build running in a campus environment – this means interdisciplinary participation.

CSU Distribution centrally tested and managed Locally tested and customized for environments Scaled for performance across campus size Agreed upon components, add-ons More to come…

Page 22: Building CSU System-Wide LMS Services using Moodle

CSU-wide Initiatives

Purpose-built for the CSU Local Infrastructure Integrations Accessible Technology Initiative CSU Library Initiatives (Xerxes, etc.) Merlot Fresca Digital Marketplace/Affordable Learning

Solutions

Page 23: Building CSU System-Wide LMS Services using Moodle

Models, Ideas

Page 24: Building CSU System-Wide LMS Services using Moodle

Key Questions to Address Common codebase process – change

management framework, QA, requirements definition … in decentralized, opt-in environment

Readiness and participation “requirements” – in-kind or $$$? Recognize diverse existing investments/resources

Defining economic value and metrics – increase efficiency/VOI, not cash savings

Communication plan – addressing diverse stakeholders w/o attending every meeting

Page 25: Building CSU System-Wide LMS Services using Moodle

Contact Information

SF State Andrew Roderick ([email protected])

Technology Development Manager

Chancellor’s OfficeKathy Fernandes ([email protected])

Director of System-Wide LMS Initiatives

John Whitmer ([email protected])Associate Director of System-Wide LMS Initiatives