1 / 35

Welcome

Welcome. Welcome to the Kuali Ready Project Board Meeting at Kuali Days!. Purpose & Desired Outcome. Meeting Purpose Communicate a common understanding of current issues and activities to stakeholders General Availability Readiness Review Desired Outcome

eshana
Download Presentation

Welcome

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Welcome Welcome to the Kuali Ready Project Board Meeting at Kuali Days!

  2. Purpose & Desired Outcome • Meeting Purpose • Communicate a common understanding of current issues and activities to stakeholders • General Availability Readiness Review • Desired Outcome • General Availability Release Date

  3. Agenda Welcome & Introductions Subscription Update GA Readiness Review Guidelines For Sponsored & Sponsoring Entities Marketing Activities Next Steps Roundtable

  4. Introductions • Opening Remarks • Shel Waggener – Chair, Kuali Ready Project Board • Self Introductions

  5. Subscription Update • Total number of subscribers: 49 • New Subscribers • Institutions that have expressed interest • Assumptions in Cost Model • 43 subscribers projected for end of Q4 2010 • 20 of the 43 (~47%) were projected to be Sponsored Subscribers • 95 subscribers projected for end of Q4 2011 • 33 of the 95 (~35%) were projected to be Sponsored Subscribers • Current number of sponsored subscribers: 32 (~65%) • University of California (14), Cal State (10), IU (7), University of Illinois (1)

  6. Release Designations • Release Candidate (RC) • Refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. • General Availability or General Acceptance (GA) • Refers to the point where all necessary commercialization activities have been completed and the software has been made available to the general market. Source: http://en.wikipedia.org/wiki/Software_release_life_cycle

  7. GA Readiness Review • Purpose • Determine if the product is ready for distribution to a wider audience by ensuring that all release criteria have been met. • Format • Review each item on the GA checklist • Project Board will be given an update by key personnel for each item • Based on the status provided, Project Board will decide if the item is complete We need participation & input from Project Leadership

  8. GA Checklist - Summary

  9. GA Checklist Review – Item #1 • Both the Kuali Ready Functional Council and Project Board feel the product has the minimum functionality and set of features that allows the service to be offered to a broader market. • Key Inputs • Shel Waggener – Chair, Project Board • Paul Dimond – Chair, Functional Council

  10. GA Checklist Review – Item #2 • Zero "blocker" bugs • High priority & severity bug categorization • Results in the service being unusable to subscribers • No open critical or high defects • Key Inputs • Tom Tsai – Software Development Manager • Paul Dimond– Chair, Functional Council

  11. GA Checklist Review – Item #3 • Open defects are logged and being reviewed by cross-functional groups. • Key Inputs • Tom Tsai – Software Development Manager • Paul Dimond– Chair, Functional Council

  12. GA Checklist Review – Item #4 • Defined & Documented Onboarding Process • Process map available on Kuali Ready Project space • Reviewed by multiple parties including Kuali Foundation • Subscriptions are handled by the Kuali Foundation • Service contract, billing, settlement • Subscription fees are collected by the Kuali Foundation

  13. GA Checklist Review – Item #5 • Defined & Documented Subscriber Support Process • Process map available on Kuali Ready Project space • Tier 1 Support - Performed at the subscriber’s institution by a functional owner • Tier 2 Support - Provided as part of the subscription by UC Berkeley • Issues are escalated to Tier 2 support by the functional owner at Tier 1 • Tier 3 Support - Infrastructure and application issues are resolved by service providers at the hosting institution in coordination with Tier 2 support

  14. GA Checklist Review – Item #6 • Defined & Documented Financial Model • Subscription Based Pricing Model • Financial Model • Copy available on Kuali Ready Project space • Viewing & editing are restricted • Plan is to use current financial model for two (2) years

  15. GA Checklist Review – Item #7 • Load Testing - Examine Service Performance Behavior and Performance • Performed by UC Berkeley’s Application Services Group • Anticipated Completion Date: Mid December • Key Input • Tom Tsai, Software Development Manager

  16. GA Checklist Review – Item #8 Product Documentation Getting Started Guide & Release Manual provided to all subscribers Copies of both documents posted on Project space Master copies of documents on Project space Copy of the Release Manual available to all on kuali.org

  17. GA Checklist Review – Item #9 Kuali Ready Service Delivery Kuali Ready – U.S. Kuali Ready - Canada UC Berkeley – Kuali Ready Service Management and Subscriber Support Multi-site Hosting

  18. GA Checklist Review – Item #9 • Multi-site Hosting • United States • UC Berkeley – Primary • UCLA - Failover • Canada • University of Toronto – Primary • University of British Colombia – Failover • Service Agreement(s) • Remuneration & remuneration process

  19. GA Checklist Review – Item #10 • Security Audit • Completed • Summary of findings sent out to Project Board • Results analyzed by UC Berkeley's Security, Privacy, and Policy Group • One item was found to be medium level risk to the service • Cross-Site Request Forgery (CSRF) • Application Services is fixing the CSRF finding • Anticipated Completion Date: Mid December

  20. GA Checklist Review – Item #11 • Product Enhancement Request Framework • Enhancements requests may be submitted by all Kuali Ready subscribing entities • Requests submitted by Local Functional Owner • Requests are logged in the Kuali Foundation’s JIRA • Functional Council will review & prioritize requests • Technical assessment will be done on the candidate release bundle • Project Board reviews recommended release bundle

  21. GA Checklist Review – Item #12 Defined & Documented Release Process For Product Enhancements Feature Based Releases Exact time & schedule will vary but anticipated interval between releases will be 6 – 9 months Information on Release Process available on Project web site

  22. GA Checklist Review – Item #13 (Con’t) • Service Maintenance - Non-Critical & Critical Patches • Maintenance Releases are intended to resolve reported noncritical bugs (i.e. bug fixes) • No new features or functionality • New maintenance releases will contain all previous bug fixes. • Production deployment of maintenance releases will be done during non-business hours • Advance notice will be given to subscribers • At least one (1) week prior to scheduled release

  23. GA Checklist Review – Item #13 (Con’t) Service Maintenance - Non-Critical & Critical Patches “Showstopper” or “blocker” bugs are critical problems that make the service unusable to our subscribers and for which there is no workaround Highest priority for development team Applied as needed and may affect service availability

  24. Risks • User Management • Users with multiple e-mail addresses can have login difficulties • Key Inputs: Tom Tsai & Paul Diamond • Financial Model • Currently working with Kuali Foundation to deploy tools to centralize subscriber data & track interactions. • At present, product enhancement requests can be submitted by Functional Council members • Need tools & process for all subscribing entities • Subscriber Service & Support • Do we have sufficient resources?

  25. Are We Ready? Have we completed the items on the GA checklist? Questions, comments, concerns, etc. from Board Members General Availability Release Date

  26. Sponsored & Sponsoring Entities • Problem Statement • Need clarity for multiple campus entities that are interested in subscribing • Draft guidelines presented at the last Project Board meeting • Key Considerations • Definition of a “system” • Who can be a “sponsoring” entity? • One service instance per subscriber • Shel requested that the guidelines be reviewed & defined no later than Kuali Days

  27. Marketing Activities • Announce General Availability of Kuali Ready • Press Release Service • Kuali Insider • Kuali Ready Logo • Special Recognition to Zachary Naiman & Kristina Batiste • Kuali Ready Tagline(s) • Academic continuity planning made easy • Managing the risk of interruption

  28. Marketing Activities • Kuali Ready Trademark • Update Kuali Foundation web site • EDUCAUSE • Update: Ryan Means & Paul Dimond • URMIA • Update: Grace Crickette • Adopter Stories • Product FAQ

  29. Next Steps • Revisions to Project Web Site • Financial Review • Downloadable Source Code • No technical support provided • Service Delivery Council • Product Manager • Job Description • FTE

  30. Next Steps • CRM • Data Ownership • Service Sunsetting - Clarification requested by UofT & UBC • What would be done to preserve the data? • What access capabilities would support retrieval and exporting of data into a standard format? • Hosting Options

  31. Roundtable • Open forum for Project Board Members • Opportunity to initiate discussion on any project related topic

  32. Thank You! Thank You For Your Continued Participation and Contribution!

More Related