When we work with end-to-end development we use an iterative process based on a version of the OPDCA method. We focus on the core product first, we design and research (INCEPTION), we build it (CONSTRUCTION), we test it (LIVE TESTING) and based on the outcome of this we start a new iteration process if changes are needed, or we release it to the end users if all requirements are met (GO LIVE)
In order to be able to minimize the number of iterations needed to reach the go live phase we believe that the initial conditions need to be understood. We therefore observe the environment in which the end-users work, trying to gain an understanding of how to best shape the product based on their needs (the intake phase). Less iterations means a decreased cost and a faster delivery.
For us to develop the best possible product for you, we need to understand your organization, because just as they told us when we were young, we are all the same, yet we are all very different. Our experience in the field combined with your input of the day-to-day work is a crucial step to ensure that we can target and cater to your specific needs.
The intake process is something we do with each customer, once. It is not part of the iterative process but rather a starting point to ensure that we understand your business.
The intake process is always adapted to the customer but in general the intake should always include the following.
Workshops to understand the need within the organization.
Interviews with employees to understand how their day-to-day work is structured.
Current environment walkthrough (if applicable).
Expectation and scoping discussions.
This process usually takes 2-5 days depending on the size of the organization.
After all of this has been done, we will present you with our understanding of your organization, allowing you to evaluate how well we understand your current needs. This is vital to ensure that we are all moving in the same direction. This includes the following:
Detailed estimates for the project.
High level requirements.
Map of external systems.
The information gathered during the intake phase as well as any input from a previous iteration phase is used to create a proof of concept. This is used to validate that our proposed solution matches the input from you as well as the need of the end-users.
The inception step spans across approximately two weeks.
After the inception phase we will present you with:
A refined or new version of the design.
Evaluation of which technology best suits the requirements.
Architectural blueprints of the solution.
The construction process is split up into two-week cycles.
Each cycle will deliver a testable prototype, sent to you for comments and feedback. The feedback given by you is a very important part of this step as we need to make sure that we are aligned with the expectations that you have.
By working together in shorter iterations, we can ensure that the end-result is easy to visualize while still allowing for modifications to be made if necessary.
It is your product, we will build it the way you want it!
After the construction phase you will be given the following:
A working product integrated with external systems.
As the construction phase progresses, we will deliver testable products that should be evaluated by a closed group of end-users.
These users will work closely with us and will be given the mandate to influence the direction of the end-result. This helps us ensure that we deliver a product that the end-users want but also helps with the user adoption.
The system should be designed for them to do their job better not to comply with a work specification created months or years ago.
The live testing phase will give you the following: * Test reports.
- Analytics reports.
After the testing phase has completed and all feedback has been taken into consideration it is time to release the system to the masses.
During this phase we will monitor the system as well as offer support to ensure a smooth transition for the users.
After the go live phase we will provide you with the following: * Usage reports.
- The final system deployed to production accessible by the end-users.
When we talk about technical support, we talk about the support that happens after a product is released. This type of support can come in many various forms and it all depends on the requirement from you as an organization. We will suggest one of the following solutions based on the information gathered during the intake phase.
Handover to local resources
We train your staff to be able to handle any support questions from the end-users related to the product.
On request support
We do not provide any support unless specific issues arise, this means no upfront cost, but each request will be estimated and charged based on the resolution time.
Keep one fulltime developer This is what we have experienced works best in most cases. One of the developers remains in the team for a time period. This ensures that the technical expertise is still available, and it allows for minor changes to be made if necessary.