1 / 10

Crafting a Successful Enhancement Request

Crafting a Successful Enhancement Request. Larry Woods NAAUG 2003 Iowa City, IA. Truisms. “No system is perfect to begin with” “No system will ever be perfect no matter how much you tweak it” “If you’ve lived without it this long, you may not need it after all”

jryder
Download Presentation

Crafting a Successful Enhancement Request

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. Crafting a Successful Enhancement Request Larry Woods NAAUG 2003 Iowa City, IA

  2. Truisms • “No system is perfect to begin with” • “No system will ever be perfect no matter how much you tweak it” • “If you’ve lived without it this long, you may not need it after all” • “Most users try to automate their manual processes – step for step, function for function”

  3. Definitions • Enhancement • An added function or feature • An added data field • A better way to do something • Bug • System generates erroneous information • System does not function according to documentation • System is inconsistent in the way it handles a common function (borderline!) • Know the Difference!

  4. Definition of Success • Gets ranked (NAAUG EGs) • Gets pointed (Ex Libris) • Gets voted (NAAUG Membership) • Gets developed correctly (Ex Libris) • Gets used (Everybody) • Makes life easier for users • Helps Ex Libris sell new systems

  5. How to get it Ranked • Communicate with peers • Convince EG members of its relative importance • See if your idea can be generalized • Make sure it solves a universal problem

  6. How to Get it Pointed • Make sure it is understandable to EL staff • Make sure it is specific enough for them to estimate the work required • Make sure it is general enough to be worth doing

  7. How to Get it Voted • Lobby your colleagues?

  8. How to Get it Actually Developed • Be willing to wait three years • Ask to see progress reports on the development • Get EGs to test new feature and “accept” it

  9. Make Sure it Makes a Difference • “Enhancements” that aren’t really used by anyone • To “Make a Difference” an enhancement should • Improve productivity • Improve accuracy • Improve system salability

  10. The Process • Enhancement Groups appointed (May-June) • EGs come up with top five requests (June-Nov) • EG Chairs meet with EL staff (Dec) • EL assigns points to each request (Jan-Feb) • EGs check for clarifications (March) • Membership votes (April) • Final submission of requests getting top votes to EL (May) • Delivery of enhancements (two-three years later!)

More Related