U.S. Department of Defense – Detecting Agile BS [pdf] (2018) • Hacker News Board

U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#1

Post by rareitem » Thu, Jul 25, 2024, 9:40 PM UTC

U.S. Department of Defense – Detecting Agile BS [pdf] (2018)
media.defense.gov

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#2

Post by [deleted] » Thu, Jul 25, 2024, 9:40 PM UTC

[deleted]

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#3

Post by bluefirebrand » Thu, Jul 25, 2024, 9:58 PM UTC

I love this document. I'm absolutely going to be sharing this around a bit at my company

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#4

Post by simondanerd » Thu, Jul 25, 2024, 10:01 PM UTC

Sharing this link to a buddy... He's a "full stack web developer" for the US Army and can't make an HTML page but sure can do "npm run start".

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#5

Post by pylua » Thu, Jul 25, 2024, 10:05 PM UTC

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.

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#6

Post by localfirst » Thu, Jul 25, 2024, 10:07 PM UTC

color me paranoid but clicking a pdf from defense.gov feels wrong but I want to read this so bad lol

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#7

Post by havkom » Thu, Jul 25, 2024, 10:07 PM UTC

First parts of the document are pure BS focusing on hype technologies rather than “Agile”. I mean, questions about ”Kubernetes or Docker Swarm?” etc.

The last section with flow chart is good though.

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#8

Post by polemic » Thu, Jul 25, 2024, 10:10 PM UTC

havkom wrote: post #7

First parts of the document are pure BS focusing on hype technologies rather than “Agile”. I mean, questions about ”Kubernetes or Docker Swarm?” etc. The last section with flow chart is good though.

They aren't "hype" technologies - but it does seem badly framed. If it were to say "the team uses version control, CI frameworks, agile tracking tools then they might be agile" it would make more sense. That would be especially useful if , say, much of their existing softare is delivered once a month via zip files on an ftp server.

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#9

Post by havkom » Thu, Jul 25, 2024, 10:11 PM UTC

pylua wrote: post #5

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.

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.

Re: U.S. Department of Defense – Detecting Agile BS [pdf] (2018)

#10

Post by doctor_eval » Thu, Jul 25, 2024, 10:12 PM UTC

While this document starts strong and has some good points, it strongly conflates “scrum” with “agile” and goes downhill pretty quickly.

> wrong answer: what’s a sprint cycle?

You don’t have to have sprints to be agile. What’s important are the four values.

The manifesto says, “Individuals and interactions over process and tools” but this document then goes on to talk a lot about specific processes and tools.

It’s a trap!