Examples of bullshit business speak here...

[fishfoodie]

So much this, basically invented by developers who hate doing documentation and plans, i have yet to encounter an agile project that has delivered on spec and to time and budget.

As an Infrastructure PM, I have been seconded to a few Agile projects.

It was ok for a few months but always reminds me of the clockmaker scene in Schindler's List - imagine a whole career of Sprints?

Fuck that!

This is interesting, my wife is a fan of Agile working, she describes it as improvement in real time, or some such - it's half past 12 on a Friday night and drink has been taken, so I might not be absolutely accurate here, but the benefits from her point of view is that iterations are put out in the knowledge that it's not the finished product but you get there quicker and more accurately with Agile, as opposed to having nothing for 18 months and then have to debug for another six months to a year after implementation.

Shoot the Kronenbourg here, not the messenger

I could write a War & Peace sized volume on the dislocation between the Agile/Lean promise; & the delivered reality.

Unsurprisingly, the discrepancy is always because Management loves what they hear about what it can deliver; but completely fail to keep focus long enough to pay attention to what THEY NEED TO DO !

Sure, every manager loves to hear about constant deliver, etc, etc; but they never hear the bits about co-located teams; or teams being under a single management, or; most importantly; how Agile/Lean is an ORGANIZATIONALChange !

Lots of Engineers like what they hear when they get the sales pitch; & this is because, lots of what they hear is intuitive; & logical; but then again; it' all predicated on stuff happening in an environment that the Company has precisely zero intention of implementing !

I've gone thru this shit on three separate occasions; & it's never the grunts willingness to buy in that's the problem; it's always the managers, "make it so", attitude that fucks it up.

[mat the expat]

So much this, basically invented by developers who hate doing documentation and plans, i have yet to encounter an agile project that has delivered on spec and to time and budget.

As an Infrastructure PM, I have been seconded to a few Agile projects.

It was ok for a few months but always reminds me of the clockmaker scene in Schindler's List - imagine a whole career of Sprints?

Fuck that!

This is interesting, my wife is a fan of Agile working, she describes it as improvement in real time, or some such - it's half past 12 on a Friday night and drink has been taken, so I might not be absolutely accurate here, but the benefits from her point of view is that iterations are put out in the knowledge that it's not the finished product but you get there quicker and more accurately with Agile, as opposed to having nothing for 18 months and then have to debug for another six months to a year after implementation.

Shoot the Kronenbourg here, not the messenger

Well, as I said, I'm not a Developer - I'm an Infrastructure PM who used to run the Infrastructure the Devs broke.

I prefer variety in my projects - Agile just seems like a hamster wheel to me. I'll do a project if there is nothing else available but it's not my preference


Let's not even start on DevOps

[Paddington Bear]

The concern across the IT landscape about total wfh is that if there's no benefit to co-location at all then most jobs upon replacement can be done by people looking for significantly lower salaries.

I see it more like the situation I was in when I first started in IT - loads of older folks with Gold-plated (TUPE) Pensions, etc who did fuck all work, just came in for coffee and smokes.

I'm happy that the industry is being shaken up - I'm not the old dude in it for the coffee

Businesses will not abandon the head offices - they will just be smaller. As for COLO - everything I've ever supported bar local LAN/WAPs has been offsite since 2012.

Yes but as much as I like India relocation to Bangalore isn’t in my life plan.

[Paddington Bear]

Ticht - Agile can work very effectively as an iterative process, just most people I see using it are using it as an excuse to cut corners

[Ymx]

Unless I’m wrong, the main principle of agile was to deliver on time rather than to spec.

It was a reaction to large waterfall project life cycles which were delivered either very late or were catastrophic failures as risks/fatal issues only come out at final system testing/user testing time.

Agile is to get to as quickly as possible a bare bones functional (single function) system. Where risks can be mitigated early on or understood early to decide if project is still feasible. As well as it provides the opportunity to re evaluate likely timescale to deliver full functionality. Or minimum acceptable functionality.

There is probably an overdone versions of agile and where it’s needlessly used on projects which are in any case less than a couple of months. Plus with daily scrum sessions make it OTT.

But other than that, I see it as a huge necessity for larger projects.

[mat the expat]

Yes but as much as I like India relocation to Bangalore isn’t in my life plan.

That has been happening for Decades - the in/out of outsourcing isn't due to Covid.

Beside, if you're job is that insecure, you can't be any good at it?

[mat the expat]

But other than that, I see it as a huge necessity for larger projects.

What kind of larger project?

[Ymx]

I was mostly talking about software ones. But in general any where there are large risks in uncertainty of being able to deliver to requirements, and where they can be mitigated/known by an early iteration.