How we are working
Today we want to open the veil and talk about several secret practices of our company . We make the TargetProcess flexible project management system. We hope that the practices will help you understand our values and vision better.
We have a special role of a caretaker for functional tests. The role is rotated, every day different people are responsible for the tests. A person in this role improves green tests and comments on reds. Tests become better and more stable over time.
To designate SFUT developer we have a cat. The cat sits all day on the table near the SFUT and smiles.
')
During the daily meeting, the cat is transferred from one developer to the next through the list.
Every day at 11 am we have a stand-up meeting. It usually takes no more than 15 * minutes for 15 people. Over the course of a year, we measured the time of the meeting and found that most people spend 3.14 minutes describing yesterday's and today's affairs.
Current progress is displayed on the big screen:
Developers with the lowest individual performance over the last week are assigned to the most complex bugs. Practice has shown that this is a great way to increase the productivity of the whole team, no one wants to deal with complex bugs and everyone is trying to work harder to avoid such a sad fate.
We used to have boring and long meetings for prioritizing work. It turned out that the statistical assessment of priorities is much more effective than human. We have developed an extremely complex prioritization algorithm based on the Gödel incompleteness theorem and Bayesian probability. The algorithm works surprisingly for sure!
The user interface is extremely simple. Owner's product clicks the button before the release planning meeting, and that’s it! We can only discuss user Story.
We are starting to think about removing the role of Product Ower from the team. Statistics (we love statistics very much) shows that there is practically no dependence on who exactly presses the prioritization button.
Algorithm for automatic assessment user Story also on the way. We tested the basic concepts and hope to include it in the next release of our system . It will save a lot of time for thousands of teams around the world!
The usual way to assign a job is pretty boring. We are always looking for ways to make things more fun. Now every developer can quickly and easily take on an interesting task:
We believe in bootstrapping. Our company has grown without any external investment. We hire people who share our vision. We do everything to create real Spartan conditions. Here is a typical developer workplace:
We really appreciate the training and make people learn as much as we can. For example, here sits Sergey. He read a stack of books on the right in the last week. He is obliged to read a stack of books on the left for the remaining 3 weeks this month. On average, each developer reads 100 books a year.
We hope that some of our practices will seem useful to you and allow you to increase the productivity of the valuableresources of people in your company.
Caretaker for Functional Tests (SFUT)
We have a special role of a caretaker for functional tests. The role is rotated, every day different people are responsible for the tests. A person in this role improves green tests and comments on reds. Tests become better and more stable over time.
To designate SFUT developer we have a cat. The cat sits all day on the table near the SFUT and smiles.
')
During the daily meeting, the cat is transferred from one developer to the next through the list.
Daily meetings
Every day at 11 am we have a stand-up meeting. It usually takes no more than 15 * minutes for 15 people. Over the course of a year, we measured the time of the meeting and found that most people spend 3.14 minutes describing yesterday's and today's affairs.
Current progress is displayed on the big screen:
Developers with the lowest individual performance over the last week are assigned to the most complex bugs. Practice has shown that this is a great way to increase the productivity of the whole team, no one wants to deal with complex bugs and everyone is trying to work harder to avoid such a sad fate.
Priorities and performance evaluation
We used to have boring and long meetings for prioritizing work. It turned out that the statistical assessment of priorities is much more effective than human. We have developed an extremely complex prioritization algorithm based on the Gödel incompleteness theorem and Bayesian probability. The algorithm works surprisingly for sure!
The user interface is extremely simple. Owner's product clicks the button before the release planning meeting, and that’s it! We can only discuss user Story.
We are starting to think about removing the role of Product Ower from the team. Statistics (we love statistics very much) shows that there is practically no dependence on who exactly presses the prioritization button.
Algorithm for automatic assessment user Story also on the way. We tested the basic concepts and hope to include it in the next release of our system . It will save a lot of time for thousands of teams around the world!
Cool appointments
The usual way to assign a job is pretty boring. We are always looking for ways to make things more fun. Now every developer can quickly and easily take on an interesting task:
Workplaces
We believe in bootstrapping. Our company has grown without any external investment. We hire people who share our vision. We do everything to create real Spartan conditions. Here is a typical developer workplace:
Education
We really appreciate the training and make people learn as much as we can. For example, here sits Sergey. He read a stack of books on the right in the last week. He is obliged to read a stack of books on the left for the remaining 3 weeks this month. On average, each developer reads 100 books a year.
We hope that some of our practices will seem useful to you and allow you to increase the productivity of the valuable
Source: https://habr.com/ru/post/141083/
All Articles