Describe the program's most important achievements and lessons learned:
INDI 2.0 is in the 2nd phase of implementation in “Production” mode. It is premature to talk about achievements. However, user feedback, in general, was very good: the application’s simple design, its usability and the practicality of being multiplatform were highlighted. INDI 2.0 maintains the achievements obtained with INDI 1, which managed to considerably reduce processes and processing times, reduced data loading errors and provided transparency to the inspection act. Clarity in the definition of the scope and user requirements: The precise definition of user requirements and scope is essential for the success of the project. It is important to collect and validate the requirements from the beginning to gain value in each process. On the other hand, establishing clear limits on what will and will not be delivered as part of the project prevents uncontrolled expansion of the project that can negatively affect deadlines and resources. Clear and regular communication is essential. It is important that stakeholders are informed about the progress, changes and problems that arise during the project. Change management: It is advisable to define a clear process for change requests and their management, to prevent the scope of the project from constantly changing. Risks must be proactively identified and managed from the beginning based on a contingency and mitigation plan. Risk management was not implemented in INDI 2.0 and this led to the application of contingency actions that had not been previously evaluated, with the impact on deadlines and resources that this entailed. Training: Ensure that users/inspectors are trained to use the new application. A meeting was held with the relevant inspectors of each TA in which they were involved in the project, participated in the test phase, offered opportunities for improvement and were also trained on the use of the new application, so that they are the vehicle for training their TA colleagues. Involving stakeholders actively and regularly is important. In INDI 2.0, this objective was achieved, which helped ensure that expectations were aligned with results.
Describe the challenges of the program:
Adequate documentation: For future projects, greater emphasis should be placed on maintaining complete and up-to-date documentation of all aspects of the project, including requirements, design, decisions made and problems resolved, as this facilitates knowledge transfer and management of future changes.
Specify if the program has any internal and external evaluations, if applicable, include key findings:
