Re:The State of Agile Software in 2018
by johan_larson on Wednesday October 24, 2018 @07:57AM
(#18291611)
Agile methods do have a bit of a problem with the concept of authority. They really really want to believe that at least within a development team, everyone is equal. That's not a great fit to actual dev teams in companies where there are junior devs, senior devs, architects, and managers.
[ Parent
| on HN ]
In my experience the power structure within the team is fairly flat, it's the managers outside the team that insist on having authority, micromanagement and veto rights over things they don't understand.
Re:The State of Agile Software in 2018
by JoeAltmaier on Wednesday October 24, 2018 @07:58AM
(#18291616)
I'm thinking they make an effort to accommodate that. The poker idea is to average out the team's estimates which is shown to come to a reasonable number (adding up noisy signals equals a better signal). And the whole scrum thing is explicitly to let mentoring happen organically
Re:The State of Agile Software in 2018
by conradfr on Thursday October 25, 2018 @11:35AM
(#18301687)
A senior dev in an Scrum team is supposed to do the same work as the junior, except faster!
Then they'll wonder why the experienced people quit.
> A senior dev in an Scrum team is supposed to do the same work as the junior, except faster!
Where do Scrum principles/rules/... say that? (I have only passing familarity with, but I haven't seen much that went into more detail than "the development team organizes itself to complete the tasks", which leaves the internal structure open)