> For the complete documentation index, see [llms.txt](https://docs.leapwise.co/backend-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leapwise.co/backend-handbook/project-management/our-ways-of-working.md).

# Our ways of working

Our meticulousness and adherence to quality are embedded into everything we do, starting from the way we build code. 

### **#1 Standard architecture** <a href="#ourwaysofworking-1standardarchitecture" id="ourwaysofworking-1standardarchitecture"></a>

Internally, we created several concepts like standard architecture, which defines an application structure on a very detailed level. It serves both as a guideline but also drastically increases development velocity.

It also enables any developer to jump into an application they have never seen before to instantly be able to navigate through the code which increases scalability within or even outside of the team.

### **#2 Technology guidelines** <a href="#ourwaysofworking-2technologyguidelines" id="ourwaysofworking-2technologyguidelines"></a>

Establishing internal technology guidelines at the company level is essential to sharing handbooks like these as part of community building.

Our **internal backend and frontend guidelines** outline the correct usage of technology, frameworks, and terminology. We think that ensuring language uniformity is critical for effective communication among team members.

### **#3 Open and regular communication** <a href="#ourwaysofworking-3openandregularcommunication" id="ourwaysofworking-3openandregularcommunication"></a>

Additionally, at Leapwise, we adhere to predefined communication protocols. For instance, our daily **scrum meetings** are limited to a maximum of 15 minutes, with each team member required to address five standard questions. This approach allows regular and continuous questioning of any approach or technology being used.

### **#4 Strategic guidance & architectural direction** <a href="#ourwaysofworking-4strategicguidance-and-architecturaldirection" id="ourwaysofworking-4strategicguidance-and-architecturaldirection"></a>

We created a **cross-department team** that provides strategic guidance and oversight for the architectural direction of an organization. This team is typically composed of experienced architects, technical leads, and key stakeholders who collaborate to ensure that the architectural decisions align with the overall business goals, technical standards, and best practices.

Such an approach ensures continuous evaluation of what we learned so far, open discussions, and knowledge sharing.

### **#5 Educational curriculum** <a href="#ourwaysofworking-4educationalcurriculum" id="ourwaysofworking-4educationalcurriculum"></a>

Creating a yearly educational curriculum executed by industry-leading names and providing hands-on workshops drastically speeds up progress not just for individuals but for the entire team, and has multidimensional cohesive effects in creating a more homogenous team.

Everything we do internally is purely intrinsically motivated and it leads to one and only one goal — to create a critical mass of professionals who are the best at what they do.&#x20;

There is a saying we live by: *If you think hiring a professional is expensive, hire an amateur.*&#x20;