Starting a new enterprise Java project

When a project is started, the project team is assembled and/or prepared for working on that project. Some of the needed activities are (usually) technical training and workshops sessions. Besides the training and workshops sessions, we can provide the following additional services:

• Initial project setup, from the technical and non-technical perspectives (Agile process setup, architecture and business domain documentation)
• Periodical mentoring and coaching discussions and technical workshops, whenever they are appropriate.
• Devops, CI (Continuous Integration) & CD (Continuous Delivery) setups, as well as containerization setups (such as Docker and Kubernetes).

Improving the team's technical knowledge

When a company intends to change, improve, or start an existing project, those changes and improvements may imply some technical and organizing challenges. Besides the training and workshops sessions, we can provide the following additional services:

• Project assessment and upgrade(s), from the technical and non-technical perspectives (Agile process setup, business domain and architecture documentation)
• Periodical mentoring / coaching discussions and technical workshops, whenever they are appropriate
• Devops, CI (Continuous Integration) & CD (Continuous Delivery) setups, as well as containerization setups (such as Docker and Kubernetes)

Migrating, refactoring or re-architecting a project

For projects that are migrating towards containers, cloud architectures and/or microservices, we can provide the following services:

• Coaching and mentoring on the initial containerisation and/or infrastructure setup
• Improving/updating the project setup, from the technical and non-technical perspectives (Agile process setup, architecture and business domain documentation)
• Periodical mentoring / coaching discussions and technical workshops, whenever they are appropriate for the project context and timeline

Duration and procedure

As the improvements path and the available time varies for each team and project, we use the following approach to tailor them properly:

• We establish the improvements path together with each team or project manager, based on an initial assessment and a series of milestones
• We agree on a number of sessions per week, usually between 2 and 3; and
• We perform periodical assessments of the achieved improvements, in order to make sure we're on the right path

Online or offline

As each team and person has a different schedule, availability and working mode, we agree on online and/or offline communication and working details for each improvement topic. We strive to provide the best time efficiency for each party; therefore we intend to use each other's time in an optimal way.