How we work
Due to the usage of common processes, methodology and management disciplines along with the well-tested PM tools, we ensure consistent high-quality performance in every project we work on.
Project Management
Effective communication between customer and project team facilitated by exceptional Project Management are the most important success factors for all projects. Due to our extensive international experience, we have developed a secure and effective communicational infrastructure and a clearly-defined framework for Project Managment processes.
The central point of *instinctools processes and communication is our own Project Management (PM) intranet called IFOS – an efficient controlling and communication tool.
Each customer gets an access to his/her project through these tools and, thus, is directly involved in the project work. Project artefacts become available to all the parties involved (customer, project manager and development team). We use IFOS as a repository for all important documents related to the project which ensures that nothing is lost in the process of development. IFOS allows scheduling meetings, collecting requirements, seeing checkpoints, tracking bug reports, asking questions and making suggestions directly to each other regardless of time and location. As a result, we have a single point of communication and accountability for all project matters.
Our Development Process
Being a customer-oriented company, we do our best to make our processes as clear and transparent for you as possible. We adhere to the best practices in the industry to give you a predictable quality result that you expect from your vendor.
Usually we build our work on next process:
Business Consulting
This phase helping organizations improve their performance through the analysis of existing business problems and development of solutions and plans for improvement.
Requirement Collection and Analysis
The main aim of this step is to collect and structure clear, complete, consistent and testable requirements on a business level which are sufficient for building a system design and TLPD (Top Level Project Description) document creation. Analysis of requirements includes classification and prioritization of requirements from customer point of view.
High-Level Design
The main aim is to process all registered User Stories, transform business requirements into technical requirements, develop one or more technical solutions to defined problems, estimate needed efforts, create top level plan and finally come up with top level project specification and offer.
Detailed Design phase
The main aim of this phase is to prepare required infrastructure for the iteration implementation. Detailed design phase of the whole project coincides with detailed planning of first iterations. All further iterations start with detailed planning of the upcoming iteration which consists of the same activities but with smaller scope.
Implementation phase
The main aim is to implement software system according to scope, time and quality defined for current iteration.
Correction Phase
The main aim is to verify the end-to-end functionality of the system in satisfying requirements and specifications planned for the current iteration.
Quality Gate
The main aim is to deploy implemented functionality on integration server, demonstrate that the system meets its requirements in the operational environment and get customer feedback.
Post Analysis
The main aim is to streamline self-reflection, help managers and developers to reflect upon the work completed and facilitate knowledge sharing.
Maintenance and Support
The main aim is to organize effective support process for delivered functionality in case it used in production mode and isolate further development activities from support and defect management efforts.