We’ve converted the ‘Development Team’ definition from the 2013 Scrum Guide into cartoon form to illustrate the role of the Development Team in Scrum.
The Development Team
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.
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 of the skills as a team necessary to create a product Increment;
• Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule;
• Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; and,
• Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
Development Team Size
Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to manage. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog
Take the Quiz!
About the speakers
Mr Scrum Master
Hello! I'm the Scrum Master, it's nice to be featured here on SSW TV :)
It’s important for anyone involved to know the basic video editing terms to keep feedback clear and concise.
Please don’t say just ‘Hello’ in chat. It’s as if you called someone on the phone and said “Hi!” and then put them on hold!
Phones have ruled our digital experience for over a decade. But where will we go for information and how will we expect it to be delivered?
This session will cover Sammy’s 3-year journey of starting in a small company and building it to become a multi-award winning organisation
After COVID the world was forced to exist remotely. Will it be the way all companies move forward into the future of business?
When asking for changes to be made to any file like a web page, Word document, PowerPoint slide, or code, always include the original version of the content (“X”) together with the changes you require (“Y”).
Are you about to embark on a new Azure project? Do you want to know how much it’ll cost to run? And everyone needs to get the cost down on their current project. Right? 💸
Can we save costs and future proof our products? Let’s use Power Apps and new development strategies.
Running events is a challenge. And making sure your speakers and attendees are happy is an even bigger task. Adam and Jakob discuss keeping conferences interesting and adding value to future events.
App modernisation can be daunting task and could include unnecessary technical debt. Let’s find out how we can navigate the future.