Good practices guarantee a high level of code quality, and will allow a better readability and understanding of the code for future developers.
Teams can select practices proposed by Promyze, or define their own practices from their own context.
Each team is free to create its own practice profile, which can then be reused by other teams. Each team becomes the main actor of your quality strategy.
The team is responsible for the quality of the code it produces. To align its practices, regular exchanges are necessary to adapt the most relevant methods.
The Promyze Craft Workshops structure these exchanges. Based on recent source code selected by the team, each developer can suggest good practices to follow, and highlight examples and counter-examples.
These concrete examples from the project then document the practices to facilitate their understanding.
A retrospective at the end of the Workshop is the scene of discussions with the aim of enriching the existing good practice guide and sharing the knowledge of each developer.
By collectively taking a step back on the code it produces, the team values the work it has done by highlighting code that respects good practices.
If a consensus is not reached on the practices, a "Battle" mode allows everyone to argue for or against the adoption of a practice. The team will decide the outcome together!
Customised feedback tells each developer the impact of their changes on code quality and code coverage. Promyze values code modifications when they improve or do not degrade the quality of the code. If code defects are added, the developer is guided in the understanding of the non-complied practice. Promyze's diagnostics enable a better understanding of the team's areas for improvement and highlight the quality of the work carried out by the team.
Regularly setting new objectives to be achieved is part of the team's ongoing process of continuous improvement. Automatic action plans are periodically generated by Promyze, with objectives drawn from analyses of project activity. Emphasis is placed on recently modified files, which are often more relevant. With these action plans, the team knows what to do and how, which also leads to a better management of the technical debt.
Developers are more comfortable improving code with which they are familiar, to avoid the risk of introducing regressions. From the action plans, custom suggestions are notified for each developer, based on the files that are most often modified. This approach gives everyone confidence in their ability to carry out these actions, and optimises the time spent by the teams on improving the code.
Connecting to your source code managers (Git / SVN / Mercurial / TFS) allows you to follow the development activity carried out by your teams as closely as possible. Automatic synchronizations are made by Promyze on repositories (and zero writing!)
The interface with your static code analysis tools (SonarQube, Checkstyle, EsLint, Rubocop, ...) allows you to understand the impact of modifications on the source code. Promyze is agnostic of the languages and technologies used, and accesses data from the tools present in your ecosystem..
No external access, you remain the sole masters of your data and the deployment of Promyze in your application ecosystem. The interface with your company directories (Azure Active Directory / Active Directory / SSO) allows you to control access to Promyze.
The attention paid by your teams to the quality of the code and the efforts made to achieve the action plans have a positive impact on the project’s quality indicators. Synthetic dashboards provide information on the evolution of these indicators.
You can generate a summary in PDF format at any time on the quality of the developments recently carried out in a team.
The content is customisable and transparently reflects the efforts invested by the development team.
Additional emulation is available on request. Based on playful principles (badges, level bars), the gaming rooms bring users together in a positive spirit (everyone wins, no penalties).