Best practices Through our experience in developing computer systems, we came across several problems that affect many businesses. This is why we are emphasising on the implementation of a new methodology for software development that would provide an effective solution to these problems. Below is a list of the most common problems we encountered in the industry and some best practices to solve them: Could you follow your system provider through the whole process? Give constant visibility We constantly communicate with the client so that he is involved in the product development process. Each week we review each stage and show the customer the product evolution in order to validate its functionality. In addition, the customer has access to an updated list of tasks that the team performs each week ("Iteration Backlog"). It can be accessed at any time during the development process. Did you have the opportunity to verify that the specified tasks were carried out effectively? Ready to deliver The customer is able to see a portion of the product (weekly delivered) in order to verify that the product is being developed as agreed. In addition, the customer has access to an updated list of tasks that the team performs each week. It can be accessed at any time during the development process. This allows the customer to corroborate that the team is performing the tasks that were agreed in the project planning. Were deviations informed at the precise moment that occurred? Iteration planning At the beginning of each week, the client and the development team meet to define what steps are to be followed in the current week. This means that the customer is always aware of the tasks the team performs during the product development. In this way, customers can find out of any detours from the original plan at an early stage of the production process. What ensures that the bugs detected by you are repaired and prioritized according to your specifications? Give constant visibility Thanks to the constant communication we have with the customer, he can be noticed of all the changes made in the project and verify that the project is executed accordingly to the specifications given. In addition each of the bugs detected are added to the list of tasks ("Backlog") to be prioritized and corrected. In this way the customer can check the status of each bug that were found during the development process and be certain that they are properly fixed. Did you need to implement a functionality before the project was completed? Ready to deliver A partial product is delivered weekly (product increment) to the customer with the functionality developed during each week. In this way, the customer has a part of product to use without having the complete version of the final product, achieving maximum return on their investment (because he can start using the product before its finalized).