News for hackers. Stuff that matters.
Re:Plan the Sprint, Not the Project by Jtsummers on Thursday August 20, 2020 @02:21PM (#24226580)
Agile isn't, strictly, about software though it certainly is the predominant application. So first, let's separate two things:

- building

- designing

Some parts of agile do apply to building. See Lean Manufacturing, parts of it are responses to maintain quality (Andons used to stop production) and parts are to change over the manufacturing floor to build something else (same plant can make many kinds of cars without a fixed production line for each, letting them meet demand).

Other parts of agile, though, are aimed more at the design portion. Sprints, for instance, are meant to give you short iterations that let you frequently evaluate both your process and your product's success/failure.

You can apply agile concepts to developing almost any kind of thing. Actual rocket scientists create simulations, scale models, full-scale models, prototypes and other things on their way to the final system. So they're already applying the same iterative approach that most agile proponents endorse. The question is, is the iteration deliberate or accidental? Or do they try to deny the iterations even exist? Once they get to building the rocket, that might be less agile depending on circumstances (is it the first one they've built? are they setting up a production line? is it a one off?).

Re:Plan the Sprint, Not the Project by bluGill on Thursday August 20, 2020 @02:59PM (#24227222)
Note that when building cars flexibility is a trade off. You can switch car type, but the jigs for the car you are not currently making is still a cost, separate lines at near full capacity are a better use of resources. Only if you can forcast demand years in advance to build the factory to the right size. This is a hard problem.

Note that flexible factories have other limits. Honda can't make a large truck in their factory as there isn't room. I don't know if Honda regrets this cost or not.

Re:Plan the Sprint, Not the Project by Jtsummers on Thursday August 20, 2020 @03:17PM (#24227479)
I always come back to this:

> Fisher's Fundamental Theorem: The better adapted a system is to a particular environment, the less adaptable it is to new environments. -- Gerald Weinberg,"The Psychology of Computer Programming"

There are always trade offs. The more flexible you make a system, the less efficient it is (most likely) in achieving its (now increased) goals. But the more efficient you make it, the harder it is to adapt it to fit additional or changed goals. Which trade offs you accept depend on your objectives, and sometimes your ability to spin up a whole new factory.

Re:Plan the Sprint, Not the Project by dllthomas on Thursday August 20, 2020 @07:09PM (#24230079)
We can probably force this to be true, to some degree, by defining "adapted" differentially... but otherwise this smells more like a "possibility frontier" situation than a strict spectrum.
Re:Plan the Sprint, Not the Project by jrochkind1 on Thursday August 20, 2020 @03:39PM (#24227787)
I think it's useful to separate building and designing like that. What it makes me think of is: One thing fairly unusual (if not unique) about software is that the designing and the building generally happen "simultaneously", or in tandem, or in very tight iterations. We design software as we build it, and we build it as we design it.

At least often/commonly. If we don't always do that with software, I think we always do it at least to some extent (in an unusual way compared to physical things), and software is (often if not always suitable to designing and building.

I think "agile" as we know it (which is really short for "agile software development", that's what the agile manifesto hasin it's title!) is particular to something you are (or can profitably) design as you build.

While there are analagous things in physical products, and there is (or profitably can be) some element of design/build cycle in physical products, I think rarely to the extent it can and does happen when making software. Rockets are probably at the far end of separating design and build.

But the tldr version is probably just: The Agile Manifesto's full name is literally "Manifesto for Agile Software Development". While some of the things may happen to be useful or applicable in other fields of endeavor, others may not be. Saying that something from the Manifesto for Agile Software Development and ensuing methodology doesn't apply to a rocket is not a relevant critique of the methodology as applied to software, as intended.

Re:Plan the Sprint, Not the Project by Jtsummers on Thursday August 20, 2020 @03:55PM (#24228025)
> One thing fairly unusual (if not unique) about software is that the designing and the building generally happen "simultaneously", or in tandem, or in very tight iterations. We design software as we build it, and we build it as we design it.

I actually had something about that but cut it for some reason.

I'd like to point out that while the manifesto is about software, a lot of the ideas (beyond the manifesto itself and influencing the manifesto) come from other disciplines. Mary and Tom Poppendieck, for example, are major proponents of Lean Software Development, whose ideas are a translation from the world of physical manufacturing. Many of the DevOps ideas (not necessarily how it's played out) come from Eli Goldratt and his Theory of Constraints.

An interesting thing about both Lean and ToC is that neither is terribly prescriptive. They're actually generalized concepts that can apply to almost any kind of system and (mostly) lack prescriptive text saying, "Thou shalt do...". Compare that to much of the Big-A Agile movement which is inflexible, ironically, and often very prescriptive. Perhaps not down to the specific tool that should be used, but often to the specific methods that should be used (Scrum: Thou shalt have 1-4 weeks Sprints; Thou shalt have time boxed meetings of this nature; SAFe: Thou shalt have a massive meeting every 6 months in the format we describe in this chapter).

Ok, that's a bit unfair to Scrum, it's actually more flexible than that. But I'll happily burn my books on SAFe (picked up for a previous job).

Many of the other ideas for Agile are born out of Systems Engineering which had already dealt with Waterfall. You had the V model (an improvement, but still many of the flaws if taken too literally, over Waterfall) which makes V&V run concurrent to design and development and encourages feedback loops. In many ways this is akin to TDD. Incremental and iterative development processes, which are fundamentally no different from Scrum except Scrum pushes you to much shorter times and has a stricter structure. Evolutionary development which is really close to what many, if not most, agile proponents endorse (MVP, then add on features and modify the base as needed). None of that came from software (specifically), it came from developing physical and (in their parlance) cyber-physical systems.