4 ms·
> 's the division of work into tiny boring pieces This is only useful if you want to ship changes iteratively. If you're working a on a big blob of a thing tha
by robertlagrant 4y ago
> 's the division of work into tiny boring pieces
This is only useful if you want to ship changes iteratively. If you're working a on a big blob of a thing that can have waterfall-style estimation and delivery then you'll avoid all that.
> it's the detachment of engineering from product, I suppose
This is more likely the cause. The emergence of product as a ruling class over engineering is a problem. Product is a useful concept, but I think we've all assumed only a person with a Product job title can be a product owner in a team, when I think Product adds much more value as a slightly more distant integration point for engineering, marketing, sales, customer support, legal, etc.
- Viliam1234 4y ago> If you're working a on a big blob of a thing that can have waterfall-style estimation and delivery then you'll avoid all that. It seems that among the cool kids, "waterfall" is considered a bad thing that everyone should avoid. I admit I miss the days when I could have spent weeks working on a project without being interrupted by daily "agile" meetings.
- robertlagrant 4y ago> I admit I miss the days when I could have spent weeks working on a project without being interrupted by daily "agile" meetings. I think if there's no team you need to talk to very often and you're working in a pretty static environment then you should be fine. It's just that a lot of those nice problems are harder to come by these days.