How to save products in a team. Pt.1
Let's start with a situation where a developer has some problems on a project, but he is silent about it and does not tell anyone.?Over time, they accumulate, and the process gets out of control.?In this case, it is necessary not only to take prompt response measures, but to heroically save the situation.?Moreover, such problems can happen even when the processes are debugged, and everything looks good.
?What do our colleagues think about this?
?It seems to me that a lot depends on the team and, mainly, on the PM.?An interesting practice was introduced on my last project.?Once every two weeks, we had a call where our QA talked about what worries him about the project from a technical point of view and not only.?Thanks to these rallies, we were able to add many valuable features.?An employee was also heard who did not want to take time at daily rallies with his insignificant, as it seemed to him, ideas.
?How to get those who keep silent to talk about problems??In my opinion, the best solution is to hold events like a retrospective with the most friendly atmosphere, where conversations about problems and ways to solve them are encouraged.?It is important to interview each participant.?After that, the voiced problems need to be solved: the more, the better.?Everyone should see that this tool works.
?Possible solution for a case for a developer
?The main thing is not to be silent, be sure to share the difficulties that have arisen with the team and the leader.?As you know, one head is good, but two is better.?This will reduce anxiety and overwork, stabilize the situation at an early stage with the help of more experienced colleagues and management, brainstorms or adjustments to the scope of the sprint.?It is important to remember that whatever difficulty arises, it can be solved by joint efforts.
?To help the project manager, team leader, product owner
?How to detect such a situation on your project (alarms):
领英推荐
?No one constantly has questions at the daily/general rallies.
?Communication between individual roles is well developed, but there is always silence in the general chat.
?Before the release, there are often issues that could have been resolved earlier.
?What to do in this situation??The most popular methods:
?Build a culture of free but controlled communication.
?Encourage the team to talk about problems at the beginning of work on a task and offer solutions to them.
?Retro is one of the most important tools.?It is necessary to make it work through competent management, the ability to talk to each member of the team and compliance with agreements.
?Ask the performers to describe in their own words how they understood this or that task so that the implementation can be corrected in time.
IT development outsourcing team.?https://getupit.tech