Services #

Every service will provide at least one solution. Every action will produce reports, documents, “things” that will present the status and suggested solutions with their expected outcome.

Pricing is set to 100 - 175 euro per 1 hour, HTVA - depending on the service and the duration of the commitment.

Get in touch via LinkedIn

  • French, English, Romanian, Russian.
  1. Create together with the CEO, Tech Leads and other high ranked IT staff the technical strategy for the company for short and long terms.
  2. Select the technical stacks to use, in what contexts.
  3. Choose service providers.
  4. Define the software development and product delivery will be organised (CICD, Release Management, Testing, etc.)
  5. Define the career management and liberties that the company will provide.
  6. Help to put, all the defined things, in place.

Improvement of the recruiting and exit processes

  1. Define the way an interview is conducted.
  2. Define the format of the job descriptions sent to new candidates.
  3. Put in place a process to validate that job descriptions are checked beforehand by the right people. (e.g. A team member will check the description and the technological stack)
  4. Define the complete organisation of a hiring interview.
  5. Define the way people need to talk, what phrases to use, what vocabulary.
  6. What actions are expected from the CEO or business in general within the recruiting process.
  7. Define the complete organisation of an exit interview.

Evaluation and Upskilling

  1. Analysis of the existing technologies already in place.
  2. Gathering the information from the staff about missing knowledge.
  3. Creation of individual or group programs for upskilling or converting, with the possibility to have a mentor and a follow-up.
  4. Finding the most efficient way to do Continuous Improvement and Learning without impacting deliveries.
  1. One shot technical code or architecture reviews of specific projects, like a simple audit.

    • A list of findings and possible solutions will be provided at the end.
  2. Per project.

  3. Globally, per company.

  4. What patterns can be used.

  5. What patterns need to be avoided.

  6. Define if a dedicated code review is needed.

    1. Format: git-flow, ad-hoc, on-demand.
    2. What format offers the most efficient results.
    3. Calculate the costs of this activity and compare to others like Pair Programming and Continuous Training or Internal/External Audit.
  7. Define the practices for Code Reviews.

  8. Help to put all the defined practices in place.

  9. How the architecture needs to be documented.

Development process review Analyze the tools and practices used by developers for:

  1. Coding.
  2. Building
  3. Documenting.
  4. Releasing.
  5. Deploying.
  6. Debugging.

Going further 8. Propose practices where applicable. 9. Pair programming. 10. Code Review. 11. Clean Code workshops. 12. Hackathons. 13. Offer improvements, fixes or tips for the current processes. 14. Validate current processes to assure that everything is fine.


  1. Coaching the CEO and other business people about technical things by using business jargon.
  2. Coaching sessions for developers as follow up for courses.
  3. Teaching specific subjects, like Spring Boot and it’s best Practices.
  4. Creation of documentation inside the company to keep the knowledge inside.
  5. Coaching on how a presentation needs to be delivered to various groups of people.

Implement or enhance documentation best practices

  1. Putting in place of a documentation platform.
  2. Defining rules of creating the content.
  3. Add documentation to the DoD Definition of Done and DoR Definition of Ready.
Value for the client
  1. The clients will benefit from the following improvements:
  2. Improved communication between business and technical departments.
  3. Improved quality and stability of the product (less bugs or regressions in production).
  4. Improved handling of incidents in all environments: dev, test, prod, etc.
  5. Improved observability and monitoring practices.
  6. Service reliability best practices (SLA, SLO, performance).
  7. Clear statistical view of the quality of the software.
  8. Lower employee turnover.
  9. Improved ROI of cutting edge vs legacy.

The aforementioned benefits will bring the following values:

  1. Optimized budget for time to market life-cycle.
  2. Less money spent on fixing what has been delivered.
  3. Less money spent on “un-doing” or “re-doing” of what was not needed/asked but delivered.
  4. Cost effective maintenance.
  5. Improved ROI in R&D projects.
  6. More motivated staff.

All the measurements will be done on the client side and presented in person. The client must provide all the required information for a proper analysis of the improvements that are to be presented as solutions

Customers who apply the recommendations will receive “badges of honor” to certify that they are doing a good job in their IT departments. The exact mechanism on how this will function will be described in the summer of 2022.