Ruben's discussion topic was about how to scale your work groups to support large products. Many groups are organized around the following:
- Product Platform
- Component
- Product Feature
- Job functionality
- Location
One comment that was very interesting was "That which is a feature to a component team is a task to a feature team."
Ruben believes that you should scale your team based on economic factors and tradeoffs. The work of your projects should flow through the collection of teams in an economically sensible way so that you will have maximum lifecycle profits.
He recommends that teams should identify where the technical waste exists. However, recognizing waste in technical development is difficult because it is neither physically or financially visible. So rather than focus on what is invisible, focus on what you can see. Ruben compared this to a relay race. You shouldn't focus on the runners and making sure that each one of them is staying busy the whole race, you should watch the baton (i.e. the product). All you have to do is make sure the baton is taken careen of and you will finish the race. High personnel utilization most of the time doesn't equate to high productivity. You should worry less about what your utilization is because it will find its natural rhythm.
This speaker was very engaging and I would love to get his best-selling book to understand Scrum further.
No comments:
Post a Comment