4 ms·
(in regards to the original post that started this) I could rant for hours about how so many misuse the term "Agile" and the misunderstanding the idea(s) behin
by mindcrime 10y ago
(in regards to the original post that started this)
I could rant for hours about how so many misuse the term "Agile" and the misunderstanding the idea(s) behind being agile. But I'm at a point where I almost don't care anymore. The use of "Agile" as though it describes a specific, prescriptive methodology is so ubiquitous that it's almost impossible to talk about the subject.
Let me just say this... go read the Agile Manifesto before issuing any criticism of "Agile" and repeat this 10 times - "Agile is NOT a methodology".
Scrum is a methodology. Crystal is a methodology. RUP is a methodology. XP is a methodology. OpenUP is a methodology. TSP is a methodology. One or more of those methodologies may be "agile", but "Agile" itself is NOT a methodology.
- feyn 10y ago(me = author) My bones ache from seeing Rational Unified Process mentioned, but of course you are correct. I would say I was "at the point where I almost (didn't) care" about 5 years ago. I then switched jobs and was made lead of a team I cared about, and decided I wasn't done with implementing Agile. There was a time, however, when I was downright apathetic. Companies had beaten me down too much, and I didn't have the energy to fight anymore, so I completely understand.
- mindcrime 10y agoInterestingly enough, I'm actually a fan of RUP, IF you instantiate it without requiring all the UML artifacts and what-not. One thing I like about RUP is that it emphasizes that you perform work in each area (requirements, design, implementation, etc.) in each iteration. To me, it emphasizes the "iterative" aspect of "iterative development" better than, say, (naive) Scrum. I also prefer the term "iteration" to "sprint" because the "sprint" analogy breaks down in that you can't actually SPRINT -> SPRINT -> SPRINT -> SPRINT forever and ever in reality. And to me, it just creates the wrong mindset. Admittedly it's a minor quibble though.
- feyn 10y agoI learned RUP before Agile, and didn't hate it. I only learned if you like one thing you necessarily have to hate something else later in life. Aspects of RUP make it into my interpretation of agile. For example, I teach my dev teams UML (sketching as defined in Fowler's book) for whiteboarding and the rare BDUF, which RUP exposed me to. Speaking of BDUF, I've saved many a feature by resorting to BDUF when communication broken down. I didn't and don't want to start a flame war, but needless to say once in an interview I was asked if I was a "Scrum Master" (after having about 15 years of agile experience). When I stopped laughing, I said, "No, no I am not." I don't think they got the joke, and no - I didn't get the job. I don't think "iteration" vs "sprint" is a minor quibble. I've seen the "wrong mindset" you speak of, as people take "sprints" far too literally. It's not a sprint, it's a jog. A long, long jog. You'll be stopping for water and stretching along the way. Sprinting is a good way to pull a muscle and have all your devs quit on your one day, leaving you with a big-old case of backlog rhabdomyolysis. I took that analogy way too far.
- mindcrime 10y agoI learned RUP before Agile, and didn't hate it. Same. I only learned if you like one thing you necessarily have to hate something else later in life. ROFLMFAO. Aspects of RUP make it into my interpretation of agile. Same here. For example, I teach my dev teams UML (sketching as defined in Fowler's book) for whiteboarding and the rare BDUF, which RUP exposed me to. Yep. My issue is, a lot of people see a dichotomy where you have "big design up front" or "no design at all". I like to talk about "sufficient design up front". I don't know if I coined the term or not, but that's my favored way of expressing that middle-ground, as I see it. backlog rhabdomyolysis I'm so going to steal that. :-)
- feyn 10y agoI shall in turn steal Sufficient Design Up Front (SDUF)
- meheleventyone 10y ago
- ktRolster 10y agoNote that Agile values "people over process," so having too heavy a focus on process violates the Agile manifesto by itself.
- mindcrime 10y agoExactly. It's almost ironic that people have chosen to conflate "agile" with a highly prescriptive, heavyweight process. :-(
- bluGill 10y agoYou conclusion is wrong. Agile finds value in process, as well. Read the last line until this sinks in: That is, while there is value in the items on the right, we value the items on the left more. There is a lot of value in the right process, the process however needs to be a servant to the needs of the people. You can be agile with long complex processes so long as you pay attention to how the processes affect the people and ensure that every time a process is getting in the way of someone it is a good thing. I think we would all agree that process needs to stop the "cowboy coder" who otherwise would check in code with many syntax errors just before leaving for a long vacation. This example is nearly a straw-man it is so trivial - but if anyone doesn't have personal processes to prevent it the team will need to create a process of some sort. This could be a simple don't do that again talk, a HR process to fire the guy, a automatic backout process, a formal checkout for pushing, or whatever - the choice is up to your team, and depends on team factors like if this is a one time mistake or a repeated offense. Going to the other extreme, medical software that could kill should have long complex processes. Agile is perfectly fine with this. Agile is taking issue with some [big companies] that have created such long cumbersome processes in ages past that no longer serve the needs. Sometimes they created a complex process because of a one time mistake that is unlikely to happen again. Or maybe the process made sense in light of the tax laws that were changed in 1986. Some processes actually are required and useful, but because of all the cumbersome ones they are ignored until it is too late.
- feyn 10y agoWell said.
- koverstreet 10y agoI notice you're not having daily standup meetings, are you sure your development is Agile compliant?
- philosopheer 10y ago| "Agile is NOT a methodology". in the Ask HN that started this, he did put methodology in literalized fingerquotes, so he didn't actually make the egregious error you decry. | 5) Agile "methodology" when used as anything but a tool and his summary point still applies right on target because the Agile "manifesto" does not solve what he identifies as the problem: I think overall we seem to be over-complicating software development. We look to architecture and process for flexibility when in reality its acting as a crutch for lack of communication and proper analysis of how we should be architecting the actual software. dear Agile Manifesto, The best architectures, requirements, and designs emerge from self-organizing teams? so therefore self-organizing teams always produce the best architectures... anybody see an error in reasoning? Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Suuure they do, and that's why we see Agile processes adopted by winning NFL teams, or in the ERs at hospitals, and... Look, there is a Zen Buddhist ideal for living your life in harmony, but it's a goal, not an emergent property of self organized teams. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. So, do not look up information in a man page, instead ask me and I will read it to you... that metric-imperial problem that lost that space probe, why another scrum or two would have identified that right away! I could keep going, but this letter is too long already. Yes, software does offer some advantages over other types of team problem solving (due to the possibility of virtualizing or dummying any of the parts) but because of that flexibility it becomes even more important to nail down as much key design infrastructure as possible, and the Agile Manifesto does not read like a manual for nailing anything down. (And software alone offers the possibility to rip up things that are nailed down, so we don't need to fear nailing down.) Love, philosopheer
- mindcrime 10y agoSure, I wasn't actually decrying any error in the original post. It was more that the post alluded to something that's a hot-button issue, just enough to trigger a rant from me. I agree with a lot of what the author of the original post had to say.
- feyn 10y agoFWIW, I don't take the manifesto or the principles behind it literally for many of the same reasons you hint at. My attitude when looking strictly at agile doctrine is a mix of skepticism (especially after having learned and practiced agile for around 15 years now) and thinking, "Hummm...they might be onto something..." I don't often criticize the written word of how people try to describe agile, but instead try to understand "what were they trying to say?" A point of illumination for me as to which parts of agile I was most interested in developing a deeper practical knowledge of, happened after I watched a few documentaries on Skunkworks, and how that group operated. Robert Kelly's 14 Rules and Practices does (to me) have a lot of conceptual similarities with the manifesto, especially when you see how they were practiced on some of the most difficult technical challenges humans have ever faced: http://lockheedmartin.com/us/aeronautics/skunkworks/14rules.html http://lockheedmartin.com/us/aeronautics/skunkworks/14rules.... I think that if someone were to pin me down and say "Tell me the doctrine you follow!!!!" and I was forced at gunpoint to give a simple single answer I would point to Kelly's 14 Rules over the manifesto. A deeply unfortunate fact of the agile's history is that the C3 system wasn't really very successful by just about any dimension: https://en.wikipedia.org/wiki/Chrysler_Comprehensive_Compensation_System https://en.wikipedia.org/wiki/Chrysler_Comprehensive_Compens... I've been told by many of Agile Manifesto acolytes that the C3 project's less-than-stellar results don't matter, but I personally think it does. At a minimum, at least you can point to Kelly's Skunkworks team, and see how they shaped modern history with their inventions and ability to deliver improbable solutions on an impossible schedule. In summary, where Kelly's 14 and the Agile Manifesto & Principles conceptually overlap, I believe there is much worth learning.