Seeks to guarantee and satisfy the needs in terms of the functional requirements of the clients and to develop the software required.

The development team seeks to generate efficiency, added value, focused on functional requirements, seeking to generate a focused process with agile methodology and integration of functionalities.

The Movup development team performs the following functions:

Functions

• Define the design and architecture of the software, to meet the requirements in its structuring and how the product development will be approached.
• Develop the components and artifacts that make up the solution of the “requirement”.
• Document the different views that compose the “requirement” for its solution.
• Research, develop and implement the product requirements.

Responsibilities

• Ensure the correct construction of documents.
• Ensure that incoming requirements can be evolved or corrected over time.
• Provide the team with any doubt or inconvenience that may be required for the Paint land of the factory.

Process flow

• Efris requirements: Contextualized from the Jira layer and other sources.
• Design: Generate the necessary solution for the process.
• Code: Creation of the required solution.
• Codereview: Instance to cross-check the development done by another person, review to ensure proper operation.
• QA Support: Performs unit tests.
• Certify the development: The development documentation is done.

Team communication channels

• Google Chat
• Jira
• Google Meet
• Email

Types of internal communication

Meetings held by the development team, focused on providing an answer or definition for each phase of a development.

• Daily
• Estimation meeting
• Coordinate move to production
• Retrospective

Support from other areas

The development team provides and receives support from different areas of the IT team, which are the following:

• QA Team: QA provides support and validation to the development team.
• Infrastructure team: The infrastructure team seeks to build the necessary elements and tools that allow us to respond to the client as soon as possible and to monitor the platform, in order to have greater control of the developments.
• Product area: We work on proposals for methodologies, documentation processes, changes in the factory, support in the transformation of processes (to adjust to different models).

Development team documentation

The team develops different types of documents to support and explain the established development, which are the following:

• Figma: Document in which it is described how the application should be built, this document helps to have a clear reference. To govern the behavior of the interface.
• Deployment diagram: It shows the different parts of the architecture and how they are affected, it refers to the queuing system, the microservices, the availability of resources within the solution, the distribution of the system.
• Final document: At the end of the development and production, a final document is delivered, the user’s manual of the development that was carried out.
• Operation manual: Infrastructure receives an operation manual, which is a document explaining the development, attaching the development.

Development tools

• Git: Used as a version control management tool.
• Gitflow: Which facilitates the cycle.
• Phyton (Backend): Programming language.
• Angular (Frontend): Programming language.
• Visual studio cloud: Used from the cloud for the design and creation of new code.
• Kubernetes: Used to manage workloads and services.

Documentation tools

• GCP Suite: Used to work the documentation from the cloud.
• Diagrama.net: Used to create documentation diagrams.

Database development tools

• MongoDB: Focused on the design of NoSQL databases, storing BSON data structures.
• Elasticsearch: Used as a search engine.
• Rabbitmq: Used to send and receive messages from the database.