Timeline for Does Scrum turn active developers into passive developers?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2014 at 12:31 | comment | added | Izkata | @MaR That's why the devs don't talk to the customers. The customers talk to the Product Owner and ask for faster horses, the P.O. is the one that sees all the clients' issues, combines and prioritized them, and in the process figures out that cars are better than faster horses | |
| May 3, 2014 at 21:16 | comment | added | DanMan | "Product Owner tells you what to do" - I don't quite agree with that. They ought to tell you what they need. A slight but important difference. In other words: they describe the problem/issue, you provide the solution. | |
| Mar 21, 2012 at 23:38 | history | made wiki | Post Made Community Wiki by thegreendroid | ||
| Aug 17, 2011 at 7:56 | comment | added | Saeed Neamati | +1 @Lukas, because of the differentiation between what and how. Thanks buddy. | |
| Aug 16, 2011 at 19:11 | comment | added | MaR | "Product Owner tells you what to do, but it's up to the Team to decide how to do that." That's exactly what can be a problem for devs motivation: lack of innovation. Most of the time customer will want faster horses, not cars. But I absolutely agree with micromanagement. | |
| Aug 16, 2011 at 14:33 | comment | added | Wivani | Amen to that last line | |
| Aug 16, 2011 at 14:24 | history | answered | Lukas Stejskal | CC BY-SA 3.0 |