Our Approach
The first thing you need to know is we are always interested in long-term relationships with our customers. Projects big or small, you can always rely on our support and being there for you. Our process is pretty straightforward. It consists of multiple consequent steps and may have as many iterations as it is needed. Here are the steps.
The first meeting
One of the most exciting things in our business is meeting new people! That is both inspiring and useful for both sides. During the first meeting, we would like to learn about you, your business, and the challenges you are facing.
The agenda for this meeting is:
- Get familiar with each other a bit
- Learn about your business
- Learn about your challenges and figure out if we can be useful
- Schedule a discovery call within the next 5 business days
During this meeting we are not going to:
- Excruciate you with sales pitches
- Show you slide decks about how awesome AgileVision.io is (here is the link to one in case you would like to check it).
we are moving directly
to the discovery phase.
The discovery phase
The discovery phase consists of as many meetings as we need to understand your business, challenges, and goals better. During this exciting period in our relations, we are going to interview you and ask various questions related to the project. Usually, from our side, we invite business analysts, UX/UI designers, technical leads to these meetings.
The final purpose of the discovery phase for us is to prepare a proposal for you. In parallel, we are also going to share with you our contract example, so you can verify the legal side of the cooperation is suitable for you. Of course, we will be happy to answer any questions about the contract also.
After the last meeting during the discovery phase, we will schedule a time for a proposal review. Usually, this happens within 5-8 business days.
Proposal preparation
Internally we perform a part of the usual iteration. That includes scope planning, UX/UI design, and estimation. If you would like to learn more about iterations, you can check it in the “Iteration” section.
The final purpose of the discovery phase for us is to prepare a proposal for you.
In parallel, we are also going to share with you our contract example, so you can
verify the legal side of the cooperation is suitable for you. Of course, we will be
happy to answer any questions about the contract also.
After the last meeting during the discovery phase, we will schedule a time
for a proposal review. Usually, this happens within 5-8 business days.
The proposal
We are working with the team to process all the information from the discovery phase and create a proposal on how we can help. Even after the discovery phase, we may still ask some questions to ensure the proposal is relevant and takes into account all your needs.
Our proposal is a simple document that contains:
- Scope of work
- Definition of deliverables
- Required investment
- Suggested timeline
Proposal discussion
At this point, thanks to our cooperation, we have a draft version of the plan (which is the proposal). Together we double-check nothing has been missed and whether any new information has appeared, and we need to update the proposal.
Deliverables described in the proposal are usually split into two-week sprints. Each sprint ends with a demo for the product owner (you) and stakeholders (anyone in your organization interested in deliverables).
Things that are not going to happen during this meeting:
- Selling
it happens 1-2 business days before our proposal discussion meeting. That is to give you some time to read the proposal and prepare questions or notes (if any).
If you need some time to think about the proposal, we are always happy to meet one more time within 3-5 business days so you can discuss the proposal internally.
Contract signing
This one is very simple. If you are happy with the contract - we sign it. If there are some questions, we discuss those.
Iteration
The most exciting part of the process is where the actual solution is being built and demoed to you. As we have mentioned earlier, the delivery is an iterative process and can be split into two-week sprints. Here is what happens during the delivery:
07.1. Iteration Planning
We sit together with you and your team to identify what to include in the iteration. Scope of work is determined by your business priorities, technical aspects of tasks, and agreed-on iteration capacity. Once the planning is finished, it is considered unmodifiable. You know what will be delivered, and we know what should be done. Any new changes will go into a new iteration.
07.2. UI/UX Design
We will sit together with you and stakeholders to find out the best UI/UX approach for user-facing features. Our experienced UX and UI designers will interview you to identify the best UX and UI to ensure end-users have a smooth and fulfilling experience while interacting with the product.
07.3. Architecture Design
The development team, together with the technical project lead, design the architectural aspect of deliverables. Carefully designed architecture becomes a solid foundation for your product. Besides it, during this phase, the team identifies the implementation approach suitable for the deliverables of the iteration.
07.4. Estimation
We work on a fixed-price model. It means you always know the cost of the iteration in advance. Our team carefully analyzes all the desired deliverables of the iteration and estimates the required effort. As a result, you are getting the timeline and investment necessary for each of the iterations.
07.5. Implementation
Our team works during the iteration on actual changes/features during this step. In parallel with the developers, Quality Assurance Engineers describe test cases and implement manual and automated tests. Additionally, DevOps Engineers create the required infrastructure.
07.6. Demo
Once the iteration is complete, we schedule a demo with you. It includes a walk-through of features delivered and usually covers all major user flows or use cases of the deliverables.
07.7. Acceptance
After the demo, we invite you to perform an additional round of testing - User Acceptance Testing (or UAT). It is highly recommended to give a chance for real users to use the feature even before it is released to the production environment. This way, we can collect even more feedback and adjust the direction of the product if needed.
07.8. Deployment
At the very end of the iteration, once all changes are implemented and tested carefully, a deployment to the production happens. After this, end-users of the product can start using new features or improvements.