Re:US Air Force chief software officer quits
by tablespoon on Friday September 03, 2021 @06:39PM
(#28410233)
> Which is to say, the upstream and downstream didn't change how they do things at all, and somehow developers acting differently is supposed to convert everything to agile.
Sounds like my corner of the private sector.
Re:US Air Force chief software officer quits
by AnimalMuppet on Friday September 03, 2021 @04:58PM
(#28409346)
Stronger: Somehow developers acting differently without the inputs that agile processes require is supposed to convert everything to agile. And somehow it never does...
Re:US Air Force chief software officer quits
by panzagl on Friday September 03, 2021 @06:47PM
(#28410292)
In practice most contractors end up hiring a bunch of former users to act as stand-ins for the real operators. These former users then get to engage in continual pissing matches with the acquisition office over how things really get done. Hilarity ensues.
Re:US Air Force chief software officer quits
by Pokepokalypse on Saturday September 04, 2021 @02:24PM
(#28417694)
I know the solution!
Hire a scrum-master! that will fix it.
Which is to say, the upstream and downstream didn't change how they do things at all, and somehow developers acting differently is supposed to convert everything to agile.
Or to put it another way, this is what you get when you tell everyone they need to "do agile" without actually retraining people on what that means and update processes to enable it.
Source: experience with healthcare "agile" and "sprints"