Contents:
- How the team is structured
- How the hierarchy is built in the team
- How to form team values and communicate them to everyone
- Planning and management in the team
- How to translate a business task into the language of developers
- How sprints are conducted
- How to evaluate whether the team has coped with the task

Free Python Course ➞ Mini-course for beginners and experienced coders. 4 cool projects in the portfolio, live communication with the speaker. Click here to learn what you can learn in this course.
Learn MoreIn this episode, we discussed development team structure, as well as methods for planning and evaluating its work. Audio versions and new episodes of the "People and Code" podcast are available on popular platforms. We share useful tips for optimizing team processes, which can improve productivity and work quality.

A physicist, analyst, and businessman who holds the position of Product Owner of the Unified Client MDM system at HFLabs. In his role, he is responsible for the strategic development and management of a product aimed at optimizing customer data management.
- How the team is structured
- How the hierarchy is built in the team
- How to cope with conflicts in the team and prevent employee burnout
- How to form team values and communicate them to everyone
- Planning and management in the team
- How to translate a business task into the language of developers
- How sprints are conducted
- How to evaluate whether the team has coped with the task
- How to join the team: advice for newcomers
How the team is structured
Mikhail, your company is well-known in specialized circles, but the general consumer is not sufficiently aware of it. What areas are you focused on?
For 17 years, HFLabs has been improving the quality of client data. We collect and process all information that characterizes both individuals and legal entities. We have data such as last name, first name, middle name, company names, documents, addresses, and other important information. Our goal is to ensure high quality and accuracy of data, which allows our clients to make informed decisions and effectively manage their resources.
Our software is installed on the servers of banks and insurance companies, effectively processing the information they receive daily. This business model is known as on-premise software, which means local installation and management of the system. With our solution, clients can reliably store data and ensure a high level of security that meets the requirements of the financial sector.
Currently, we offer five key product lines, and I am responsible for one of them. I am also involved in the development of new products and the formation of product teams for their successful launch on the market.
Our team is organized to effectively complete tasks and achieve project goals. It has several key roles, each with its own unique function.
First and foremost, there's the project manager, who coordinates the team's work and ensures deadlines are met and tasks are completed to the highest quality. Next come the content specialists, who create and edit texts, ensuring they meet SEO requirements and appeal to the target audience.
The team also includes designers, who are responsible for the visual design of materials and the creation of an attractive interface. Developers handle the technical side of the project, ensuring the website's functionality and optimization.
Each team member plays a vital role in achieving shared goals, which contributes to the successful implementation of projects and the high quality of the final product.
When I first started working at the company, there were about ten of us on the product team. Now, this team comprises over fifty specialists. Since then, my understanding of how a team should be organized has constantly evolved. I've realized the importance of flexibility in structure and interaction, which allows us to effectively adapt to changes in the business environment and market demands.
Team structure directly depends on its size. In small teams, members perform a variety of functions, from development to client negotiations. Each team member serves as a coder, tester, business analyst, and service engineer. In addition, there are "implementers" who also serve as project managers. This is typical for startups, where conditions change rapidly and employees work closely together. This approach allows teams to be flexible and adapt to market demands, which is an important aspect of successful business development.
As the company grows, distinct roles begin to emerge, and one of the first to emerge is the technical support team. This function is the most difficult to plan, as it is impossible to predict in advance when and what problems the client will encounter. Following this, teams responsible for customer interaction and the implementation process were formed.
The modern product team structure includes developers, testers, a product manager, and analysts. Analysts on the team are divided into two categories: external, who primarily interact with customers, and internal, who focus on the product itself. Internal analysts formulate functional requirements based on the roadmap and handle other aspects of development. This structure facilitates efficient product development, balancing technical and business needs.
Team size can vary depending on the project and its scale. Typically, a team consists of several people to dozens of specialists. It is important to consider that the number of participants affects the efficiency of work and communication within the team. A team can consist of various roles, such as a project manager, developers, designers, and testers, which allows for the best results in implementing the assigned tasks.
Each product is developed by a separate team, and the size of these teams can vary significantly. In some cases, teams consist of as few as three people, while in others, they can reach twenty. For example, our flagship product development team consists of 27 specialists. This team is divided into subgroups, each responsible for specific product features and capabilities.
How is the team hierarchy structured?
The question of building horizontal and vertical connections within a development team is an important aspect of workflow organization. Most companies have a specific hierarchy that helps structure the interactions between different roles. Typically, it looks like this: at the bottom level are simple developers who are directly involved in writing code and solving technical problems. As they gain more qualifications and experience, they can become lead developers or senior developers, who take on more complex projects and can act as mentors for less experienced colleagues.
The next level are team leads and tech leads. Team leads are responsible for leading the team, coordinating tasks, and maintaining effective communication between project participants. Tech leads, in turn, focus on the technical aspect of development, ensuring adherence to quality standards and architectural decisions.
At a higher level are product managers and project managers (PMs), who are involved in strategic planning, defining product requirements, and project management. They connect the development team with business goals and customers, ensuring the successful completion of tasks.
At the very top of the hierarchy are the VP of Engineering and other managers who make company-wide decisions, determine development directions, and are responsible for the overall management of the development teams. It is important to note that each of these roles plays a unique role in the development process, and effective communication between them is critical to the successful implementation of projects.
The project does not have clear grades for developers. Given its long history and complex business logic, it takes time to fully understand all aspects. Developers can be roughly divided into experienced and novice. However, key issues, such as architectural decisions or major changes, are discussed by the entire development team. This approach promotes a better understanding of the project and ensures high-quality execution of tasks.
We recently faced the need to create a unified monitoring system for all our products. It was crucial to coordinate actions across teams: determining which tools to use, where to move shared code, and other aspects. We don't have a centralized leadership that could set uniform rules, so teams can reach agreements on their own, and that's enough for now.

Product managers play a key role in this story, as they are responsible for strategic planning and product development. Their job is to understand user and market needs and coordinate the work of various teams to achieve common goals. Product managers analyze data, collect user feedback, and make decisions about product functionality and design. They act as the link between developers, marketers, and customers, ensuring the consistency of all processes. Importantly, their involvement at all stages of the product lifecycle contributes to the creation of a successful and in-demand solution.
Product managers at our company perform not only product management functions but are also actively involved in people management. This means they manage teams and ensure effective interaction between project participants. This approach not only allows us to create a high-quality product but also develop the team, increasing its productivity and collaboration.
As a result, a three-tier project management structure is formed. The product manager is responsible for product development, backlog management, task assignment, and interaction with account managers and customer-facing analysts. The production department handles planning, releases, regression testing, and project handover to the customer. Additionally, each team—testing, support, and development—has a designated team lead who coordinates internal communication and monitors task completion. This structure ensures effective collaboration between the various roles and contributes to the successful achievement of project goals.
Developers interact with various departments related to the development process. They most often work closely with testing, design, and product management. The testing department ensures software quality by providing feedback on functionality and identifying bugs. Designers help create a user-friendly and attractive interface, and product managers define requirements and priorities.
Relationships between developers and other departments are built on open communication and collaboration. Regular meetings and information sharing help ensure a clear understanding of project goals and improve efficiency. Successful collaboration contributes to a better final product and increased user satisfaction.
The traditional approach of strictly dividing a company into departments, each performing only their own portion of the task, is becoming increasingly outdated. This approach slows communication, which negatively impacts work efficiency. It is important for employees to actively communicate and share knowledge, thereby creating a more flexible and productive work environment. Improved communication between departments facilitates rapid problem solving and increases overall company productivity.
In our practice, the process of working on a major feature begins with the formation of a cross-functional team of three to six people. The team may include developers, testers, analysts, designers, and front-end developers. Within this small group, members independently determine the most convenient working methods. The composition and number of such teams are not fixed and vary depending on the specifics of each specific feature. This approach allows for the efficient use of resources and the ability to adapt to changes in the project.
How to Form Team Values and Communicate Them to Everyone
Product strategy is formed based on a deep understanding of user needs, market analysis, and competitive environment. This process begins with identifying the key goals and objectives to be achieved. After that, it is important to create a clear and understandable description of the product vision, which will serve as a guide for the entire team.
To effectively communicate the strategy to the developers, I use several methods. First, it is important to organize working meetings during which all team members can discuss the strategy and ask questions. This helps create a shared vision and understanding. Second, I create documentation that details all aspects of the strategy, including the target audience, key features, and benefits of the product. This approach ensures information is accessible and allows the developers to better navigate the tasks.
I also actively use visual tools, such as diagrams and flowcharts, which help clearly present the strategy and its elements. This makes complex information easier to understand and facilitates better assimilation. Regularly updating this documentation and openness to feedback from the team help keep the strategy relevant and adapt it to changes in the market and user needs.
Our products have specific functionality aimed at normalizing large volumes of data. We strive to properly combine information and create a universal standard for the company's customer data. To achieve this, we use clear metrics such as data processing speed, result quality, error rate, and our competitive position in the market. These metrics help us improve our solutions and ensure a high level of customer service.
There is an aspect of our strategy that is less predictable. Unlike SaaS services, which have a constantly growing customer base, we only have a few dozen customers. New customers appear on average once or twice a year, and their requirements can vary significantly. For example, a customer might request data volume or online load that exceeds all our previous projects combined. This creates unexpected challenges that are impossible to predict. We've encountered similar situations before.
In our small team, close communication with the developers is essential. I actively communicate business goals to them so everyone is on the same page. We don't overload the process with multiple levels of OKRs, as everyone clearly understands their tasks and goals. Effective communication helps us achieve success and deliver projects on time.
We don't do custom development, as our business model differs from this approach. We can't satisfy all clients' needs, so it's important to maintain the core focus of our product. This requires close integration between product management, presales, and the development team. This will help avoid desynchronization and ensure that the introduction of new features does not lead to a new direction or fork that is inconsistent with the existing product core.
Team Planning and Management
Do you have planning methods such as long-term, medium-term, quarterly, monthly, or sprint planning? The right planning system allows you to effectively manage time and resources and achieve your goals. Determine which system is best for your work to increase productivity and improve results.
Long-term planning is relevant in the context of large-scale projects. For example, we have a component responsible for finding duplicates, which involves comparing all records against each other across large volumes of data to identify similar ones based on certain criteria. This task is distributed across several products: one part is solved in one application, another in another, and the final information is collected in a third. We successfully managed this process, but soon realized that with our current approach, in two years we would be faced with data volumes that we would not be able to process in an acceptable timeframe. This highlights the importance of strategic planning and adapting to growing data volumes to ensure the system's efficiency and performance in the future.
Long-term planning is a key aspect of successful business development. We set a meaningful goal that we worked towards over several years, leveraging the work of several teams. A crucial step was implementing this goal in a way that ensured all clients continued to receive high-quality services without interruption. This process took two and a half years.
Operational management in my team includes several key processes from which tasks arise. The foundation is the product roadmap, which captures significant features and changes planned for the year. In this first stage, tasks are formed at a high level by quarter, after which they are detailed down to specific tasks and distributed among sprints, taking into account available resources. This approach ensures effective project planning and implementation, which contributes to the achievement of the company's strategic goals.
As our clients grow in size, so does their need for rapid implementation of necessary features. Our primary goal is to ensure profitability, and if a client is willing to invest in functionality that fits seamlessly into our core, we are happy to accommodate it. We organize our project work with clear deadlines and a flexible roadmap that, although divided into quarters, remains adaptable.
The product is in production, allowing us to receive ongoing feedback from users. Based on this information, we plan improvements, fix any bugs that may arise, and make minor changes that take no more than one business day to implement. This iterative work contributes to improving the quality of the product and user satisfaction.

Special time is allocated for refactoring, for example, One day a week. This allows the team to focus on improving the code, increasing its quality, and simplifying future maintenance. Regular refactoring helps eliminate technical debt and improves application performance. Dedicating time to this task is an important part of the development process, as it helps prevent the accumulation of problems and makes the code more readable.
We tried various methods. Previously, we allocated a dedicated day for this, but it was not effective. The problem was that remaining tasks from previous days interfered with focus, and one day was not enough to address more serious issues. As a result, we were only able to fix minor defects.
We implemented technical releases as a separate sprint focused exclusively on resolving technical debt and refactoring. We maintained this practice for a year, but soon realized that we could not dedicate a full sprint to these tasks, as we had commitments to customers with set deadlines. As a result, we began planning refactoring and technical debt removal in each sprint, based on available resources. In most sprints, we were able to include small tasks that took one or two days. In some cases, we even found it possible to dedicate an entire sprint to working on technical aspects.
How to Translate a Business Problem into Developer Language
The line between business problems and developer tasks is often blurred, but it can be clearly defined. A business problem is formulated with an emphasis on the needs and goals of the company, for example, increasing sales or improving customer service. A developer task, on the other hand, requires a technical approach, including defining the architecture, technologies, and algorithms.
Translating a business problem into a technical one occurs through the process of analysis and decomposition. First, it is necessary to understand how the business goals relate to specific product features. Then, based on this information, developers can create clear and measurable tasks that can be implemented using programming and technology.
Therefore, it is important to maintain communication between business analysts and developers to ensure clarity and efficiency in the transition from business problems to technical solutions. This collaboration helps create a product that not only meets business requirements but is also implemented using modern technologies.
Solving tasks largely depends on the team working on them. We have a small group, and there are no strict standards for formulating tasks. There is a common understanding of the approach to describing tasks, but the specific execution depends on the developers and analysts. If a developer has questions, they can be identified during the planning stage, which helps avoid misunderstandings and improves work efficiency.
Each task should have a clear business formulation that explains its purpose. It is important that each employee understands why they do their work, what value it brings, and to whom exactly. Motivation based on an awareness of the significance of their work contributes to increased efficiency and engagement. This understanding helps not only in achieving individual goals but also in achieving overall business objectives.
Regularly performing tasks such as "rename this field" or "add a table" without a deep understanding of their purpose, processes, and potential benefits for the company can lead to demotivation of employees. It is important to understand how each task fits into the overall strategy and how it can affect the financial results of the business. Covering these aspects not only increases motivation but also leads to more effective task execution, which in turn contributes to the achievement of corporate goals.
How Sprints Work
Now let's take a closer look at a sprint. A sprint is a key part of the Agile methodology, representing a period of time during which a team works on a specific task or project. Typically, a sprint lasts from one to four weeks.
At the beginning of the sprint, the team gathers for a planning meeting to define the goals and tasks to be accomplished. Participants discuss priorities and break the work down into smaller tasks that can be completed during the sprint.
While completing the tasks, the team holds daily standups to discuss current progress, emerging issues, and plans for the day. This allows for a prompt response to changes and maintains a high degree of transparency in the work.
At the end of the sprint, the team holds a retrospective to analyze the results, discuss what went well, and what can be improved in the future. This allows the team to continuously improve its processes and increase efficiency.
Thus, a sprint is a structured and effective way to organize the team's work, ensuring flexibility and the ability to quickly adapt to changes.
Over the course of our work, the team has undergone significant changes. We have significantly increased our headcount, and the COVID-19 pandemic has had a strong impact on us. Previously, most employees worked in the office every day, with offline meetings held twice a week, using boards and cards to organize processes. Now, we've adapted to the new conditions and successfully continue collaborating remotely, which allows us to maintain high productivity and efficiency.
During the lockdown, we switched to a completely remote work mode, and not all employees have returned to the office yet. Some of the team continues to work remotely, while the rest have chosen a hybrid format. We've adapted to the new conditions, although before the pandemic, I had doubts about the effectiveness of remote work.
Previously, we analyzed a set of tasks estimated by analysts based on the time and resources required to complete them. These tasks were organized into separate fields in Jira. We collected the volume of tasks for a sprint, taking into account its capacity, and prioritized them based on importance, complexity, and the number of customers. This approach allows us to effectively manage projects and achieve goals on time.
We used two-week sprints. Synchronization meetings were held once or twice a week to discuss current tasks, their stages of completion, and any issues that arose. By the end of the sprint, a clear understanding of what had been accomplished and what remained unresolved was achieved. Following the sprint, a release was issued, which underwent regression testing for specific customers. The builds were then transferred to technical support for implementation. This approach ensures effective project management and minimizes development-related risks. Since customers are large companies, feedback from them was delayed. We then held a retrospective: after each sprint, we met to discuss positive and negative aspects, as well as changes that needed to be made to the workflow. This helped us improve the quality of our work and increase customer satisfaction. The pandemic brought significant changes to the team's work processes. The team, with a high level of collaboration, successfully adapted to the new conditions. All synchronization rituals were eliminated, as team members began to understand each other without words. The workflow became more efficient, and delays were minimal. Retrospectives were held every two sprints, which allowed us to maintain a focus on results and process improvement. Difficulties arose as the team grew. The addition of new employees disrupted the previous mutual understanding that had existed without additional rituals. In response to these challenges, we implemented a mini-team format, each focused on developing specific functions and creating effective processes around them. This solution improved communication and increased productivity.
We had two approaches. If team members knew each other, they could get by without additional rituals. However, when newcomers joined the team, which happened quite often, synchronization was necessary. This allowed us to quickly receive feedback from new team members and provide them with effective support.
Retrospectives became a hot topic for us. We hadn't held them in a long time and tried various formats, but hadn't yet found the optimal solution. We decided to focus on case-based retrospectives. If problems arise during the development of a function or interaction, we assemble a team of 10 people familiar with the situation and analyze the case in detail. This approach allows us to identify the causes of failures and develop effective solutions for future projects.
When estimating the scope of tasks, poker uses both a formal process and an intuitive approach. Teams often use a planning poker method, where each member votes on their estimate based on their own assumptions and experience. This allows us to gather opinions and reach a consensus. This approach ensures a more objective assessment and minimizes the influence of subjective factors. Thus, by combining formal methods and intuitive estimates, we can achieve a more accurate understanding of the scope of tasks.
Poker is not used in our process, but the planning method has changed significantly. We have come to the conclusion that there is no need to gather all participants for a single general meeting. We currently use an asynchronous approach to task estimation. This process is carried out in a general chat where tasks are received for estimation. One specific person is responsible for estimating, but all participants can see the estimates and make adjustments if necessary. This approach allows for greater flexibility and efficiency in the planning process.
After the estimation, the planning stage begins. In this process, the sprint is filled taking into account available resources, task estimates, and previously determined priorities. It is important to remember that proper planning contributes to the effective distribution of work time and increases team productivity.
How to evaluate whether the team has completed the task
What happens next? Are there any criteria by which one can determine whether the task has been completed well? When is the work considered accepted? These could be tests, code reviews, and other factors. It is important to establish clear standards that will help evaluate the quality of the task’s completion and ensure that all requirements are met.
A year and a half ago, we did not conduct code reviews, since all the developers had sufficient experience. However, as the team grew, the need arose to conduct code reviews as needed. In the process, we realized the importance of creating an ongoing process. Currently, Jira has a separate status that allows you to assign a reviewer. They conduct a code review of the task, and only then is the task considered complete. This improves code quality and team collaboration.
Each task is assigned a closing tester, who further enriches automated tests with scenarios. The testing process is fully automated. We use our own data-driven testing framework, which enables efficient data management. This approach requires defining the initial and final states of data and performing operations between them, which forms test cases. Testing is performed using the framework at various levels, including the service level and full integration testing. At the integration level, we launch two or three of our products that interact with each other, allowing us to test their compatibility and functionality in real-world conditions.
The condition for a task to transition to the resolve status is the absence of failed tests. Our testing system includes tens of thousands of tests. Next, we analyze the results together with the tester, determining which tests failed correctly and which did not. If any issues are identified, the task is returned to development for further debugging. This approach ensures high product quality and minimizes risks during the development process.
Developing new functionality is an important stage in the product creation process. Let's consider a specific example of adding a website search function.
At the initial stage, the team collects requirements, determining which parameters need to be taken into account in the search engine. After this, an interface prototype is created that demonstrates what the search function will look like. During the development stage, programmers implement algorithms that ensure effective data search, as well as integration with the database.
After development is complete, the function undergoes testing, where its performance and accuracy are checked. It is important to ensure that users can quickly and easily find the information they need. After all detected errors are fixed, the function is launched.
Thus, the example of developing a website search function demonstrates how a complex process, including requirements gathering, prototyping, programming, and testing, goes from idea to implementation. This approach ensures the creation of a high-quality product that meets user expectations.
When support requests related to performance issues arise, a prompt response is necessary. If our service has begun to process requests more slowly, it's worth conducting a comprehensive analysis. A good start is to check server load and identify any infrastructure bottlenecks. It's also helpful to analyze logs and identify possible causes of the slowdown. Optimizing code and database performance can significantly improve service speed. Regularly monitoring system performance is essential to proactively identify potential issues and address them promptly.
We've developed a specialized process and implemented a number of useful features that simplify our product's performance analysis. When certain triggers occur, such as an increase in response time for a specific API method, the system automatically activates profiling. Flight Recorder is launched in this case, allowing for effective performance monitoring and analysis.
We collect data using nmon, which allows us to analyze the status of the processor, disk, and other system components. All collected metrics are then forwarded by a support engineer to the developer for analysis. After this, two scenarios are possible.
The first problem, which can be resolved in 10 minutes, is excessive database access. For example, requesting the same value three times results in unnecessary resource usage and slows down the application. Optimizing database queries not only speeds up the process but also reduces the load on the server. It is recommended to use data caching or store results in variables to avoid repeated requests. Improving application performance is directly related to effectively managing database requests.
The second, more complex type of problem arises when the nature of the problem is clear, but its solution requires significant resources. An example is refactoring an entire module. Implementing such changes immediately isn't always practical, so we begin planning. It's important to analyze whether other customers have encountered similar problems. We also estimate the frequency of this problem's recurrence in the future: if it occurs frequently, it makes sense to schedule its solution for the next sprint. The next stage involves detailed development planning and the development process itself. This approach allows for effective resource management and minimizes risks.
How can I tell if the problem has been resolved? One of the simplest ways is to deploy changes to production and observe the results. However, we have four different stress tests tailored to different databases. We use these rigs to simulate the average workload and typical state of the data our customers work with. This allows us to more accurately assess the solution's effectiveness and minimize risks when implementing updates.
We analyze metrics and apply chaos engineering methods to simulate complex situations. This includes increasing database response latency and changing hardware parameters while the product is running. Such approaches help us better understand how the system reacts to non-standard conditions and ensure its stability and reliability.

