Home > The ONE Solution > Implementation Methodology

Implementation Methodology

Blueshift has a best-practice, proven implementation methodology. Below is a typical implementation methodology, however this is adapted to suit every implementation.

Phase Timeframe Details Blueshift Deliverables Customer Deliverables

Project Initiation

(Onsite consultant(s) as necessary)		 2-4 weeks
  1. Contract Negotiations
  2. Top Level Requirements lock-in and time estimation
  3. Project Plan
  • Contracts
  • Time Estimates
  • Project Plan
  • Final Top Level Requirements - prioritised
  • Contracts signed

Implementation Sprint Cycles

(Dedicated development resource of approx 50 hours per week, 1 consultant on-site 1 day per week)		 Approx 3-6 months 4-6 week sprint development cycles, each consisting of (top level):
  1. Detailed requirement lock-in
  2. Development
  3. Alpha and Beta testing
  4. User / Technical Manual updates
  5. User Acceptance Signoff
  • Alpha Testing and Beta Releases
  • User / Technical manual updates
  • Detailed requirements
  • Beta Testing
  • User Acceptance Signoff

User Training

(2 onsite consultants)		 2-3 weeks User and Power User Training Training Sessions User Availability for Training

Go-Live

Run-down

(1 onsite consultant 1 day per week)		 2-3 months Post go-live high-availability dedicated support, to react quickly to any problems or user queries High availability for support and training questions Necessary level of remote access to facilitate support

Support

(1 onsite consultant 1 day per fortnight)		 Ongoing Ongoing support and maintenance SLA deliverables All relevant information required to fulfill the SLA