Prior to implementing this solution, we had a lot of fear of losing our code due to some kind of situation that was outside of our control. At the same time, our team was distributed between different regional locations both inside and outside of Lebanon. When we started using this tool, it was a great way to have full access to all that was being developed between different areas.

Here in the organization, we use Chrome, with development. Also, when we are planning on sprint, for example, it's too easy to put the requirement needs above the product, and a product on that feels very good to write features too easily, and to share with the development team. Pretty quick and fast, by only writing the duration and assessment criteria and also uploading the make-ups related with the deliverables, the thing we have work with, and it also improves the communication because everybody sees the requirements. It is posted in the inbox and shares brainstorming ideas to 35 people, and how the requirement would be implemented. It's very easy to know the status of the funds of the project because the protocol will be accessible to the tools remotely and easily. He/she will review the bar down chart and know how much work is being done by the team and when the work will be approximately finished.

In the engineering area, we use an engineering process because they realize the campaign board will be very useful for consulting the deliverables of the engineering process because we develop elevators, cabinets, and also casétas used in electrical plants here in Mexico. Comisión Federal de Electricidad is our electricity plant. Our customers customize the products for us and we are introducing new product families. It's important to follow and manage the deliverables in time.