2 ms·
This. The people paying for a project want to know how long it will take, how much it will cost, and what the feature set is going to be. This is of course not
by pjc50 4y ago
This. The people paying for a project want to know how long it will take, how much it will cost, and what the feature set is going to be. This is of course not reliably possible, so we end up with an elaborate back and forth that tries to re-impose waterfall whatever the label on the process is.
Similarly, "Individuals and Interactions over Processes and Tools" is really difficult for an organisation to cope with. Everything else in corporate land is about de-personalising and standardising the actions of workers as much as possible, so that they're interchangeable. See manufacturing lines, fast food production, call centres. "Cattle not pets", but for humans rather than servers. Once you start caring about and adapting the work process to individuals, they're not replaceable.
On the other hand, there's comfort in having a bad process. Because then you don't have to blame and confront individuals as people, just over whether they've followed the process.
- Terretta 4y agoI agree with your concern. What’s the alternative? One idea… > the people paying for a project want to know how long it will take, how much it will cost, and what the feature set is going to be. Certainly … if they’re “doing it wrong”. :-) Do VC know any of these things? The agile approach, YC, and the SAFE are predicated on these being unspecifiable to any signficant accuracy. So a better approach may be to: 1. Change the money process from budgeting to investment. 2. Fund capable teams of dedicated fixed capacity, and you can nail budget to the penny. 3. Then, fund by mix of ROX/ROE/ROI* on prioritization of the backlog, and you’ll get out of the team what you chose to fund as the team capacity. Done. * Return on Experience (NPS etc.), Return on Equity, Return on Investment. And consider sharing something like “Implementing Beyond Budgeting” with the money people: https://smile.amazon.com/Implementing-Beyond-Budgeting-Unlocking-Performance-ebook/dp/B01HXJIY80/ https://smile.amazon.com/Implementing-Beyond-Budgeting-Unloc... ** To maintain trust with the money people, engineering cannot employ unproductive teams. It may be the tradeoff for engineers from a terrible budget driven process is better job security, since their individual performance or abilities to output great features matters less to the corporation than the estimation/budgeting/CYA processes do. In the budgeting world, senior executives get rotated out faster than IT teams.