5 ms·
Personally, I never liked agile. I like to get a description of a problem. Prototype. Take that to that customer and ask for feedback. Iterate. QA. QA. QA. Rele
by BirAdam 4y ago
Personally, I never liked agile. I like to get a description of a problem. Prototype. Take that to that customer and ask for feedback. Iterate. QA. QA. QA. Release. Thing is, much like governments, these models all fall short because people aren’t great. I think that if agile isn’t working for a team they should try another method, and if agile does work for a team that’s fantastic. People, imho, shouldn’t blindly follow a methodology in religious fashion. They should try different stuff until something works for them.
- criley2 4y agoThe one thing agile helped here is to take that process and make it fast. The problem with "Requirements, prototype, feedback, iterate, qa, qa, qa, release" is that most large shops turn that into a 3 year process. As in, a group sits in a room for 6 months and writes some insane "Requirements Doc". Then six months of prototyping against it before any customer has seen anything. Etc etc down the line until you're a programmer looking at a 3 year old requirements doc with a thousand questions that arise during implementation but the designers who wrote the doc left the company two years ago, etc etc Waterfall was to me inarguably worse than agile. At least with agile people try to do requirements, prototyping and iterating in a very short period of time, so the feedback loop with customers actually works, and you actually release something on a regular basis.
- deleted 4y ago[deleted]
- kwanbix 4y ago> Personally, I never liked agile. I like to get a description of a problem. Prototype. Take that to that customer and ask for feedback. Iterate. QA. QA. QA. Release. That is agile for me. What is agile for you then?
- websitescenes 4y agoI think maybe there is a conflation being made between Agile and Scrum.
- HelloNurse 4y agoAn almost deliberate confusion between the agility of making changes to software easy and the agility of running like hell because you are chased by deadlines.
- _ea1k 4y agoSince when was scrum about deadlines?
- HelloNurse 4y agoManagers are about deadlines, and I'm afraid Scrum is about managers.
- _ea1k 4y agoIts weird how far things have come from the original goals: https://en.wikipedia.org/wiki/Agile_software_development#The_Manifesto_for_Agile_Software_Development https://en.wikipedia.org/wiki/Agile_software_development#The... I'm seeing a lot of processes and tools over people and interaction in more recent iterations of Scrum implementations. Sprint commitments were originally the opposite of imposed deadlines.
- marcosdumay 4y agoWell, this is the process IBM consultants were selling around when Agile started to grow. Anyway, Agile has that one principle that is focusing on people, not process... You can make any process agile.
- robertlagrant 4y ago> I like to get a description of a problem. Prototype. Take that to that customer and ask for feedback. Iterate. QA. QA. QA. Release. Assuming you don't stop there and keep doing those things, I don't see why you don't like agile.
- gnfargbl 4y agoI think the parent is coming from a place where projects have a defined start point and a defined deliverable at the end. In that situation, they might be advocating for spiral development [1], which isn't really that different to agile. It's a bit more process-heavy maybe, but as always these things are what you make of them. [1] https://en.wikipedia.org/wiki/Spiral_model https://en.wikipedia.org/wiki/Spiral_model
- layer8 4y agoIf you look at the actual agile manifesto, I don’t think your view is in conflict with it: https://agilemanifesto.org/ https://agilemanifesto.org/