FMX Solutions mission goes beyond the
simple analysis of your needs and requirements. We
believe that it takes a strong focus on interaction and
feedback to make sure that not only you requirements
have been properly translated into your Scope of Work
and Specifications documents, but more importantly that
you, in turn, fully comprehend the solution to be
delivered in its current and future implications.
It is our consultants’ main goal to
help you select the right IT options not only for the
present but also for the future.
We ensure that teamwork is at the heart of our analysis
processes so that we work together building your IT
infrastructure for the future. Our analysis methodology
follows proven steps:
• Discovery workshops, (initial assessment) are
conducted by FMX Solutions in order to elaborate and
understand the customer’s functional requirements (functional
analysis). To this effect, FMX Solutions conducts a 1 to
2-day workshop with the customer’s designated staff in
order to describe these requirements. FMX then writes up
and delivers a document summarizing these requirements
for validation by the customer;
• Scope of work confirmation: when discovery
workshops have been completed, FMX Solutions conducts a
review of initial scope of work with the customer and
adjust according to the findings if needed;
• Initial recommendation: in light of the defined
requirements, FMX Solutions will recommend high-level
path to a solution, that may entail the use of a
software platform or the adjustment of an existing one.
In this case and at that time, a training of the project
management team is conducted in order for the customer
to understand how the solution works and be prepared for
the specifications workshop;
• Specification workshops, when requirements,
scope of work and software platform have been validated,
FMX Solutions designs a specification document that will
be a translation of the functional needs into the
customer’s environment. This phase usually involves a 2
to 3-day workshop with the project management team and
is followed by the write-up of the specification
document and an implementation plan;
• Prototyping and/or proofs of concept: we
strongly believe that the analysis phase wouldn’t be
complete without the creation of a prototype. Hands-on
testing is critical to validate the platform and
processes. It is also a critical phase to make sure that
all stakeholders (executives, end-users...) adhere to
the solution that will be implemented;
