Developers are divided on technology stacks for an app. How do you unite them towards a common goal?

To unite developers on technology stacks, start by facilitating open discussions where everyone can share their preferences and concerns. Focus on the app’s goals and requirements, and align technology choices with these objectives. Consider running a proof of concept or pilot project to evaluate the strengths of different stacks in real-world scenarios. Emphasize collaboration by involving all team members in the decision-making process and making the final choice based on data, feasibility, and team expertise. Encourage a unified approach by setting clear goals, fostering open communication, and supporting the chosen stack with necessary resources and training.

I've always followed the same methodology whenever a technical issue arise in a project like choosing the best tech stack: - Spike the different options, to be able to filter the ones that fulfill the project constrains and requirements. - Create Proof of Concepts so performance and effort can be evaluated and a winner can be choose. - If its not enough with features and performance, other filter criteria can be: a. amount of expertise within the team for each tech stack b. community support c. available documentation Together all these points will be enough to make an informed decision about the best technology for the project

To unite developers with differing tech stack views: Document each developer’s opinion. List pros and cons of each stack. Estimate the project budget. Assess the durability, support, and community of each stack. Analyze the data, narrow to two stacks, and finalize after team discussion.

To start, make sure the developers understand the core goals of the app and any existing business, technology, or architecture constraints. I would then recommend spiking on the different options using small to medium complexity use cases, as project time allows. Keep in mind if the use cases are too simple the proof of concepts may not give a realistic example of their capabilities. With the proof of concepts completed the developers can have an informed discussion on which solution would best match up against the apps goals and constraints. Discussing concrete examples and their results should also help limit the impact of developer biases.

Establishing clear objectives for the app can unite developers with diverse technology preferences. By focusing on shared goals and outcomes, developers can evaluate how their preferred technologies contribute to the overall success of the project.

A collaborative evaluation of technology stacks against project objectives can help developers make informed decisions. By considering factors like practicality, maintainability, and scalability, the team can choose the best option for the project.

Encouraging collaboration and knowledge sharing among developers with diverse expertise can foster a sense of unity and promote innovation. By working together and learning from each other, developers can appreciate the benefits of different technology stacks and find common ground.

Moreover, cooperation is not just about mentoring, but to see the problem from a different perspective, like: As a backend dev it is easy to forget how the frontend will use the api we are building, but by working together is a natural way of understanding each other's difficulties, resulting a better (more performant, easier to use) api.

Recognizing and utilizing each developer's unique skills can create a balanced team dynamic and foster a sense of value. By assigning tasks that align with individual strengths while encouraging learning and growth, you can optimize team performance and ensure that all members feel appreciated.

Planning together as the whole scrum team is crucial in terms of product quality. Even a junior dev could have great, thought-provoking suggestions!

The decision regarding the technology stack should be made collaboratively, taking into account the team's discussions, evaluations, and shared objectives. Fostering a sense of consensus and ensuring that every voice is heard is crucial for building ownership and commitment among team members.

I must add, that the decision must (should) be made on the level where the problem arises. In case of a technical decision it should be made mainly by the dev team, like financial decisions should be made by the finance guys. Product-related decisions should be made by the product owner (the customer's representative) AND the dev team due to its high technical exposure. And so on. I have been on many projects where even the technical decisions were made without the devs, above them, and yes, I can confirm that this kind of behavior degrades the commitment and indirectly the product quality as well.