Hacker News new | ask | show | jobs
by pylua 698 days ago
This document has no teeth. It is more simple than this … does it have fixed scope and fixed timeline ? If so it’s not agile.
2 comments

It is part of an effort that will have impact. Remember that the US federal government is the largest IT spender in the world.

This is part of their efforts to move agencies internally I using a carrot first. Now that the GAO officially released an agile audit guide, the stick is in place.

GAO Agile Assessment Guide

https://www.gao.gov/products/gao-24-105506

Note that in the public sector, appropriation committees have the power, and see how they are targeting states here.

https://guides.18f.gov/derisking/state-field-guide/budgeting...

TOGAF, ITIL and the other crusty frameworks all had to take steps to modify their long held dogma over the past few years.

I would give it another 5 or 10 years or so before federal funding to even states depends on compliance.

Remember that the military moved away from Taylorism to mission command a long time ago.

This is moving IT the same way.

If you have or aspire to have government contracts it is probably a good idea to pay attention.

Note how that 18f page links to the above document and goes farther, saying that if there is a single individual who can insist on a Gannt chart , you aren't 'agile'

There is two centuries of experience in the military setting, with only about 70 in the biz world, the feds are quite clear that they won't wait for IT.

They're right though- teeth means enforcement. These DOD recommendations/guidelines aren't worth the paper they're printed on if they aren't don't make into the contracts.
The document vibe to me is like it is written by some junior engineers who have just read a blog post about the Netflix stack and think they know it all now.