Each Project follows the same project phasing:
Assess phases (Analysis),
Design, Project Planning, Audit, Architecture, etc.);
Build phases (Development, Configuration & Implementation, User Testing & Acceptance, Preparation for Deployment & deployment, etc.);
Run phases (Post Go Live, Maintenance, Support, etc.).
A careful assessment phase is a key success factor to start an IT project. Moving too quickly to design and implementation creates the risk of starting the wrong project.
The assessment phase can range from a simple meeting with System in Motion’s experts, to a full assessment mission, depending on the size and complexity of the target project. This important milestone must establish clearly business objectives, limits, constraints, and all key factors to take into account.
The assessment phase is the right time to get all stakeholders around a common set of business goals. During this phase, stakeholders must concentrate their energy on identifying:
business issues the project must solve,
key indicators the project must reach,
The assessment phase will mainly consist in interviews with key users and management team designed to identify the above set of objectives. It is of course a time for System in Motion to give expert recommendations, review relevant Business Cases, and in general help the customer to better define their project.
System in Motion’s methodology guarantees a thorough and detailed assessment of all key elements, without missing a critical aspect of the project, for a smooth transition to the design phase.
Based on a clear definition of the objectives, as defined in the assessment phase, the design phase lists all necessary technical and functional components to assemble into a clearly defined Software Architecture. The design phase will also prepare and plan the specific requirements to take into account, and propose implementation solutions to address each requirement.
The design will also review all critical elements associated with business success factors, such as deployment strategy, performance, scalability, response time, etc.
Very often, during the design phase, System in Motion’s architects and analysts will propose different options matching the business requirements, with pros and cons, to give the project owner all the elements to make the right choice.
Depending on relative priority, cost and delay of implementation, the business requirements are grouped into phases. Phases are designed to provide the optimum value in the shortest time, to reach the highest return on business improvements. Later phases will be planned to bring incremental benefits. The planning also takes into account business related deadlines, and external constraints.
System in Motion will use the clear understanding of the business objectives, gathered in the assessment phase, combined with its expertise in technology, to design a pragmatic and reliable solution for its customers’ requirements.
Once the project owner has decided on the various options, and validated the project phasing, System in Motion puts in place a full development team, to build the target solution.
During the build phase of the project, System in Motion actively communicates on the progress of the project. Regular checkpoints are scheduled with the customer’s Project Manager, to review all project tasks, dependencies and adjustments needed. This open and uninterrupted communication is critical to keep the project in line in terms of timeframe, budget and features. This also allows reacting quickly and efficiently to external changes which can influence the outcome of the project.
When applicable, early versions of the solution, with a limited feature set, are demonstrated to key users to get early feedbacks. This approach, for a large project, allows for small adjustments and progressive user adoption. It makes it possible to detect missing requirements, identify priority changes, while keeping the project at full speed, and reach the deadline.
When a version is ready, packaged, and validated by Quality Assurance team, key users are trained, and then invited to review the version. Always looking at the system from business processes point of view, the final validation guarantees that the solution is fully operational, and matches all requirements in scope.
The solution is then transferred into production, and all users are trained. After a short period of post production, the project moves into a maintenance phase.
Once the solution is used in production by all users, System in Motion continues to provide services. It is critical that the solution is kept in working order, and most often, it is also important to continue adjust the system to new requirements, changes in business processes.
Within the context of maintenance, customer can choose between slow, carefully identified, enhancements, or a more dynamic, constant adjustment to businesses changes, and search for process improvements.
In all cases, it is critical to continue upgrading the Core solution, and for all related modules to benefit from new features, and continue to get support. Small enhancements help users in their adoption of the solution. System in Motion uses online collaborative tools to constantly gather feedbacks from users, and regularly meets with customer’s Project Manager to plan coming releases of their solution.
System in Motion offers several Maintenance Options to fit each customer’s profile and adapt these offers to the outcome their customers want.