Jove
Visualize
Contact Us
JoVE
x logofacebook logolinkedin logoyoutube logo
ABOUT JoVE
OverviewLeadershipBlogJoVE Help Center
AUTHORS
Publishing ProcessEditorial BoardScope & PoliciesPeer ReviewFAQSubmit
LIBRARIANS
TestimonialsSubscriptionsAccessResourcesLibrary Advisory BoardFAQ
RESEARCH
JoVE JournalMethods CollectionsJoVE Encyclopedia of ExperimentsArchive
EDUCATION
JoVE CoreJoVE BusinessJoVE Science EducationJoVE Lab ManualFaculty Resource CenterFaculty Site
Terms & Conditions of Use
Privacy Policy
Policies

Related Experiment Videos

The second time around: reaching for the right package.

C J Weissman

    Fund Raising Management
    |September 6, 1991
    PubMed
    Summary
    This summary is machine-generated.

    Replacing software requires careful planning. Asking key questions upfront saves significant time, money, and reduces potential issues during implementation.

    Related Concept Videos

    You might also read

    Related Articles

    Articles linked to this work by shared authors, journal, and citation graph.

    Sort by
    Same journal

    2003 non-profit software guide.

    Fund raising management·2003
    Same journal

    American Red Cross releases September 11 report.

    Fund raising management·2003
    Same journal

    Evaluating and choosing a fund-raising database program.

    Fund raising management·2003
    Same journal

    The non-profit sector and the market: opportunities & challenges.

    Fund raising management·2002
    Same journal

    Is it feasible?

    Fund raising management·2002
    Same journal

    How to make an impression in a competitive market.

    Fund raising management·2002
    See all related articles

    Area of Science:

    • Software Engineering
    • Information Systems Management

    Background:

    • Software package replacement is a common but complex organizational process.
    • Inadequate planning can lead to project failures, budget overruns, and user dissatisfaction.

    Purpose of the Study:

    • To identify critical questions that must be addressed before initiating a software package replacement.
    • To provide a framework for successful software transition.

    Main Methods:

    • Qualitative analysis of common pitfalls in software replacement projects.
    • Development of a checklist of essential pre-replacement inquiries.

    Main Results:

    • Key questions span functional requirements, technical compatibility, vendor support, data migration, and user training.

    Related Experiment Videos

  • Proactive questioning mitigates risks associated with system integration and operational disruption.

    • Conclusions:

    • Thoroughly answering pre-replacement questions is crucial for project success.
    • Strategic planning minimizes post-implementation problems and maximizes return on investment.