Discover Your DevOps Maturity 1. CODE QUALITY 25% of survey complete. Question Title * 1. Do you use sonar? If so, are you strict about : - The minimum coverage required. - Fixing bugs and code smells'. We don't use Sonar for our development. We use Sonar, but only for certain parts of our development of our development (less than 80% coverage, few bug fixes, code smells, etc.)'. We are strict about using Sonar, fixing reported bugs and have a minimum code coverage rule of 80%. Question Title * 2. Do you write unit tests on a regular and systematic basis? Unit testing is not a priority in our development work. We write unit tests when we can, but only for certain parts of our development. We are rigorous, all the code we produce is covered by unit tests. Question Title * 3. Do you use TDD in your development work? TDD is not common practice in the team We use TDD for some of our developments TDD is a practice mastered by the whole team and used for all our development. Question Title * 4. Do you regularly refactor code? It is not a priority and we have little time to refactor code. We do occasional refactoring of certain developments Refactoring is done very regularly in our company, it's a practice we're familiar with. Question Title * 5. Do you regularly engage in peer programming? Peer coding is not a common practice in the team. We do peer programming occasionally. Yes, we do peer programming on a regular basis, it's a very common practice. Question Title * 6. Is code review a natural and systematic part of your team's work? Code review is not a common practice in the team. We do it when we have the time, only for certain parts of our development. Yes, we do regular code reviews, it's common practice in the team. Question Title * 7. Do you have team code standards? If so, do you use them in your development? No We have some code/development rules and standards within our team We have a standard code base that is regularly updated and frequently used in our development and code reviews. Question Title * 8. Is technical debt managed by the team? Technical debt is not a priority for the team We do very little work on our technical debt We have a technical debt management strategy that is understood and accepted by everyone. Question Title * 9. Are the SOLID principles understood and used by the team where appropriate?Single ResponsibilityOpen/ClosedLiskov SubstitutionInterface SegregationDependency Inversion No We have a few SOLID principles that we use from time to time. Our thinking about our developments is systematically 'driven' by principles such as SOLID. Question Title * 10. Are you comfortable using GIT in your development? We still have a fair amount of complexity and misunderstanding in our use of GIT. We have mastered the use of GIT, but still have some areas for improvement The whole team understands and masters our strategy for using GIT. Question Title * 11. Are you able to develop, maintain and deploy loosely coupled modules without affecting the whole system? We know the principles of weak coupling, but we don't have the time to rethink the architecture. We're trying to break things down into smaller modules, but we're constrained by deadlines and complexity. We have mastered weak coupling and are able to ensure the autonomy of our components. Question Title * 12. Do you value writing reusable code/components? We don't have time to rethink the design and write reusable code. We are trying to write reusable code, but we are constrained by time and complexity. Yes, we optimise lead times and costs by developing reusable components. Next