3 ms·
Her description strikes me as containing so many process problems. All of this could be avoided with a kanban-style process with clear WIP limits, a visible bac
by wpietri 8y ago
Her description strikes me as containing so many process problems. All of this could be avoided with a kanban-style process with clear WIP limits, a visible backlog, and small units of work with frequent releases.
I guess the whole adventure thing rubs me the wrong way. It reminds me of one of my favorite bits from Rick and Morty: "The thing about repairing, maintaining, and cleaning is: it's not an adventure. There’s no way to do it so wrong you might die. It’s just work."
- vidarh 8y agoTwo issues with this: 1. You're not always in a place to enforce process, so you may have no way of getting that visibility. 2. No matter the process, at some point you have a unit of work that people might answer "working on it" or "it's more effort than expected" or similar. The effect per unit of work may be lower if the unit of work is small, but it is still useful to think about how to get visibility when the communication is faulty (as it clearly is if someone is saying "working on it" when they've not even started). This can apply to a months long project or asking someone to do a task that should take an hour - it has nothing to do with the overall project management, and everything to do with validating your inputs.
- wpietri 8y agoI partly agree on #1. Although if someone is in the position to request work, they're in the position to influence process, and to request discussion of process. So I think "no way" is too strong. I think #2 is definitely false. Last time I started a company we used a kanban board, strong WIP limits, daily stand-ups, pair programming with pair rotation once or twice a day, and units of work that averaged a day in size. We never had a need to distrust what somebody told us. Even without all that, if units of work are sufficiently small, task flow is transparent, and your WIP limits are sufficiently low, then there's no reason to be getting into people's business on a task-by-task basis. If there's a real problem, it will be visible at the normal scale. In my view, a good process doesn't demand trust. It creates it over time.
- vidarh 8y ago#2 is only false at very small scale. At some point you're going to rely on an external supplier for example.