Feature vs Component Teams

General Agenda

6:30 - 7:00pm - Open networking & Announcements

7:00 - 8:30pm - Presentation

8:30 - 8:45pm - Q&A, Open networking (hard stop at 8:45pm)

=========================================

Overview

A feature team is a cross-functional and cross-component team that can pull end-customer features from the product backlog and complete them. A component team focuses on the development of a component or subsystem that can be used to create only part of an end-customer feature. Organizations tend to favor component teams, which is a poor long-term bet. In this talk I discuss the trade-offs of feature vs. component teams and provide strategies for how best to blend the two to achieve the fast, flexible flow of features while maintaining the integrity of core components.

Bio

Kenny Rubin is Managing Principal of Innolution, a company that provides Scrum and agile training and coaching to help companies develop products in an effective and economically sensible way. A Certified Scrum Trainer, Kenny has trained over 18,000 people on agile and Scrum, Smalltalk development, managing object-oriented projects, and transition management. He has coached over 200 companies, ranging from start-ups to Fortune 10. He is the author of the best-selling book Essential Scrum: A Practical Guide to the Most Popular Agile Process. He was also the first managing director of the worldwide Scrum Alliance.