2 ms·
I think your point is kind of what I was alluding to with the 'or makes it [i.e. it exists without it] unapologetically transparent' parenthetical? Certainly i
by OJFord 4y ago
I think your point is kind of what I was alluding to with the 'or makes it [i.e. it exists without it] unapologetically transparent' parenthetical?
Certainly it's not 'scrum' per se that bothers me - I was carefully not saying 'agile' because I think that's fine it's just the typical method of 'doing it' that I meant, but seem to have fallen into a different trap in the process - but it is the breaking down of the job into actionable work pieces, 'tickets', and some of the ceremony around that, whether strictly 'scrum' or not.
But that's just me right, obviously some (lots of) people like it! My initial comment was that it's surprising (to me) how few seem to not like it, so I'm perfectly aware that's just my (and some few others') opinion.
- Ensorceled 4y ago> But that's just me right, obviously some (lots of) people like it! My initial comment was that it's surprising (to me) how few seem to not like it, so I'm perfectly aware that's just my (and some few others') opinion. I guess it's a continuum ... I have people on my team right now that are working on a single story, other people who have a few dozen this sprint. If your team is breaking down what would be a single story on my team ... I could see that being annoying. Now, the developer working on that story has a breakdown of tasks that they are managing as sub items in the story, but that's not getting managed with story points or any other heavy weight system.