46 ms·
How a two-day sprint moved an agency twenty years forward
- Beltiras 11y agoThat's somewhat of a plum project thou. I'm amazed that stuff like this is still printed out for reference [shudder].
- Domenic_S 11y agoURL typos are forever: how-a-two-day-spring
- mojuba 11y agoI first read the title as "two day sprintf". Need a little rest definitely...
- cantstop 11y agoOuch.
- Splines 11y agoYou could have the same title as a lessons-learned post about the post-mortem into discovering why the time server for an org was 20 years fast, diving into the machine to discover to their horror that some intern modified the time service to think about years, seasons, and months in a very human perspective. :p
- irl_zebra 11y agoThis is cool. It looks like the end result took the pdf chapters and made them searchable and in html form, which is a big improvement. Is there more to it than that that I'm missing?
- dublinben 11y agoThe end result isn't the end at all, but just the beginning of a more comprehensive system. This was just a proof-of-concept to show that something like this was possible.
- DannyBee 11y agoSo, that part has been known for years, and in fact, IMHO, part of the problem (with no offense meant) has been that many orgs provide proof of concepts to agencies or as part of sprints, etc, but in the end, the agencies really want someone who helps them maintain it forever. They want someone there to hold their hand and help make it work, forever. Not someone who shows them what the future looks like, does a little work, and then says "welp, gotta run, have fun building it!". Because then the agencies go back to their multi-million dollar consulting contracts, and end up with what they got in the first place: Someone selling them 20+ year old technology at a high price. (Sorry, i spent way too long in DC watching this kind of thing happen repeatedly)
- wslack 11y ago> They want someone there to hold their hand and help make it work, forever. If "it" is part of the core work of the agency, shouldn't that agency learn "how to fish" and develop that capability?
- rndmize 11y agoNot on the technical side. But I would consider that to be almost secondary - I think the important part is demonstrating that you can do this over a span of days and have real, serious improvement; and that the outsiders (18F/GSA) work to build something with the interested organization rather than for. By comparison, I'd imagine the standard gov process is something more like: * decide something needs improvement * create spec as far as what they want (weeks) * find contractor to implement that meets all rules/reqs (weeks) * pass specs to contractor, contractor builds product (weeks) * get finished product that doesn't work very well because spec was created in a vacuum and contractor didn't discuss issues unless they were game-breaking I feel like the emphasis here is more on process improvement rather than the end result.
- Animats 11y agoSome of the PDFs were based on Microsoft Word documents, so those could be easily processed. Some of them apparently had to be OCRd. Of course, now they have two versions to be kept in sync. But that was a "non-goal", so it's not their problem.
- kzhahou 11y agoDoes anyone see value in the huge emphasis on the "sprint" term? Advocates promote the word as a new way of working, but I see it as just adding confusion for the audience it's trying to reach. That is, if I'm a person entrenched in government and want to learn about this new way people are working, and I see the word SPRINT everywhere, I might assume it's some complex new idea. But it's not -- it's just a time period with goals. Those have existed forever. The real win in this short project came from having a cross-functional team in the room, in a working session with a clear short-term goal. So just say that.
- sp332 11y agoWhy would you say that whole sentence when you can just say "sprint"?
- deleted 11y ago[deleted]
- BWStearns 11y ago"Project", "period", "effort", and other words are less techie/jargon sounding and communicate the idea.
- sp332 11y agoI think they lose a lot of the meaning. And it's not like the government has any aversion to jargon! If we called it a "cyber-sprint" they'd eat it right up.
- BWStearns 11y agoAgreed, but this wasn't really about Agile methodology as much as the generic notion of fast iteration, which can certainly exist outside a specific agile regimen. From my experience, if your government audience is not already familiar with a piece of jargon, then introducing it risks 1) distracting from what you're actually trying to communicate, 2) giving them a false sense of understanding that will later be unintentionally used as a bludgeon against you or others in some planning meeting (a slightly caricaturish example: "No! Sprints are two days, why are you doing two week sprints!?").
- _kst_ 11y ago"The handbook consists of four five-inch-thick binders containing printed and photocopied pages. These binders are replicated and distributed across numerous regional and local offices. The handbook also exists as online PDFs, where each chapter or subsection is published as its own PDF. With these two options, investigators don’t have an easy way to quickly access and search for much-needed information that helps them complete investigations, particularly when they’re working out in the field." If I were working in that environment, I'd concatenate the multiple PDFs into one so I could search the entire set from any PDF reader. It's probably not as convenient as a web interface with a more sophisticated search facility, but it solves part of the problem fairly quickly. To concatenate multiple PDFs: gs -q -sPAPERSIZE=letter -dNOPAUSE -dBATCH - \ sDEVICE=pdfwrite -sOutputFile=ALL.pdf *.pdf Adjust the paper size and the order of the input files to taste. ("gs" is the Ghostscript command.)
- Splines 11y agoLonger term the team should track down where those PDFs are coming from. "Source --> PDF --> docx --> HTML --> json" is just nuts.
- dublinben 11y ago>Coming into the sprint, we understood that one of the major constraints is that the handbook is created and maintained using Microsoft Word. It's likely that the original source for the PDF/paper copies was lost. This necessitated the process of using OCR to get it into Word. Obviously maintaining such a large and important piece of documentation in Word is wrong, but that's apparently how it's being done.
- mungoman2 11y agoWhat are the options? It should be something that any clerk can handle and that doesn't become obsolete.
- vampirechicken 11y ago
- jbob2000 11y ago"Over these two days we demonstrated that with the right support and the right people in the room..." That's the solution, full stop. The right support and the right people. A "sprint" is just a mechanism, it's useless without the right people. So maybe that's the problem the government has? It's not the process, it's the people!
- dangerlibrary 11y agoWhat? Everyone in this room works for the government. 18F is a government project - an arm of the General Services Administration (GSA).
- bdavisx 11y agoYes, but they were from the 18f team, not exactly representative of the typical government worker.
- dangerlibrary 11y agoHow would you describe the typical government worker? What characteristics would you ascribe as 'typical' among the nearly 2,800,000 federal government employees? What do think of the engineers at NASA? The biologists and mathematicians working on the human genome project? What character traits do you think are shared by Park Rangers fighting fires and educating people about the value of wilderness in Yosemite, and FBI Agents working undercover to investigate organized crime? I'm genuinely curious.
- bdavisx 11y agoI should probably have been more descriptive and said "typical US Federal government IT worker". And I would describe a typical USFG IT worker as someone who's OK with lots of process (because otherwise they would likely have a different job). Certainly not all of them, but many (I would venture to say most). And I speak with some experience here. In the early 90's I taught a class about Microsoft Solutions Framework to a group of government IT people, and they were less than thrilled to have to learn a new way of doing things. MSF is a slightly agile process, more so than many others at the time, nothing like XP or even Scrum though. They had been using a waterfall process for a long time and were just fine with it. While one class doesn't automatically mean that everyone in government IT is that way, from my experience in consulting with several government agencies and other large companies, there are a lot of people who don't want to change. I think that many people who have never had to work in that environment don't realize how it is, certainly nothing like a startup - and I've also worked at a startup in the past as well.
- iamleppert 11y agoUmm, they took a bunch of PDFs and combined them together in two days?
- bglazer 11y agoThat's a super dismissive point of view. Here's another: Working with a government office with zero technical expertise they setup elastic search and converted hundreds of pages of Word documents into a searchable, well designed form and saved government workers hundreds of man-hours of fruitless searching. This process, in and of itself, was useful to show the agency how technical change can be executed quickly and successfully.
- djcapelis 11y agoYou're correct. That is a much more buzzwordy way to say they combined a bunch of PDFs in two days. The real point both of you are touching on is the surprising part of this story has nothing to do with the technology. It's perfectly reasonable to have accomplished a prototype like this in two days. The big thing here is in how they overcame the entirely non-technical obstacles to do it. I think there's probably two main things they did right: * They selected an achievable project with immediate high impact on the organization's day to day work. * They had the reputation, credibility and positioning required to make sure that their project didn't get bogged down by procedure or requirements imposed by external forces. As it turns out, these two things are some of the most important ingredients for affecting change with software and are relevant to nearly all teams. Many teams only get one of the two. Sometimes you get none.
- revelation 11y agoHow are people that work "often literally (sic) in the field", presumably without stable internet access, be best served with a web app running ElasticSearch? This is the kind of solution you get when you go into a problem planning to do some web app thing. It leads to an implementation that includes people slapping on a "Word -> HTML" conversion with not a thought given to the massive technical debt and complexity you are incurring there. (Presumably, these PDFs come from somewhere?)