'agile' can mean anything from a slightly reductive but generally useful process to a mind numbing waste of time where no one is really allowed to do anything a

'agile' can mean anything from a slightly reductive but generally useful process to a mind numbing waste of time where no one is really allowed to do anything at all except talk about the work they're ostensibly supposed to be doing. if hiring companies were more clear, we could steer well clear of the latter. but they all say 'oh, yeah, we just have a lightweight agile process, not really a big deal, we're trying to do it right, not like those other terrible people'. everyone whose been in the industry knows how to deal with the former. look, if you need daily status from me that i'm not just going to volunteer anyways, fine, its not a huge overhead. if you me to track my work with tickets, not gonna kill me. if you want me to meet every two weeks to make some plans, i can do that. thats not what people have a problem with. not being able to actually make plans because we're supposed to come up with our own sprint goals is. spending 1 week out of every two 'planning' is. aurguing about the proper number of story points for a given task is. incessantly arguing about how we can cut up the work so it it nicely fits into 3-4 stories per sprint or whatever management wants is. at some point the management narrative completely overwhelms the actual work at hand. omg i forgot some of the even bigger ones. expecting me to squeeze in all the other parts of my job like mentoring new hires or meeting with product or responding to issues in prod without messing up your sprint schedule. or undermining my ability to make any plans longer than a sprint because that contradicts your desire to tell simple stories and interchange workers.