How a Project Runs
Seven stages. None of them optional, and the last two are the ones most often skipped elsewhere.
Planning
Define requirements, dependencies, scope and implementation approach, including what is explicitly out of scope.
Design
Develop a practical technical solution aligned with the organisation's requirements and existing environment.
Implementation
Configure and deploy the required technology, in a sequence chosen to limit disruption.
Migration
Move services and systems while controlling disruption, with a defined rollback position at each step.
Testing
Validate the solution before operational handover against the requirements agreed at stage one.
Documentation
Document the resulting environment for future support, maintenance and reference.
Handover
Transition the project into operation with support arrangements, ownership and next steps confirmed.
Typical Projects
The work most often comes in one of these shapes:
Infrastructure upgrades
Network implementations
Cloud migrations
Microsoft 365 implementations
Server deployments
Firewall projects
Backup and recovery projects
Security implementations
Technology refreshes
If your project is not on this list, it is still worth a conversation — the delivery method does not change with the technology.
What You Get at Handover
A project is finished when you could support it without us:
A working solution, tested against the agreed requirements
Documentation of the environment as it now stands
Configuration details recorded, not held in someone's memory
A defined support arrangement, whether ours, yours or a third party's
A record of what was deliberately left out of scope, and why
Known limitations stated rather than discovered later
No lock-in. If you want another provider to support what we built, the documentation is written so they can.
Not Sure the Project Is the Right One Yet?
Sometimes the project that has been proposed is not the project that is needed. An assessment establishes the current state first, so the scope is based on the environment rather than on an assumption.
If the assessment confirms the plan, you have lost nothing. If it does not, you have avoided implementing the wrong thing.
Related Services
Where projects most often lead:
Cloud & Infrastructure
Design and implementation of cloud, hybrid and on-premises environments.
Managed IT Services
Ongoing operational responsibility once the project is in service.
Microsoft Services
Microsoft 365, Azure, identity and endpoint implementations.
Planning an IT Project?
Talk to Felix Core about your requirements, timeline and implementation needs.