Capgemini - Prosegur
#The Challenge: Keeping an app in many countries
DISCLAIMER: To comply with my non-disclosure agreement. I have obfuscated confidential information in this case study. All information in this case study is my own and does not necessarily reflect the views of Capgemini.
The company
Capgemini is a global consulting and technology company, and I worked with the customer Prosegur, a leading global security company.
My position
During this period, I worked with the customer Prosegur in an Outsourcing model and my position there was maintain a global app already in production. This app is available in several countries, including countries in Europe, Argentina, Brazil, USA, and India. Some of my daily tasks included:
Developing new features using internationalization. The app was available in English, Spanish, and Portuguese.
Developing critical features such as a "panic button" and GPS tracker for armored truck drivers transporting high-value money.
Scaling monitoring using Crashlytics and Google Play Console to get data insights, solve bugs, and avoid possible crashes.
Releasing versions and keeping an organized version control changelog for several coutries around the world.
The team
The project had a squad focused only in mobile and was composed by a product manager, a requirement analyst, four android developers and two Q&A's. Other professionals like backenders, designer, product owners were separated in another team. In the total we were a team of eight people and they were distributed in mid and seniors professionals.
The methodolody
The methodoly used considering the software engineering was Kanbam model and the purpose of all the team was to maintain the app working in production for a lot of countries solving bugs, giving support with parametrizations, and creating new features. We used kanbam in this project because some features were so big and used for several countries around the world without the possibility to delivery partial parts of a feature. So, because this motive we didn't used scrum that says we need to have a delivery every sprint end.
Requirements & Analyse
As I mentioned in the team composition, we have had a requirement analyst which talks with several managers and PO's/PM's around the world. This professional was responsible to bring the critical request for our product manager (PM) who decides what was more important and plan the backlog for the next sprint based in datas and duedates collected around the world.
Design
This project in special had a special pecualirity that the focus was in perfomance and funtionality. On the other hands, it doesn't need to be beautiful, but needs to have precision in GPS, be fast, have good translations for natives from others coutries, cover internationalization around the world, print relevant reports in mobile printers and process the things fast. So, because this motive the design was simple but intuitive and with a good user experience.
Development
The development start with a developer updating the status of a task or bug in JIRA. Changing the status to 'active', means that the developer is working in that functionality and the first thing to do is read the description wrote in jira with evidences and files for parametrizations and armored truck routes simulations. With all the files configured and sincronized the developer codes what is necessary, test it with stressfull tests (e.g: monkey test, overflow test) and by the end fixes the internationalization document and parametrization to work for several countries. With this done, the developer move the task or bug to 'ready' in JIRA and the Q&A assumes from here.
Tests
The Q&A's create fake data, fake routes, fake parametrizations to test the app in the environment of development and homologation. The objective here is test with the homologated and tested devices for prosegur that are used around the world. In these devices are included some smartphones, tablets and portatil printers. The Q&A's:
Set the routes in the app.
Define a country and the devices.
Simulate a fake armored truck doing delivering and collecting money in banks or big companies.
Print the documents and status from the deliver or collect.
After that, change the parametrization, change the language and test all again to verify if it continue working for all the countries.
Deploy
The proccess of deploy consists in the generation of a .apk in jenkins platform and after that the product manager (PM) get the artifactory and upload the current version for the countries that required the changes.
