Canvas roll-out for Stanford University

Login: http://canvas.stanford.edu
Help and resources: http://gocanvas.stanford.edu
CourseWork has been used for 10 years (not many people are aware of this).
Currently exploring options for other Learning Management Systems (LMS).  CourseWork is built on Sakai.  Other institutions have already moved over to Canvas, now Stanford is too.
 
Users were split between CourseWork and Blackboard (paid), contract was ending in 2013 and Stanford was considering more modern options for an LMS.  An open-source version of Canvas was piloted in Fall of 2013 with about 5 courses.  Faculty and student feedback was gathered.  Pilot ended in summer 2015.
Stanford joined the cloud-hosted version of Canvas and off the open source version.
Currently, Stanford supports both CourseWork and Cavnas during the transition period.
GSB has moved over to Canvas already.
Stanford is part of a Canvas R1 Peer Group, collaboration with other institutions and have a monthly conf call to deal with feature requests, building new functionality, sharing policies, etc.  There is also a Canvas brown-bag lunch group on campus.
Single sign-on is supported.  Tablets and smartphones are supported.
Continuing studies operates year round and has courses over the summer as well.  Since Continuing Studies was helping to pay for Blackboard license, when that was expiring, we (VPTL) collaborated on a pilot of both NovoEd and Canvas.  Now Continuing Studies is using Cavnas independently.  Continuing Studies needs to support non-Stanford users (Blackboard does this and so does VPTL's Cavnas).  Some Continuing Studies courses are also online only, so they got to test features needed that are primarily for online courses only.
>73% found it easy to use and were satisfied (higher levels for students).
User interface in Canvas is much better.
GSB adopted Canvas in August 2014 on their own separate instance.  Satisfaction has gotten better over time as users adapt to the new system.
Downsides of Cavnas vs Sakai (CourseWork): Canvas has only limited support for recording, limited support for different types of assignments (like anonymous grading).
Canvas has a website to accept and track feature suggestions (includes voting).  As part of an R1 school, Stanford can help organize feature requests and help to get them voted on.
There is a phased transition from CourseWork to Cavnas, starting in Fall 2015.  By end of Fall 2016, all courses will be off of CourseWork.
There are currently 303 courses on Canvas, past the goal for this point.
There is a Sakai to Canvas migration tool, but it doesn't do everything, so staff will help with this process.  Faculty can also rethink their course design during the migration to improve student engagement.  Kristen and Kimberley can consult on the migration to help with this process.
Canvas has development communities with information about APIs.  Canvas Brown Bag group is a good way to learn more.  Contact one of the sessions organizers to learn more.
Currently doing interviews, surveys, monitoring support requests to gather feedback and understand more about Canvas migration.
Multiple login buttons: GSB, Continuing Studies (may or may not have SUNET), everyone else (with SUNET ID).
Canvas does releases every 6 weeks.  ZenDesk is used for Stanford Canvas support.