Agile Practice (2)-Unified Team

What is the purpose of the Unified Team? Need to build a unified Team no?

Scene One: A research and development needs to confirm the demand, find A,a let find b,b let find c,c not, research and development work interrupted

Scenario Two: A test found a problem, research and development requirements to borrow the environment, testing that the impact of its testing work, both white tear.

The two scenarios are very common, and they are very inefficient, and I need an efficient team, so I need to address both of them.

The first problem is that the communication distance is too long to cause the work to pause. I personally hate this, when I like being buck, from A to B to C, and C is not, I can imagine the difference in mood, let alone efficient work. I component team, to their own requirements is to make the team happy work (in fact, high efficiency is very easy to make people work happy, after all, no overtime ~). In order to achieve this goal, I need to respond quickly to the needs of members, in fact, this is the role of the Unified Team PO, in many cases, it is not easy to do this, but if you can do it, the effect is amazing. Based on the previous description, the entire system is reconstructed by my design, my authority on the requirements is absolute, so basically all the requirements I can confirm, do not need to find other people. This, in turn, has left the league members free of distractions and work inertia has continued. Iterative review the good aspect of unified recognition is "clear division of labor, good communication atmosphere"

The second problem is the problem of communication between different roles, and testing colleagues also need to work efficiently and naturally do not want to be interrupted. To solve this problem, my approach is to arrange for a communication, organization-based researcher (preferably influential) to complete the test with a test colleague, who can quickly help test colleagues to solve minor problems and test colleagues without having to struggle with these small issues and improve their productivity. On the other hand, if it is an important issue, the researcher can also assist in locating the analysis and avoiding the impact on the research and development team. And if more people need to be coordinated to locate, the developer can also ensure that people are quickly coordinated to locate. Maximum assurance that the work of the test colleague is not interrupted and works efficiently. (The tool for the developers is very demanding, but this method was also taught by IBM, when I as the role and test colleagues, can clearly feel the entire testing department of the role of the demand, 20 supposedly people take turns ask me, tired of not)

In view of the above share, talk about my views on "the purpose of the Unified Team": to open up the barriers to communication, so that the distance between each other is 1. There are many small cases, such as the need for a PO to take on a lot of external communication responsibilities and avoid affecting members of the team. And when PO is unable to grasp things, need to personally and team members to confirm, without members to organize communication.

There is also a sharing is when the team is relatively large, as I described the team members have 13 people, then PO's work will be very tired. My approach is to find influential people and set them up as Team Leader and share part of the work. In fact, my luck is better, the team has two such personnel, I homeopathic into two groups, these two people's enthusiasm is very high, but also have the intention to help colleagues in the group, while I also ensure that Members have doubts, the team leader should also be clear, so as to achieve excellent communication results. (e.g. I may)

Agile Practice (2)-Unified Team