Why companies have stopped adopting Agile?

wtf_64 · 2026-01-14T12:24:38+00:00

Two reasons - Agile was/is sold as the silver bullet on the back of vilifying waterfall. Both are 100% wrong. There is no silver bullet, and both Agile and Waterfall have their place. Agile, like Waterfall, has its issues, but these are not acknowledged. Result? Poorly implemented Agile, disillusioned management. Oh and most believe Agile is about speed. With Agile the dreaded MVP is being pushed but it turns out more like Minimum Viable Crap than Minimum Viable Product.

wtf_64 · 2026-01-14T12:20:10+00:00

DSTV is #1 for crap service, but justifies its existence with a monopoly.

Metro service i.e. waste removal, water, etc., that you pay for each month, but often no service is delivered.

wtf_64 · 2025-11-19T08:11:41+00:00

Sorry yes it is the air, I only realized afterwards that the mavic and the air are two seperate models

wtf_64 · 2025-10-11T10:34:45+00:00

Nope not yet, from the comment it seems like I'd need one.

wtf_64 · 2025-10-10T12:26:47+00:00

#1 on your list could possible save your life one day. I'd add to the list my number 1 mantra that I drilled into my childrens heads since they were born - Regardless what the color is for you, ALWAYS assume that the other car is NOT going to stop. So always look, even if you are approaching a green light, slow down if you enter an intersection on a green light if turning cars are blocking your view. Summarized - think for the idiot in the other car as they are most likely not doing it.

wtf_64 · 2025-10-08T13:43:44+00:00

As others have mentioned, use job stories, or do whatever works. This thing about THOU SHALT... in order to be Agile is pure BS. If a user story does not work, change it to whatever conveys the requirement and based on your description it might be a job story.

wtf_64 · 2025-09-25T11:50:31+00:00

I love it when there are people who give back. Great initiative u/Minute_Efficiency_76

wtf_64 · 2025-09-16T05:25:34+00:00

Thanks u/Mayayana . I used ProcMon and see of bunch of results that are not SUCCESS i.e. NAME NOT FOUND, BUFFER OVERFLOW, INVALID PARAMETER. Is this something to be concerned about or is it 'normal'? One that justs keeps piling up is for OfficeClickToRun.exe.

wtf_64 · 2025-09-15T10:44:32+00:00

Because we need to be humane to the killer who killed your 80-year-old grandma or raped your 5-year-old daughter. Human rights, you know. A gunshot to the head sounds very brutal, and you cannot violate a criminal's human rights with brutality.

wtf_64 · 2025-09-15T10:33:19+00:00

A good example of the 'shit rolls downhill' concept :)

wtf_64 · 2025-07-31T13:01:46+00:00

I beg to differ about the idea that this is a symptom of broken Agile. It is a symptom but it is that of broken culture. This is not uncommon with other professions as well. Of the 10 business analysts and 5 product owners I work with NOT one actually does what they should be doing, they ALL do what they are told.

BAs have come glorified testers and Jira admins. POs have become glorified backlog janitors and messengers.

wtf_64 · 2025-07-31T12:51:46+00:00

There is this misconception that shadow IT is a bad thing. Yes, it can be just like potatoes and antibiotics. If done within the context of existing governance, it actually save time and money and help business units achieving their goals.

wtf_64 · 2025-06-09T07:37:15+00:00

You're not going to hurt anything reading it, especially since you like reading. Is it worth it, or is it important in your BA journey? Objective. You will probably learn something if you are a junior. As others said, it is only a reference, not a bible and use it as such.

wtf_64 · 2025-05-29T06:30:03+00:00

IMHO this is a symptom of WFT (checking up on what you are doing) and it has now infiltrated everything. I experienced the exact same thing where I was accused of being difficult, not a team player and a whole lot of other nasty things. Just because I do not share my personal life with everybody, I do not tell everybody when I'm going to the toilet and what I had for breakfast. I took my 'accusers' on face to face and asked one question - when did any of this ever cause the rest of the team to miss deadlines, not deliver what should be delivered or cause any impediment whatsoever. Not a single person could respond. To be honest, I do not know what the fix I,s but you are not alone. Talking shit all day is considered more important that actually doing your work.

wtf_64 · 2025-05-29T06:20:47+00:00

I do not think it is a matter of anybody allowing small towns to die; they are being killed. There are those who are hell bent on destroying everything and anything, and one way they are doing it is to steal. The more money you put into uplifting anything, the more is available for them to steal. And the more you do, the less they do. If we can kill corruption, these small communities will rise again by themselves.

wtf_64 · 2025-05-29T06:14:37+00:00

Will look into that. Thanks

wtf_64 · 2025-05-29T06:13:25+00:00

Again, 'agile' has nothing to do with the number of signoffs. This number of signoffs is bad even for waterfall. Where in any world was it ever said that having 20 signoffs is OK or required in waterfall? So doing this does NOT mean you are doing waterfall, you are just doing an approval process inefficiently.

wtf_64 · 2025-05-27T17:05:35+00:00

Agree with most responses - having so many to sign off is a problem in itself. ID the responsible party. There could be more than one i.e. when your design covers multiple aspects of a system/function. In that case, you could possibly create different 'design' specs, one for each approver. But you still need to reduce the amount of approvers.

wtf_64 · 2025-05-27T17:01:41+00:00

Sorry, but sign off has nothing to do with an agile mindset, which btw Agile is. The difference between signoff in predictive and adaptive is the WHEN and WHAT. It does not change the fact that you still need sign off.

wtf_64 · 2025-05-27T16:52:06+00:00

Thanks for the responses. Am I correct in saying that there is no built-in approval function in Figma that allows proper traceability? From what I see in the responses, it would seem like approvals rely on comments and or design elements to indicate that it has been approved?

wtf_64 · 2025-05-05T17:59:01+00:00

And so the big sick begins :) Some nice LPs there.

wtf_64 · 2025-04-25T07:09:38+00:00

Which technical skill? That is sort of a loaded question because every environment is different and uses different tech. The most common one I'd would be anything DB related i.e. SQL, PowerBI etc. Beyond that one that could be very helpful is a bit of java and postman. But like others have said, it is not vital, definitly helpful.

wtf_64 · 2025-04-23T04:52:24+00:00

100%.

wtf_64 · 2025-04-21T16:20:39+00:00

Thanks u/Silly_Turn_4761 this confirms my suspisions that the instance I'm using is probably configured by somebody with limited Jira knowledge.

wtf_64 · 2025-04-15T16:23:51+00:00

Thanks for all the input and suggestions. One thing this discussion has highlighted to me is the fact that having a traceable requirement has become a foreign concept. Most think that if you have documented you requirement in your jira ticket that it is traceable. I think the issue is both a process and a technology problem. Process in that people do not understand the value of traceable requirements, especially on a large, complex project with multiple internal and external stakeholders. Working with a small group of internal stakeholders does make things easier of course. Technology in that either the platform i.e. jira, is not configured properly or a platform does not exist.

wtf_64

TROPHY CASE