Our Engagement Methodology

Engagement Methodology Diagram

• Briefing              – Confirm project requirements and engagement process
• Initiation             – Kick-off meeting to establish success criteria & outline plan
• Analysis             – Business & Requirements Analysis – What is needed and why?
• R & D                  – Application design and identification of supporting technologies
• Implementation – Develop / Integrate / Configure solution
• Go-Live               – Support acceptance and go-live process


Our prime consideration is your success!

We can engage at any stage of our Engagement Methodology and don’t have to start from the beginning if you’re part way through already. Budget projections / approvals can be phased to fit your business and we can work collaboratively with your own in-house resources. We value your own technical and industry specific expertise. You can disengage at any stage boundary and pass the baton on. We hope you will stick with us, but we won’t be offended. 

Briefing Session

A briefing session is typically a call or online meeting.
Primary objectives are to confirm that:

• Our profile and knowledge is of value to the project
• Our approach and risk management strategy is a good fit
• Budget has been allocated and timescales are broadly achievable
• We can support the purchaser’s decision making process


The initiation phase includes a half or one day kick-off workshop to:

• Explore the current state of the systems and processes being used
• Discuss the company strategy / programme for digital transformation
• Identify the key outcomes and success criteria for the engagement
• Agree the outline plan for the project with key milestones


The analysis phase involves going into depth to discover and verify:

• The current business challenges and opportunities
• The current system issues, functional gaps and future potential
• A detailed and prioritised list of requirements
Central User-Stories and/or Use-Cases
• Determine high level expectations regarding technological approach

Research & Design

The research and design phase involves:

• Develop further descriptions of how users achieve specific goals
• User-Stories / Use-Cases (for all ‘must-have’ and most ‘should-have’ requirements)
• Develop high level functional design (functions, screens and integrations)
• Identifying candidate technologies and services (open source / proprietary)
• Define one or multiple development approaches; with recommendations
• Present proposed phased implementation schedule and milestones

Implementation & Deployment

The implementation and deployment may be subdivided into separate ‘sprints’; adopting some aspects of ‘Agile’ development with each ‘sprint’ consisting of:

• Planning: Review and confirm the requirements to develop
• Development: Parallel design, implementation and testing
• Review: A demonstration of completed features
• Retrospective: An opportunity to review and refine the process
• Latter Sprints Will Usually Focus On Quality & Non-functional Requirements

Go Live

This will involve:

• Reviewing the system for functional and operational readiness
• Planning the transition of business users to the new system
• Confirming that the necessary support provisions are in place
• A stakeholder go/no-go decision. (no-go would result in another sprint)
• Directly supporting users to ensure they are able to work effectively
• A post go-live review
• A maintenance schedule would be agreed
• A regular stakeholder review process would be agreed

Post Go-Live

Post go-live updates may be agreed to:

• Make minor refinements to existing features (and correct bugs)
• Include features which did not make the first release
• Expanding system scope to include new / emerging requirements

Significant enhancements / growth may involve returning to earlier phases, depending on the scope and coverage conducted during earlier iterations.

Engagement Methodology Diagram with arrows