Before hiring a service delocalized development and having chosen the company where they will deposit the confidence to develop our project, we have to get down to work.
Below is a list of best practices when you begin:
USE CONTINUOUS INTEGRATION TO BE CONTINUALLY UPDATED
Not worth reviewing each week. The review should be constant through mechanisms of CI. This results in:
- Do frequently commits
- Jenkins or other continuous integration servers running the build every few minutes (1 hour minimum)
- Software quality tools like Sonarqube
- Automatic Deploys
- Automated Functional Test
Motivation: if something breaks I want to know when to react quickly
USE A CORPORATE WIKI TO SHARE BOTH TECHNICAL AND BUSINESS INFORMATION
When teams are further separated by slots communication is a handicap. Generates orderly project documentation and technological base that teams have to learn. Not only the code convention but also the architectural patterns used, what is expected of them as developers … Some troubleshooting is not bad.
Motivation: Let’s clear things, minimizing the error.
INCENTIVE TRAVEL BETWEEN COMPUTERS
Knowing well and start building a relationship of trust is fundamental. Also, put a face and eyes the name you see in the commits is also very important. We have found that relationships are greatly improved when the teams meets, creating a situation of “camaraderie”. We propose constantly travel from Barcelona to Vietnam and vice versa, at least once every three months. Never cut corners to have a motivated team is the most powerful force.
Motivation: When teams are known and understood, the project flows.
PROMOTE MEETINGS BY VIDEOCONFERENCE
In Apiumtech, we are continually making calls via Skype. To resolve customer questions, to clear doubts technical teams to have functional feedback … On many occasions is much better than emails.
Motivation: Make the most of the benefits of connectivity to connect people.
MAKE ITERATIONS OF SOFTWARE DELIVERY IN TWO WEEKS SPRINTS
It sounds so exhaustive that will be companies who prefer more or less time. However, based on our experience number two is perfect. A week falls short because the stabilization and estimation of the new sprint make the time to develop very small. Three weeks is too much to make a demo customer.
WITH A TWO-WEEK SPRINT AGENDA IS AS FOLLOWS:
- We begin the sprint planning meeting II in Tuesday. About noon we filled two weeks of development. We started to itch immediately.
- The sprint is going to not have controlling deviations from the following Monday we usually have user stories to go finished teaching the client. We have one week ahead.
- Between Thursday and Friday we know we have to go running, you can consider two situations: either everything is perfect and we have come a long way (then we put another user story in the sprint) or go just for some impediment, here we tend to re-estimate and solve locking points. QA has been giving us feedback as we were finishing each story.
- Monday is the last day. It’s all over but QA test intensively so that everything is perfect. Monday stabilize.
- On Tuesday, while the client makes the demo in Barcelona, we are estimating the new sprint and back again.
Motivation: The agile method is the best way to produce software.
THE BEST ORGANIZATIONAL STRUCTURE FOR AGILE OUTSOURCING IS CUSTOMER-PROXY
On the way to organize client computers with traditional offshore, it is the client who hires outsourcing in another country and it manages these resources. To ensure that the offshore works, we simply put a layer between the client and offshore. People Apiumtech in Barcelona is the intermediary between the client and the offshore, adding value throughout this layer. Nowadays, what assemble all (continuous integration, repositories, automated QA, code quality, sprint user stories in Jira …) so that the client only worry about your product.
Motivation: Apiumtech Barcelona takes care of everything to make the project a success. In Vietnam we code like animals. Coding is what make us happy.
This is roughly the methodology we have adapted from the existing ones (We have not invented the wheel) to provide the best quality. The code matters to us!
If you are interested in receiving information or can help to clarify some doubts drop us an email and within hours we will contact you.
