3 ms·
Surprisingly reasonable & well written. I wonder who wrote this, sounds like a person with extensive experience with contractors that sell themselves as 'agile
by montenegrohugo 8y ago
Surprisingly reasonable & well written.
I wonder who wrote this, sounds like a person with extensive experience with contractors that sell themselves as 'agile' but really have no idea what the term even means.
EDIT: These actually seem like great questions to ask at an interview to a potential employer
- pjc50 8y agoThe actual author has been scrubbed, presumably as part of the declassification, but the organisation responsible is https://innovation.defense.gov/ https://innovation.defense.gov/ I see Neil deGrasse Tyson and Eric Schmidt on there, but I very much doubt they've seen this document.
- AndrewKemendo 8y agoProbably Josh Marcuse or someone on his team. He's the Civilian Permanent Chair of the DIB for the DoD.
- ddebernardy 8y agoI wish it was only contractors. I've seen my fair share of startups over the years that were nothing but. And heck, I'm no agile specialist by any stretch, and I'm often first to point out how god awful it's being implemented in practice. But the one thing I grokked about it is that if you're not talking to end-users each sprint you're not agile plain and simple. (And agreed these are good questions for would-be employers. But if you do ask them and refuse to work in a non-agile shop, you'll find precious little outfits to work for.)
- nikk1 8y agoI'm working for a large defense contractor. We are adopting an "agile framework" (this is being pushed on us by upper management) and I've been going nuts over how nobody around here seems to understand the true agile philosophy. I'm really glad the DoD recognizes how to spot good software development.
- williamdclt 8y agoI was telling myself the same thing, even if I'm not expecting a potential employer to actually do all of that, their reactions and answers probably will say a lot about the culture of the company