1. SLN2.0 Overview of the Technology Strategy

2. 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

3. Task Force-driven evaluation criteria  Integration, integration, integration u Strong support for discipline-specific and other niche tools u Native interoperability with SUNY’s developing portal environment u Strong integration with other campus IT systems  Student-centric design  Support for the IMS Learning Design (LD) specification  Open Source development

4. A better way forward  uPortal at the center  Tools from a variety of sources u Sakai u JA-SIG u Various Open Source projects u Various commercial ventures  LAMS for enhanced course authoring and learning experiences

5. Key milestones  December 2005 u Chancellor’s review of SLN business case u Completion of SLN2.0 first functional and technical requirements snapshot  Early 2006 u RFP bidding process u Specification of first proof-of-concept  Fall 2006 u First proof-of-concept piloted  Fall 2007 u First production release

6. Implementation strategy highlights  Outsourced development  Recruitment of development partners  Quarterly milestones (“timeboxing”) with community feedback  Risk mitigation plan  Agile development

7. 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

8. 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?

9. 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