The Implicit Difference
Proven Track Record
We believe that it's best to let our clients speak for themselves. For over fifteen years,
Implicit has been building and nurturing long-term partnerships with our clients by being
responsive to their needs and delivering the highest quality software. The majority of our
business is from repeat customers and referrals. We have clients that we have been working
with for over ten years on many different projects.
The Best and the Brightest
We strongly believe that our success is directly tied to our customers' satisfaction which
is tied to the quality of our software products and support services which are directly
tied to the quality of our team. Therefore, our philosophy is very simple:
- Hire the best and the brightest
- Compensate them well
- Keep them happy and motivated
- Keep them challenged
- Provide an environment where they can thrive
Clear Expectations Result in a Superior Product
Every project involves a multitude of potential risks. A well-defined development process
makes it easier to manage risks. Before we start the project we dedicate ample time to discuss
and clarify the customer's requirements and develop a very detailed and comprehensive Statement
of Work (SOW). Very often the SOWs include prototype screenshots of how we envision the user
interface and charts to specify the data flow and the functionality. This process ensures that:
- Your business goals and priorities are well understood and documented
- Software functional requirements are clear and documented
- Our commitments are in accordance with your expectations
- Roles and responsibilities are clearly defined
- Deliverables are well defined and there is mutual agreement that the goals are achievable within the given constraints of schedules, budget and resources
Disciplined and Methodical Approach to Software Development
A key factor in the success of any software project is a disciplined and methodical management
of the development process. Implicit has extensive experience in managing large and complex software
projects as well as short-term "quick response" projects under tight schedules.
There is certainly no "one-size-fits-all" approach to managing software projects. Each customer
has a unique set of requirements and constraints. However, there is a common process we employ
to ensure the success of each project and the delivery of high quality software on-schedule
and under the budget constraints of the customer.
Each project is assigned a project Manager who is the Customer's single point of contact
for project coordination. The role and duties of the project manager is to:
- Plan and manage the project
- Coordinate and schedule appropriate engineering resources for the project
- Provide project communication with customer
- Maintain consistency of project development, standards, procedures, and processes
- Coordinate the efforts of Implicit’s team with those of Customer's project personnel with the goal of developing a cohesive and responsive project team
- Monitor project activities
- Review progress against the plan
- Interact with Customer Project Manager to coordinate and conduct regularly scheduled Status Meetings and prepare and distribute Status Meeting minutes which outline progress against the plan, open issues, and action items
- Communicate/escalate, within Implicit, any technical or business issues relating to the project Conduct Project Reviews (checkpoints during the project life cycle). The reviews help identify emerging problems and recommend corrective actions.
Evolutionary Approach to Software Development
Our experience has taught us that very often customers change their requirements throughout
the development process. Once customers receive the first few milestone deliveries, they go back,
re-analyze and re-adjust their requirements. New requirements are added and others are removed or modified.
It's a natural progression of developing a new product and one that is hard to avoid. To minimize the
impact of changing requirements, Implicit has adopted "Agile Software Development" methodology.
Instead of setting major milestones for deliveries of substantial functionality, we break down the
process into a sequence of much shorter milestones so we have an opportunity to get the customer’s
feedback and re-adjust requirements if necessary.