this post was submitted on 29 Nov 2024
121 points (80.4% liked)
Technology
59772 readers
3162 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you are properly using either of those it's very easy to tell if someone's not pulling their weight or is having extreme difficulty in a situation.
As soon as someone starts underperforming in project management constructs, you put more eyes on the task. They're either a legitimately stuck, or they're not working.
They're just tools, and they make it very easy to visualize what's going on.
Exactly.
We use both, and the only people who spend significant amounts of time interacting with the board are project managers (during sync meetings across teams), scrum masters (planning and following up), and product owners (creating requirements). Devs spend a little time adding their own estimates, comments, or moving things along the kanban board, but that's not a lot of time, and that goes for me as a lead as well.
We have 7 or 8 dev teams, three project managers (one per region), and two scrum masters (at HQ, not sure how our outside teams handle it). And honestly, I think our two scrum masters are a little redundant because there's only so much agile that needs to be done.
If a dev (regardless of seniority) is spending more than half a day in a given week on kanban stuff, they're probably avoiding doing their job.