Get A Free Consultant
Efficient Hours or Agile with Budget Control (Recommended)
Overview
Initial high-level scope, estimate, and budget are defined.
Initial high-level scope, estimate, and budget are defined.
Initial high-level scope, estimate, and budget are defined.
Initial high-level scope, estimate, and budget are defined.
Advantages
Agile Flexibility. Frequent deliveries and demos of the product allow the client to change the requirements, incorporate new ideas or pivot at any time.
Full Collaboration between the client and the team — creativity, proactive exchange of ideas, brainstorming. The team is focused on how to create the best possible product for the available budget.
Maximum Cost Efficiency. We provide the best resources for a specific task. Only efficient hours within the provided estimates are billed. Outages and inefficient work are not billed.
Transparency and Pay as You Go. The progress and costs are demonstrated and reported on a weekly basis. The client pays only for what he has reviewed and approved.
Fixed Price
Overview
Initial high-level scope, estimate, and budget are defined.
Initial high-level scope, estimate, and budget are defined.
Initial high-level scope, estimate, and budget are defined.
Initial high-level scope, estimate, and budget are defined.
Advantages
Exact scope and functionality of the project are fixed in the contract and can’t be changed.
Minor client involvement is needed during the project implementation phase.
This model works reasonably well for the enterprise clients who are able to specify in detail what exact software they need
Initial high-level scope, estimate, and budget are defined.
Disadvantages
Long preparation/analysis phase is required to elicit, document and fix all the requirements.
Higher price – the risks buffer is included in the price.
Doesn’t work well with agile approach – the team will deliver exactly what is specified in the contract.
Complicated process of changing the requirements that leads to signing an addendum to the contract.
Outstaffing / Development Team as a Service
Overview
The client sends qualification requirements for certain positions.
Itexus sends CVs of the candidates fitting the requirements.
The client interviews and accepts/rejects the candidates.Pre-agreed monthly rate is billed for the accepted candidates.
Itexus helps organize work in the most efficient manner, sets up development environment that can be secured and integrated into the client’s infrastructure.
Advantages
Full control. The client has a full control over the team and processes, can integrate new engineers with an existing team.
No hiring costs. No need to hire HR managers, recruiters or pay an exorbitant amount of money to recruiting agencies
Flexible scaling and descaling. The client can quickly scale the team up and down depending on the workload.
On-demand resources.The client is able to attract the resources with a specific skills part-time or full-time to complete a specific project task.
Disadvantages
Requires strong project and technical management on the client’s side — very skilled managers to supervise the remote developers.
Possible miscommunication.
Higher rates. Very often such projects require more experienced and expensive engineers with excellent communication skills to be able to work efficiently directly with the client..
Itexus collective expertise is not fully utilized, only individual expertise of the selected engineers.
Efficient Hours or Agile with Budget Control
Fixed Price
Outstaffing / Development Team
Size of project:
Requirements:
Flexibility:
Client’s involvement:
Budget / Rate:
Any
Evolving
Flexible
Average
Strictly Controlled
Any
Defined
Non Flexible
Minor
Fixed
Any
Evolving
Flexible
Full
Fixed
Think What Cooperation Model to Choose?
Contact Us
From Idea to Ready-to-Market Product
Initial Consultation
Discovery Phase
Design
Architecture
Implementation
Testing / QA
Cloud Setup / DevOps
Going Live
Post Production Support
Initial Free Project Analysis/Consultation
Usually we start projects with a free consultation phase during which we collect and document the initial high-level requirements, perform feasibility and risk analysis, analyse potential integrations and competing products, design high-level architecture, recommend technology stack, create the workload and cost estimate. This phase lasts about one-two weeks. It consists of several workshops with an Itexus business analyst and a software architect and results in a creation of the initial project documentation and a proposal. Once the budget, scope, and architecture are approved and the contract is signed, the project starts.
Discovery Phase
If the client has only a high-level idea or the project is complex we usually recommend starting with a more detailed Discovery / Requirements Analysis / Architecture design phase.
We prepare a detailed documentation and thoroughly think over the architecture of the project. The discovery phase is needed to prepare everything before the development and set up a budget. Besides all unclear moments are revealed and covered. Thus it’s possible to find out the exact cost of the final product development and exclude force majors during the development phase. The scope of the project is split into sprints. Requirements are specified on the Use Case or User Story level.
Additionally we create UI mockups of the main user screens, combine them into a clickable prototype and involve the UI/UX designer to create graphical design of the UI on screen-by-screen level.
UI/UX Design
Once the requirements and user journey map are identified and fixed,the UI/UX design phase starts. We pay attention to all principles of visual design such as unity, balance, hierarchy, proportion, emphasis, and contrast. On each principle, there are elements, like line, shape, text, color that we should play right and attractive for users. The right design helps users understand the product. It will also build a good first impression that furthermore build the trust. And to make it right and more beneficial for the client in terms of attracting customers and the usability designers work together with our business analysts. All designs are compliant with the latest design guidelines from Apple and Google.
Architecture Design
Our approach to architecture design starts with identifying and prioritizing the key non-functional requirements such as:
simplicity/cost of development
security
performance
scalability
Some requirements like scalability and the cost of development may conflict with each other. The architect’s job is to identify the technologies and the architecture of the future system that will be an optimal balance of the requirements, documentation and simplicity of future usage by any development team. Well thought-through and documented architecture allows us to deliver high quality software in less time.
Implementation
Our development process is based on the Scrum process adjusted for remote collaboration.
The Software is delivered in two-week sprints starting with core functionality with a potentially shippable and shapeable product increment delivered at the end of every sprint.
Every sprint is followed by the demonstration of the results to the client, client’s feedback is collected and incorporated in the subsequent sprint.
The code is covered with unit tests and goes through a code review process in the git or github code management flow.
CI/CD (Continuous integration and delivery) practices are used in conjunction with automated and manual testing to ensure the quality.
DevOps Implementation
Itexus DevOps engineers are usually involved in every project part time and they:
Setup development, test and production environments in the chosen cloud platform.
Organize backup, automated monitoring, security and fault tolerance of the production infrastructure.
Automate continuous integration, continuous deployment and environment provisioning processes.
And perform other, project specific DevOps activities.
Quality Assurance
Our QA approach is based on the well-known test pyramid pattern.
The code is covered with unit tests.
Regression testing is automated with service-level and UI tests.
Manual QA team is working mostly on testing of the new features and documenting the test cases for future automation.
All defects are logged and prioritized with Jira or another defect tracking system.
The development team and the client receive daily reports of all newly identified and currently open defects.
All automated tests are executed after every code change as a part of the CI/CD process.
Recent Projects
Algorithmic Intraday Stock Trading System – Stock Trading Bot
Wealth Management Platform
Wealth Management Platform
Reasons to Choose Itexus
Contact Form
Drop us a line and we’ll get back to you shortly.
Office
United State
Poland