4 ms·
This is about making teams completely responsible for the product as you possibly can. Maybe even profit/loss responsibility. The idea being they're closer to p
by UK-Al05 7y ago
This is about making teams completely responsible for the product as you possibly can. Maybe even profit/loss responsibility. The idea being they're closer to product then anyone, and thus should make better decisions.
If you follow the feature factory route, the team will just produce things they are told too. If it doesn't work, it's not the teams responsibility. They did what they were told to.
- loopz 7y agoThis is pinnacle of old style dev. It just doesn't make much sense unless devs become stakeholders.
- UK-Al05 7y agoDevs are stakeholders in a project by definition. Stakeholder is anyone with an interest in a project.
- wruza 7y agoOtoh, those who “tell” are closer to the business/client, and thus should issue better requirements. I honestly can’t see what’s wrong with doing what you’re told to. You cannot play a jack of all trades and program the damn thing perfectly at the same time. (And if you can, you should not waste your time bringing profits to that Corporate, Inc anyway.)
- UK-Al05 7y agoTeams that take ownership have a product person, who sits with the team. And is part of the team. Their entire job is work out the best product direction. They interact, sit with, pair, answer questions from developers everyday, talk to customers etc. Work with the team to set future product direction. It shouldn't be external group pushing features into a team backlog. Devs talk to customers, look at the logs, debug issues, look at the stats being logged out. As result they have far better understanding of product usage than most people higher up.