HackerTrans
TopNewTrendsCommentsPastAskShowJobs

bfuclusion

no profile record

comments

bfuclusion
·قبل 6 سنوات·discuss
From a pure engineering standpoint, you're correct. But after starting my own company I have a different opinion: The idea that any work is "Worth doing" more than 10 minutes ahead of time is kinda specious. Everything needs to be evaluated against what's going on RIGHT NOW. People aren't necessarily being unreasonable to interrupt, it's just that the whole picture might not be obvious. Of course there are those who interrupt when they know better, but no process will stop that.
bfuclusion
·قبل 6 سنوات·discuss
You're conflating not knowing (or caring) what's going on with a meeting. You absolutely should care what's going on with a team, because if you're work isn't affecting each other there's little reason for you to be a team. That communication shouldn't be every day though, it should be constantly available to whoever needs it at the time they need it.

Software can achieve this, and it's what my startup is trying to make happen. The key is to unify status-as-in-state with status-as-in-active-communication so the two can inform each other.
bfuclusion
·قبل 6 سنوات·discuss
Standups in low performing teams degenerate into managerial oversight and "reporting". That's both demoralizing, and forces people who hate it out of the company. Standups in high performing teams are usually less useful because it doesn't really matter what process you use. Your best bet is one that lets them collectively agree on what to do, and then get out of their way.
bfuclusion
·قبل 6 سنوات·discuss
Your comment is a symptom of a larger problem. Sprints make the assumption that you've got some set block to "work on these things". It's just not true. Business is a live environment and priorities change quicker than that for both good and bad reasons. You should be asking the question "Is this something I should be doing" EVERY time you take a task, so doing that once a sprint isn't often enough.
bfuclusion
·قبل 6 سنوات·discuss
Yeah, that's why I built my startup. Status is not a discrete event like standups pretend, but you also need a tool set that lets you raise issues without breaking people's flow. The proper way for this to work is to have your workflow system enforce some structure on severity and types of communication, and just notify you in priority order when you're ready to handle stuff. Shameless plug: my startup is Uclusion (https://www.uclusion.com)
bfuclusion
·قبل 6 سنوات·discuss
If anybody wonders what 'irony' means, this is it.