1 / 10

CI Project Planning

CI Project Planning . - a ‘10 minute’ update on the Flinders project . Marlene Pitman Head, Student Systems & Enrolment Flinders University Wednesday 13 September 2006. Funding. Proposal submitted Oct 2005 Approval in principle Provides for

sawyer
Download Presentation

CI Project Planning

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. CI Project Planning - a ‘10 minute’ update on the Flinders project Marlene Pitman Head, Student Systems & EnrolmentFlinders University Wednesday 13 September 2006

  2. Funding • Proposal submitted Oct 2005 • Approval in principle • Provides for • training/consulting support including tech training • limited increase in technical environment • 3 years FTE additional staff support • additional module (XLOne tbc)

  3. Technical preparations • 4 staff certified for CI installations (May) • 2 x DBA • 2 x server support • Preliminary Technical Requirements review held in August • Test environment • established for 2-tier, Citrix client • N-tier and DP’s still to do

  4. Software installation • Release 4.0 installed successfully by beginning of August • small delay due to obtaining license key • larger delay due to substantial unfamiliarity, user accounts having no access etc • Patch 1 applied successfully in late August

  5. Initial training and consulting • 3 day training/consulting September 4-6 • Roles and workplaces • Reporting options • capability of searching (including grids, grouping, publishing) • use of alerts for ‘need to work on’ items • integration of reports into workplaces • User help options • local help files • personal workflow • Next consulting 8-9 November

  6. Live dates so far.. • Plan A : April/May 2007 • Plan B : October 2007 • mooted March 2006 • confirmed June 2006 • Plan C : April/May 2008 • confirmed September 2006 • Plan D : ???

  7. Main project goals • Focus on user processes • well managed transition for users (staff/students) • better system support for user procedures • user documentation (3rd attempt) • just-in-time training and support • Better reporting model • grids, alerts, XLOne, Crystal • Anticipate down-sides and prepare users • Additional functionality without risking main goals

  8. Immediate tasks • Test pages as delivered • pick up usability issues as early as possible • gain familiarity during testing • ‘catch up’ by patch 3 delivery timeframe • Work on infrastructure-type issues • distinguishing databases • new system-wide defaults, function keys • ‘Finalise’ project plan • confirm approach to be followed • establish staffing requirements • Main project commences March 2007

  9. Early issues/concerns • Software delivery • 4.0 very limited delivery • 4.1 much less than previously expected • too hard to plan on at this stage • Software design • Extent of involvement to date, or lack of • Roles/workplace design • not clear how to fine-tune access (eg special security codes) • N-Tier model • impact on reporting via DP

  10. Questions

More Related