Our Methodology for Software Systems

Business requirements and technology change over time. Outdated software systems and poorly integrated sub-systems drag on your business every day. We have consulted on and managed transitions to modern, efficient software systems in several organisations. Below is a typical outline plan, which we always adapt to your requirements. The methodology begins with an accurate systems analysis. Then it moves carefully through the change management stages.

Intelmaven Bernard Grinberg System Analysis

Why Changing Your Software Systems Matters

Change is vital for the health of any enterprise. Without it, organisations stagnate and drift away from success and prosperity. Change can be transformational, incremental, or a blend of the two.

However, most people instinctively resist change. It means leaving their comfort zones and learning new methods and skills. Consider an employee who sticks with old, inefficient ways instead of newer, faster ones. What is comfortable for the employee is often not best for the business.

To implement change, you need good processes. First comes the audit and systems analysis. After that, we provide change management and project management through every implementation stage. Experienced external consultants suit these steps well, because they act with objectivity and impartiality while staying sensitive to the human side of change.

 

  1. Audit & Analysis – interview stakeholders, review and document:
    • Current usage – data fields, data flows, reports, processes, documentation
    • Management structures
    • Sub-systems integrations
    • Security – internal, external
    • Support – internal, vendor
    • Future requirements in all of the above
  2. This process results in an agreed Scope or Statement of Works (SOW) as appropriate.
  3. Determine whether the use of the current systems can be improved, or the systems need replacement.
  4. If the current systems can be improved, prepare Project Plan with agreed steps and outcomes, likely coordinated with current vendor(s).
  5. If replacement is required, prepare Request for Quotation based on the SOW and draft Project Plan.
    • Identify potential vendors
    • Send out RFQ
  6. Evaluate vendors
    • Technology
    • References
    • Support
    • Implementation
    • Pricing
    • Accounting & other systems integration
  7. Short list vendors
    • Demonstrations
    • Follow up Q & A’s
    • Update SOW and Project Plan
    • Choose vendor
    • Negotiate the terms with the vendor, including any customisations if required.
  8. Implementation
    • Project plan, including transitions
    • Training plan
    • Hardware implications and changes
    • Set up
    • Data import
    • Testing
    • Go live
    • Follow up

    • Services engagement estimates – project management
      • Phases 1 -3 ( month 1): three days on site, then equivalent three days follow up (phone, Zoom/Teams, emails, documentation, progress reporting)
      • Phases 4-7 (month 2): three days equivalent 
      • Phase 8 (months 3-5): two days equivalent per month