Your SlideShare is downloading. ×
0
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
You're Live, Now What?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

You're Live, Now What?

341

Published on

A presentation by Emily Almond of Georgia PINES for the Evergreen International Conference 2009.

A presentation by Emily Almond of Georgia PINES for the Evergreen International Conference 2009.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
341
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. You’re Live… Now What? How to Build a Support Infrastructure to Maximize your Investment in Evergreen Emily A. Almond PINES Software Development Manager Georgia Public Library Service
  • 2. What’s Your Driver? <ul><li>TIME </li></ul><ul><li>How long to define requirements? </li></ul><ul><li>How long to Develop X? </li></ul><ul><li>RESOURCES </li></ul><ul><li>How much $ </li></ul><ul><li>How many developers? </li></ul><ul><li>FT? PT? Contract? </li></ul><ul><li>What’s going on in the open-source community? </li></ul><ul><li>What’s the cost-benefit of monitoring development there? </li></ul><ul><li>SCOPE </li></ul><ul><li>What is the end goal? </li></ul><ul><li>How do we define functional? </li></ul>
  • 3. Roles &amp; Responsibilities – Who Has the D? Using the RAPID method to determine who does what PINES TEAM EQUINOX <ul><li>Schedule Site Visits and Reports </li></ul><ul><li>Set prioritization of PINES development issues </li></ul><ul><li>Monitor allocation for development to insure accurate reflection of PINES library needs. </li></ul><ul><li>Updates to PINES page </li></ul><ul><li>Evergreen-related policy, process, software updates to PINES libraries </li></ul><ul><li>Updates to PINES documentation </li></ul><ul><li>Govern Help Desk </li></ul><ul><li>Define allocation of funds per category of development and/or support. </li></ul><ul><li>Answer Help Desk Tickets (working with the PINES team @ GPLS). </li></ul><ul><li>Work with Emily to prioritize development. </li></ul><ul><li>Develop software according to priorities communicated by the PINES team. </li></ul>
  • 4. Defining Scope <ul><li>Define Approach to Software Development: (see handout) </li></ul><ul><li>Software Development LifeCycle vs. Product LifeCycle </li></ul><ul><li>Triage issues: </li></ul><ul><ul><li>Policy | Process | Software </li></ul></ul><ul><li>Software: </li></ul><ul><ul><li>Criteria for Defining Issues </li></ul></ul><ul><ul><li>Informs where issues belong in development cycle </li></ul></ul>
  • 5. Communicating Scope Pulling together issues from emails, listserves, site visit logs, and existing docs and spreadsheets: <ul><li>High-level graphical timeline </li></ul><ul><li>Timelines filtered from spreadsheet for use by working groups </li></ul><ul><li>Updated spreadsheet to Directors on regular basis </li></ul>
  • 6. Time to Build Support Infrastructure November 2008 March 2009 <ul><li>Define Approach to Software Development: (see handout) </li></ul><ul><li>Software Development LifeCycle vs. Product LifeCycle </li></ul><ul><li>Triage issues: </li></ul><ul><ul><li>Policy | Process | Software </li></ul></ul><ul><li>Software: </li></ul><ul><ul><li>Criteria for Defining Issues </li></ul></ul><ul><ul><li>Informs where issues belong in development cycle </li></ul></ul><ul><li>PINES team adopted development approach, resulting in: </li></ul><ul><li>New Development Roadmap </li></ul><ul><li>New Help Desk Workflow </li></ul><ul><li>Testing/Training Environment </li></ul><ul><li>Holds Cleanup </li></ul><ul><li>New Communications Model </li></ul><ul><li>--- </li></ul><ul><li>Training Cluster live as of 02.09.09. </li></ul>
  • 7. Time for Testing Took release through it’s paces on the Test System:
  • 8. Time for Testing Developed Report Card on Major Features / Fixes:
  • 9. Tapping Existing Resources November 2008 March 2009 <ul><li>Working Groups Mission: </li></ul><ul><li>Establish a baseline on how the specific module/functionality actually operates in the existing version of Evergreen. </li></ul><ul><li>Discern the difference between process, policy and software solutions. </li></ul><ul><li>Document optimal module functionality within a future Evergreen release and develop a list of requirements. </li></ul><ul><li>Become the de facto module testing group, through which all new  development would be filtered from the PINES library side of the development process. </li></ul>Able to discern quickly that there was a break between understanding of software and following of process. Removed Cap on Holds Pull Lists &amp; Implemented a HOLDS AMNESTY RESULTS: December 2008 – 4500 Unfilled Holds January 2009 – 890 Unfilled Holds March 2009 – 20 Unfilled Holds
  • 10. Communicating to Stakeholders November 2008 March 2009 Site Toolkit Site Visit Logs : (see handouts) Resolution Tracker: all issues assigned to individuals on PINES team for resolution and/or follow-up 11.11.08 – Athens 11.12.08 – Southwest Georgia 11.13.08 – Dougherty 11.13.08 – Ohoopee 01.27.09 – Lee County 02.16.09 – Mountain Regional All issues either filed through Help Desk or on development spreadsheet. Several reported issues resolved in Release 1.4.
  • 11. Communicating to Stakeholders <ul><li>Utilize public PINES page as primary communications channel for: </li></ul><ul><li>Software Development Timeline </li></ul><ul><li>Site Visit Logs </li></ul><ul><li>Working Group Reports </li></ul><ul><li>PINES Updates </li></ul><ul><li>Resources </li></ul><ul><li>Training Materials </li></ul>

×