A "self-organizing team" has the authority to choose the work that it will perform and the responsibility to do that work in the way that it chooses.  These are important aspects of a self-organizing team:

• The team selects its own work. At the beginning of a work cycle, the team collectively selects the work from the prioritized project work. Work selection is performed within given constraints, including the priorities set by stakeholders, time (such as the length of the current work cycle, iteration or project increment), the budget, and the skills of team members.
• Individuals select their own work. Someone will choose to do something because they are good at it and know that they can do the work effectively, because they want to gain more experience at something and hope to improve their skills by working with someone with such experience, or because they know that the work needs to be done and that it's their turn to do so. Although an individual fulfills one or more roles on a project team, that doesn't imply that the person is constrained to doing only specific types of work.
• The team determines how to perform the work. At the beginning of a work cycle, the team holds an "all hands" planning meeting where it determines the general strategy for doing the work and the tasks required for that. More detailed planning, if required, will be done on a just-in-time basis by the individuals doing the work. Notice that the team is still constrained by your organization's standards, technical infrastructure, regulations, and so on.
• Everyone commits to the work. The team commits to accomplishing the work that it has agreed to do by the end of the work cycle. Individuals also commit to doing the work that they say they will do in that cycle, although as the time progresses, various tasks may be renegotiated as required.
• The team coordinates regularly. To ensure that the work is accomplished, the team must coordinate its efforts effectively. This is typically done through daily standup (scrum) meetings of the team and impromptu discussions between individuals.

This is a participatory approach to decision-making, where everyone has the opportunity to provide input and to listen to the decision-making process. The goals are to make decisions at the right place within the organizational structure and to empower teams by giving them both the responsibility and the authority to get the job done. Giving them control over their work improves motivation among team members and, thereby, their productivity.

Project manager responsibilities

There is still work for the project manager on self-organizing teams:

• Provide leadership. Team culture and project vision must be nurtured and must evolve throughout the project, and direction must be provided to the team.
• Mediate disagreements. The manager must be prepared to step in and make a decision when other team members are unable to reach a decision.
• Ensure that team members increase their skill sets. From time to time, the manager may need to motivate individuals to take on new tasks that are outside of their comfort zones or to work with others to help those people gain new skills.
• Ensure that the team respects their limits. Self-organizing teams have the authority to make decisions within the scope of their responsibility, but that doesn't mean that they get to rethink everything that they feel like changing. For example, the development team must still conform to the technical infrastructure and to the business strategy of your organization; they probably do not have the authority to change these things even though they may not fully agree with them. When an issue falls outside of their scope of responsibility, the team must either accept it or collaborate with the people with the appropriate authority.
• Summarize the project plan. External stakeholders, such as senior management or business representatives not actively involved with the team, will want to know the current status of the project and the team's current plans. The project manager may be required to summarize and communicate this information to those people.

What "self-organizing" does not mean

The concept of self-organizing teams often sounds like anarchy or non-management to traditional IT professionals, but this is not true. Although self-organization relies on team members being responsible and mature, it is tempered by the guiding hand of a good project manager. It is also tempered by organizational standards, infrastructure, and external regulations. "Self-organizing" doesn't mean that you have complete freedom to do what you want.

Self-organization isn't necessarily a consensus-based approach either. Sometimes, individuals will disagree with a decision but will choose to go along with the will of the team. Consensus decision-making isn't ruled out by this approach. but it certainly isn't required.