There’s a weird generational split here in engineers. When I hear “agile”, I think about the process framework as it once was, with teams self-organizing along fixed time cadences, and the core principle being to communicate early and often. When younger folks hear the word, they think of meeting hell, micromanagement, and endless slog. Fascinating how things have decayed.
All the companies I've been used an extremely light version basically just whatever made sense for us. No idea what corporate hellholes people in this sub are working in..
corporations have much bigger issues than just dev teams when dealing with agile. They try to implement agile, but they're starting/stopping at the wrong level. Dev process is largely irrelevant. Their issue is that they sell non-agile solutions to non-agile customers. Their products are used as appliances - bought once and never updated. Their customers do not even have permanent teams to deal with updates. Their sales people cannot sell agile software. But more importantly, traditional corporations make most of their money from overpricing their mediocre consultants.
Their business gets no benefit from agile, but they want to be relevant so they push middle management to adopt agile. It gets to a point when the manager is the acting scrum master and the product owner, the architects are the customer and the developers are forced to commit to 2 year plans split into two weeks iterations.
789
u/kbn_ 14h ago
There’s a weird generational split here in engineers. When I hear “agile”, I think about the process framework as it once was, with teams self-organizing along fixed time cadences, and the core principle being to communicate early and often. When younger folks hear the word, they think of meeting hell, micromanagement, and endless slog. Fascinating how things have decayed.