Responsible for the analysis, design, architecture, development, implementation and validation of the components necessary for the sale, operation and maintenance of the checks product.

The development team is in charge of providing technological solutions to the challenges and objectives posed by the product checks.

The team analyzes the problems and challenges posed by the product, they also design and implement solutions with the purpose of reaching customers who require such solutions in a timely manner.

Functions

• Analyze problems.
• Design solutions.
• Coordinate tasks.
• Communicate designs and agreements.
• Develop solutions.
• Implement solutions.
• Maintain implementations.

Workflow

The checks development area follows the following flow:

Definition of the objective

Upon receiving an objective from the coordinator, the team will be in charge of proposing the necessary solutions and fulfilling the requirement, in this way tasks are proposed with the final objective of fulfilling the objective.

Task creation

Once a clear definition and tasks are defined, the team creates different task tickets, describing what is expected to be accomplished with each ticket, using kanban, a board in which tasks are listed, visualized and assigned.

Task development

All tasks are available for development by any member of the development team.
When a team member wishes to take a task, it is assigned to him/her and the ticket is moved to “Doing” status.

Task validation

At the end of the task the member will move the task to the “Validation” grouping, for another member to validate the task, providing feedback to the development designer.

Meetings

Daily

The team performs daily dailys with the participation of the product teams and coordinators, to synchronize and align on the same objective, and notify the status of the tasks from the previous daily.

Weekly

• Weekly’s: Meeting whose objective is to discuss where and how to get to and meet a goal, looking to talk about progress, drawbacks, and extend or minimize the time (if necessary) for the next sprint.
• Sprint: The development team seeks to open a sprint for the next two weeks, seeking to meet the objective before the next sprint.

Methodology

Some practices of SCRUM, KANBAN and OKRS methodology are used as a basis to open and close objectives per sprint.

Sprints: Objectives are defined and written, focusing on strategies according to what the product seeks to pursue, to be directly related to the objectives of the organization, to finally propose how to validate the result of each sprint.

Team communication channels

• Google Chat: The official channel through which check teams communicate.
• Trello: Used for task organization, place by which the team communicates about the status of progress, and development.
• Mail: Used formally.

Documentation

The code is self-documented, the development team always tries to leave comments within the code, leaving necessary instructions to explain its installation, how to perform the tests, with a small description of the component that is stored in gitlab.

For the API’S, there is a channel offered to the clients in which a user is offered so that the client can visualize the way in which the API’S is integrated, where the input and output methods are found.

Development tools

• Python: Language used for programming.
• ReactJS: Used for all frontend.
• Docker: Used to automate software deployment inside containers.
• Kubernetes: Used to manage workloads and services.
• Airflow: Used to create Python scripts for checks.
• MongoDB: Focused on NoSQL database design, storing BSON data structures.
• Postgrest: Used for the creation and management of related databases for checks.
• Gitlab: Used to maintain version control, tracking and code review for the checks development team.
• Gocd: Used for software development helping to automate the continuous delivery of software.
• Nexus: Used as a code repository for the checks development team.
• Jamboard: Used to design solutions, agreeing on team conversations.
• Google Drive: Used to store information or files that can be used in the future.

With which teams does the checks development team interact?

• Product team.
• Coordination.
• Infrastructure.
• Development factory.