1. Where Were We Last Time?
1.1. Birth of Bonsai
1.2. Pricing Strategies Explained
1.3. Rollout Plan Provided
2. Where Are We This Time?
2.1. Impact Letters (2 Variants)
2.1.1. Bonsai will cost x but you may be interested in Bloom...
2.1.2. Bonsai would cost x but Bloom is required...
2.2. 26 Customers Have Renewed Onto a New Service
2.2.1. Using Contract Amendment Letters
3. Rollout of Bonsai
3.1. Recap
3.1.1. No Significant Changes to Price
3.1.2. Boundaries/Restrictions Clearly Defined
3.2. Progress
3.2.1. 18 Customers Signed and Invoiced So Far...
4. Rollout of Bloom
4.1. Recap of Benefits
4.1.1. Very High Service Levels
4.1.2. Unlimited Storage*
4.1.3. Additional Optional Services
4.2. Progress
4.2.1. Process is More Time-Consuming than Bonsai
4.2.2. 8 Customers Signed and Invoiced So Far...
4.3. Contracts
4.3.1. Planned to Introduce New Contract
4.3.2. New Contract is Still in Draft
4.3.3. Currently Using Existing Contract (with Amendment Letter)
5. Customisation
5.1. Principles
5.1.1. Enable, Encourage and Support Customisation
5.1.2. Responsibilities Clearly Defined
5.2. Supporting Services
5.2.1. Private Theme - Customer-Specific Theme Code
5.2.2. Tailored - Customer-Specific Plugin Selection
5.2.3. Leading Edge - Customer-Specific Moodle Core Version
5.3. Pragmatic Decision Making
5.3.1. Prevalence of Bespoke Code
5.3.2. Lack of Customer-Configurable Themes in Moodle/Bloom
5.3.3. Private Theme/Tailored Available to both Bloom AND Bonsai
5.3.4. Offered at No Charge Until At Least August '15
6. SLAs
6.1. Significance (see el.blogs.ulcc.ac.uk)
6.2. Progress
6.2.1. 16 Complete (3 unpublished) with 6 Remaining
6.3. Where To find?
6.3.1. el.blogs.ulcc.ac.uk
6.3.2. Signed Contract Amendment
6.3.3. Portal?
6.4. Versioning
6.4.1. Balance Evolving Document and Consistent Service Provision
6.4.2. Recognition This Must Be Managed
6.4.3. Open to Suggestions / Thoughts
7. Management Changes
7.1. John Hilton - Focus on Analytics
7.2. Dave Kenworthy - Interim Head of Learning Technology Services
7.3. Effectively Operating as Single Unit
8. Bloom Software
8.1. Quarterly Upgrades
8.1.1. Fortnight Into First Rollout
8.1.2. Release Note Feedback Welcomed
8.1.3. Considering Weekends for Future Releases
8.2. Roadmap
8.2.1. March 2015 - Aiming for Moodle v2.8
9. Where Should We Be Next Time?
9.1. March 2015?
9.1.1. Closer to Completion of Bloom/Bonsai Transition (75% ?)
9.1.2. All SLAs Complete and Published
9.1.3. New Contract Ready for Bloom Use
9.1.4. Established Delivery of Bloom/Bonsai Service Levels
9.1.5. Planning Rollout of Moodle v2.8