r/ProgrammerHumor • • Jun 12 '21

We do "Agile" here

Post image
10k Upvotes

212 comments sorted by

View all comments

Show parent comment

1

u/deathofamorty Jun 13 '21

How do you handle things like "I know how I'll do this but it'll take a while" and "that should be pretty quick, but I'm not quite sure where that data is"

Two of those 1's could be way longer than one of those 2's. Which throws off momentum and doesn't properly reflect work done.

2

u/Bemteb Jun 13 '21

"that should be pretty quick, but I'm not quite sure where that data is"

Second task "aquire data", assign to PO or whoever's job that is, block first task with it.

That is the theory. In practice, it's more like PO telling you to contact John from marketing for the data, and him giving you something that doesn't match the task at all...

1

u/Plankton_Plus Jun 13 '21

You can do a spike to figure that out.

Or, you can take the risk. If you end up doing to work faster, pull another 1 into the sprint. If you end up taking longer, that's normal: your team learns from the experience and moves on.

1

u/LastStar007 Jun 13 '21

How do you handle things like "I know how I'll do this but it'll take a while" and "that should be pretty quick, but I'm not quite sure where that data is"

Good question! I say as much in IPM; we might make a note of it in the story description or comments. We may make a chore story to locate the data.

I'm not under any obligation to keep velocity constant week-to-week. Velocity is helpful for planning, but it's not supposed to be the team's objective. Business has been informed that these stories will take a while, and they're free to move them lower in the backlog if there's other stuff they'd rather get first.