Development Teams manage their own work. No one tells them how to do their job.
Development Teams increase transparency of their work and processes, inspect them and adapt their work and actions to synchronize and optimize their efforts so that they can deliver values to their customers.
Here is a quote from the Scrum Guide about “The Development Team” coupled with a nice YouTube video in the end to demonstrate their team work.
The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. A “Done” increment is required at the Sprint Review. Only members of the Development Team create the Increment.
Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness.
Development Teams have the following characteristics:
- They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
- Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;
- Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
- Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis;
- Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
Here is a YouTube video by Mr. Jose Diez. Very nice presentation of how a team should operate as a one piece led by the same goals and the direction. Enjoy!
スクラムの開発チームのあり方を体現する3分ほどのビデオです。作者はホセ・ディーズ氏。どうぞ!