It's more like ticking boxes and pretending to know what they're doing than actual agile project management.
So now we're stuck with a lot of overhead crap and even more workload. And the system actually slows us down when we try to adapt to a changing environment.
Problem is mainly that this happened because the director of project management really liked the reports from Jira and thus the main reason for it all is to get as much data as possible in there (notice how 'accurate data' does not seem to be a focus :) )
When you’re doing something for the sole purpose of keeping someone off your back about it then you inevitably half-arse it, so in reality we’re paying Atlassian a small fortune for nothing more than a wall of fairly bullshit estimates. Don’t even get me started on how slow and flakey the UI is on the cloud version, it’s such an intolerably poor quality bit of software to actually use as a dev. I’d be very surprised if Atlassian actually dogfooded the cloud version because it really is an abysmal effort.
And yeah it's slow but not super slow. Pretty sure we have onprem though. Because I can only access it on VPN. Unless they fiddled with some port forwarder which I wouldn't put past them.
So as long as you define what "leadership" or "customer satisfaction" (and the rest) mean to you, and you have a vaguely plausible but not necessarily effective process that ticks each of the boxes, you have a quality management process. And you can apply for - and will probably get - formal quality management certification.
In reality you can have zero actual leadership or customer satisfaction. But you have a process - so OK.
This isn't to say that we should just do away with all process. There are good, even life-saving reasons why processes exist, but a process alone is no cure-all, and an overdose will paralyze us.
- Abstractions/models tend to completely replace reality. We, software engineers, are very prone to that sort of thinking. Another prominent category are accountants: leaders drive their businesses only looking at the "map" of accounts; governments do the same with their constituents.
- "Paralyze" is exactly the right term. Excessive bureaucracy actively discourages any creative action, for the sake of illusion-of-control.
Cannot upvote this post high enough, you made my day. Maybe humanity is not completely hopeless yet.
It was the first time I'd read ISO 9001 documentation end to end, and it was eye opening.
Total bullshit.
It ensured there was a paper trail documenting the total bullshit, of course, but it nevertheless was total bullshit that said a lot about describing what was done, but nothing about ensuring it actually worked as it should.
This same place had locked doors to the interior stairwell so consultants like me could not even get into areas we were not assigned to because of work done for clients like the police, but had confidential documents about police infrastructure sitting unprotected on the machine I was assigned.
To me that was a good indication they ran everything including security how they handled quality management: it was just a box ticking exercise. Document things and track deviations rather than care about actually getting things right.
I recently read this about it:
https://essenceofbuddhism.wordpress.com/2016/04/19/what-the-...
You need to focus on the real problem at hand, and devise/adapt a correct solution in context. Systems and frameworks provide helpful tools and templates, but they all require contextual adaptation.
FWIW this is what I like about the foundations of Agile for project management. The manifesto points all direct you away from your tools and processes and towards the actual problem. eg "People over process," "working code over documentation," etc. Basically the people on the team should focus on working software, communicating with the customer, and adapting to change. Their processes, documentation, contracts, and plans should all be aligned to that solution, not the other way around.
And out of that... we got millions or scrum certificate weilding alcolytes who will tell you that if your project failed, it's because you didn't do their system religiously enough. God certainly has a sense of irony.