News for hackers. Stuff that matters.
Re:US Air Force chief software officer quits by dragontamer on Friday September 03, 2021 @04:22PM (#28408933)
The full paragraph reads:

> The DoD is still using outdated water-agile-fall acquisition principles to procure services and talent instead of leveraging “Capacity of work” agile contracts to staff teams. Improving acquisition ensures teams have the ability to groom their backlog and move at the pace of relevance. Only Platform One, and teams like Kessel Run, are truly end-to-end agile, from what I have seen to-date.

I don't know what "water-agile-fall" is exactly, but he's probably talking about some terms in the Air Force. Maybe he means that the waterfall model still exists, and a bunch of people are trying (unsuccessfully) to convert to agile. But he's only seen Agile properly happen in a minority of projects.

Re:US Air Force chief software officer quits by crimsoncastle on Friday September 03, 2021 @08:45PM (#28411088)
Correct. Although there are some "doing agile" it may only be a relabeling of waterfall processes or insertion of agile processes into the current ops. Teams are all too willing to say they are following agile even when they aren't.
Re:US Air Force chief software officer quits by jrochkind1 on Friday September 03, 2021 @04:32PM (#28409044)
that is somewhat clarifying! Still trying to wrap my head around "to procure service and talent" with regard to agile/waterfall.
Re:US Air Force chief software officer quits by mpyne on Saturday September 04, 2021 @06:56PM (#28420125)
He's talking about how you contract for additional staff to help with developing digital products.

Typically the way government does this is by not contracting for staff at all, but instead contracting for a company to develop a software product that meets a long laundry list of requirements. Since 'agile' is in the DoD zeitgeist these contracts often throw in some agile buzzwords like "Story points" instead of "work breakdown structure", or split up the product into some kind of phased delivery scheme. Sometimes they'll throw in to do user-centered design.

But invariably these contracts lay out the same thing: develop a product that meets X requirements. This means you have to know the requirements. You can't instead hire smart people to help explore a problem space, do interviews and experiments to determine whether you've achieved product-market fit (or what we'd call mission-market fit), and only then to start fielding a digital product in increments.

This is considered a 'services contract' and these are frowned upon because they seem ripe for fraud ("you paid BigCo $40 million a year to do 'market research and product discovery'????? What did they discover? Why couldn't it have been $20M instead??").

TL;DR: The type of services you'd contract for are different for a modern digital product compared to a waterfall-style project. Even though DoD says we're doing agile, the reality is that the contracting system still pushes you hard to waterfall because no one seems to have the expertise to do 'agile acquisition'.