[jackmaney]

> Scrum is not a methodology for writing code, it is for getting a series of tasks done.

0_0 Y...you didn't just write that, right? I'll be unusually charitable and give you a chance to think again about that sentence up there.

> "The story points are there to track productivity" - Oh noes the people paying you want to know how long the project is going to take to be done.

And yet, points aren't supposed to be translated to time intervals..... (Spoilers: in practice, they are.)

[cmdkeen]

What is wrong with that sentence? TFA focuses far too much on the coding aspects of Scrum by asking "what does the senior dev do?", my point is all the things a senior dev does are fit to be tasks or stories in Scrum. It's outgrown being developer focused, and even more literally writing code is a small subset of "software development".

Points don't have to track time intervals to give you a sense of progress. Averages are a powerful thing, hopefully management is focused on long term graphs not getting het up about the number of hours difference between your tasks for two similarly pointed stories.

Oh and Scrum makes no requirement re using story points - it only requires that backlog items be estimated. We estimate tasks in hours and stories in points for instance, Scrum doesn't care. All our Product Owner shows to the stakeholders is a burnup with just numbers on the x axis.

[jackmaney]

> What is wrong with that sentence?

So, writing code has nothing to do with getting a task (of ANY KIND, mind you) done?

Again, do you want to take a moment and rethink that?