| Why Sakai as a
Service? |
|
|
|
|
|
|
|
| Campus can reallocate staff
resources |
||||||
| Focus resources on outcomes, not
technology |
||||||
| Focus staff on training/engaging
faculty |
||||||
| Technical staff
gain experience with open source |
||||||
| Gradually take ownership of the project |
||||||
| Not a proprietary instance of Sakai |
||||||
| No vendor lock-in assures choices |
||||||