sln2.0 overview of the technology strategy. lms’s and combinations evaluated lms’s academus ...
Post on 18-Jan-2018
222 Views
Preview:
DESCRIPTION
TRANSCRIPT
SLN2.0SLN2.0
Overview of the Technology Strategy
LMS’s and combinations evaluated
LMS’s Academus ANGEL Blackboard dotLRN Moodle Sakai WebCT Vista
Combinations Sakai + Moodle +
uPortal Sakai + Academus +
uPortal Academus + Sakai +
LAMS + uPortal
Task Force-driven evaluation criteria
Integration, integration, integration Strong support for discipline-specific and other niche
tools Native interoperability with SUNY’s developing portal
environment Strong integration with other campus IT systems
Student-centric design Support for the IMS Learning Design (LD)
specification Open Source development
A better way forward
uPortal at the center Tools from a variety of sources
Sakai JA-SIG Various Open Source projects Various commercial ventures
LAMS for enhanced course authoring and learning experiences
Key milestones
December 2005 Chancellor’s review of SLN business case Completion of SLN2.0 first functional and technical
requirements snapshot Early 2006
RFP bidding process Specification of first proof-of-concept
Fall 2006 First proof-of-concept piloted
Fall 2007 First production release
Implementation strategy highlights
Outsourced development Recruitment of development partners Quarterly milestones (“timeboxing”) with
community feedback Risk mitigation plan Agile development
Timeboxing: The three-month window Concrete milestones will be set for release every three
months. Inside the timebox, listed deliverables are goals; outside the
timebox, they are forecasts. Once development begins, a new release will be available for
community review every three months. A functional system will be delivered every quarter, even if
features need to be dropped. Various levels of stakeholder involvement and review will be
set in cooperation with the SLN community
Layers of Support
SLN MID’s and Help Desk (as always) LE technology team external vendors and
internal developers Open Source component communities The LMOS Open Source community Your own campus’ developers?
Envisioning the solution
Many of the components available for review Functional spec snapshot in the RFPC, based on
existing functionality SLN1.0 being documented for modeling
purposes Several functional prototypes before production 3-month feedback windows
top related