All design methodologies have their drawbacks, but I think the most hellish design method is "Agilefall", where you use the trappings of Agile/Scrum/Kanban deve

All design methodologies have their drawbacks, but I think the most hellish design method is "Agilefall", where you use the trappings of Agile/Scrum/Kanban development (Jira, standups, tickets, etc.) to implement a series of hardcore requirements the clients thought up before anyone started building anything. I worked at a software company that built extremely sensitive survey applications (iOS, Android, and web-based). A significant part of my job entailed breaking down a literal design specification document into Jira tickets, which were then worked on by a rotating staff of programmers. The rotating programmers were assigned to 10-30 apps at one time and often had to make enormous customizations to the base product. The base product was formed out of 15 separate sub-products whose teams did not correspond with each other. The clients were allowed to make broad changes to the entire system by (a) changing the design document (b) emailing furious demands to the sales team/my manager (c) adding requirements to the master contract and not telling us. There was no traceability established between the contract/design doc/tickets, and I was not allowed to standardize any of those documents. There was no standardized format for writing the Jira tickets, so every person on my team made up their own method. The design document was missing about 40% of the context necessary to deliver a working app, so I added that context into the Jira tickets, but the clients weren't allowed to review the Jira tickets. I spent 20% of my time in "Scrum" meetings including sprint planning, sprint reflection, and hour-long standups. My company was worth hundreds of millions of dollars. I made a fat chunk of change in a year and a half, put a down payment on a house, and quit.