TK - Development Team

Owned by Samir Sheikh (Unlicensed)
May 17, 2021
2 min read

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. Only members of the Development Team create the Increment.

Basic Attributes of the Development Team

Self-Organizing: The Development Team selects the work that it is supposed to do during the Sprint. No one, not even the Scrum Master/PO tells the Development Team how they are going to deliver the potentially releasable increment.

Cross-Functional: The Development Team has all the necessary skill-set required to convert the selected Product Backlog items into a potentially releasable increment.

Size: The optimal size for the Development Team is 3-9 members. With less than 3 members, the Development Team may not have enough skill-set to create the potentially releasable increment. Having more than 9 members on the Development Team may create additional complexity which might be difficult to be managed with the empirical process.

Title: There is only one title in the Development Team and that is "Developer". Scrum recognizes no other titles. It also discards the notion of sub-teams.

Accountability: The Development team is accountable for delivering an increment of potentially releasable "Done" product at the end of the Sprint. The Development Team is also accountable for the quality of the "Done" product increment as per the acceptance criteria.

Overview of the Development Team

  • Cross-functional, multi-learning and self-organizing, and while individuals often have specialized skills or areas of focus, accountability belongs to the team as a whole

  • Build and deliver the potentially shippable product increment from planning, analysis, design, programming and testing

  • Development Teams tend to have between 3 to 9 team members. Preferably dedicated.

  • Responsible for building the actual product Increment

  • Performs the development and testing of the product

  • Outlines the tasks that need to be completed in order to develop a feature/user story

  • Should be full-time

  • Ideally, membership should change only between sprints

  • Strong Cross Matrix of skillset with Developers having enough insight to ask business questions

  • Works with the Product Owner to drive ambiguity lower

  • Works to continuously improve the application and the methods/processes the team utilizes

  • Members are dynamic with enough experience to be able to handle a variety of coding elements.

Drone project example see: https://tcmarin.atlassian.net/wiki/spaces/DDMP/pages/519438377