this post was submitted on 18 Oct 2023
213 points (93.8% liked)
Technology
59373 readers
8209 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can see this being an issue in an agile development environment.
Work gets assigned points based on various factors. You learn how many points a team can do every X weeks (all teams will be different, each team tries to hone in on what they can do and how they number it)
If you complete all your work, great! If you don't, that's okay too, but if you complete early, you're still supposed to take more work. Maybe it's something that QA doesn't need to test so it doesn't mess up everyone else. Documentation, experimenting on something, or maybe QA does have bandwidth to test it too. Either way, you do something.
If you can never finish it all, you figure out why and adjust the total points you can take each period. If you always have left over time, you figure out why and increase the points you can take. If it's a one off reason, don't change anything.
But if "I did all my assigned work" is the answer to then slacking off, that's not what it's supposed to be. All tickets done doesn't mean don't do more.