How We Work - Delivery Model for Agile IT Development
At Magenta, we have developed a delivery model that ensures that your project goes through the necessary steps to achieve the best possible result. The model is based on the best practices, 20 years of experience with agile IT development, and focuses on quality.
Pre-analysis
The first thing that happens when you want us to look at your IT project is that we examine your business case. You have certainly put a lot of good thought into why the system should be built! Preliminary analysis will often alert you to even more benefits that can be achieved. Have you considered what the actual time savings will be? Will an employee’s workflow become more intuitive or precise? Is there a focus on the core message? What are the specific success metrics? Are there specific KPIs that need to be improved?
The outcome of the pre-analysis is a basic understanding of your needs, a strengthened business case and an understanding of the scope of the project.
Business case-analysis
One of the first things we look at is where your new solution creates value: is it for a specific user group? Is it making a work process more efficient?
User Surveys
We are conducting initial surveys of users. How high is the demand? Is there already a solution? If so, how does it work and how can it be improved?
Scope Analysis
The understanding of the scope of the solution is nuanced as the pre-analysis progresses, and at the end of the phase we qualify the estimate for the development of your solution.
Analysis
You rarely start building a house without talking through your plans with an architect, builders etc. The same concept applies when developing an IT-project. One of the most important aspects of IT-development is planning out the process. This is one of the safest ways to ensure budget and quality. To work in an agile environment with incremental processes is one of the ways to ensure a successful analysis. This creates a solid foundation for your further development – from backend architecture to specific userflows and visual expression.
When the analysis is complete you will have specific documentation that resonates our common understanding of the project and how we move further. It is a must to reconsolidate our expectations, to reach the goal of a succesful project.
IT-architecture
As part of this phase, we will develop documentation for architecture, API, which technologies that needs to be applied, and everything else relevant to the technical aspect of this project.
User-friendly design
Through user-surveys the userflow and design are decided. From the analysis you will have specific userdesign and examples of pages.
Projectplan
As a part of the analysis, we will plan out milestones so that everything from work to calendar is crystal clear.
Agile development
At Magenta we prefer to work agile with focus on incremental distribution. We will work intensely on getting core functions out within 2-4 weeks, meanwhile you, as a customer, can follow our work as well as test the functions we implement. This creates transparency as well as it leaves you with the opportunity to change and precise anything you may want during the development. Because even if we make a thorough pre-analysis you might have something you want to change later in the process. The ability to change is a core aspect of our distribution. If the customer wants you can even be a part of our SCRUM-meetings as a “product owner” and test it from the get go(MVP).
Development prints
We typically plan 2-4 weeks ahead and then intensely work on getting the functional aspects, so you will be able to test it right away.
User-tests
To ensure all functionality is follow the quality demands, we will test it internally (QA) and you will test the functions as part of the actual user-test.
Ongoing prioritisation
To work with incremental development means that you can prioritise our milestones. This ensures that the thing that adds the most value is prioritised firstly.
Delivery
After the development is completed, next step is to the deliver the project to you. We review the planneded delivery and shake hands on a succesful project. The delivery process may vary but the key focus is that both of us walk away happy!
As the last step of the process we will sit down together and evaluate the project: what went well, and what could have been done better? That way, the experience we gain throughout that process can be used to grow for both of us forward.
Delivery test
Here we formally approve of the product. How this is done vary on the projects size. This is also the part where we shake hands and agree wether the project is done.
The implementation
The finished product will be implemented and the ownership will go to your organisation. If you want to run the solution, we will ensure that you have the nessasery knowledge.
Operation maturation
When the product is implemented and running, we will make a test to ensure that everything is running as wanted and that there are no inconveniences. After this the operation is over.
