by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
FCW : July 15, 2016
Government projects are not agile enough • Large projects are always a risk but less so with agile. Government projects always seem large and com- plex, and that dramatically reduces the likelihood of success, according to the Standish Group’s Chaos report. The report cites success rates of 5 percent to 12 percent for “grand” and “large” projects. But it also states that the likelihood of success increases four or five times when one uses an agile approach. • Digital is a necessity, not a “nice to have” technology. When he described the future of business innovation, Marc Andreessen is quot- ed as saying, “Software is eating the world.” But that is not true just of business; government is also look- ing to software to deliver improved services, connect with citizens and make better decisions. And digital is synonymous with agile. In fact, the U.K. government insists that all digital programs follow an 18-point service standard. Point 4 describes the need for projects to “build the service using If a robot delivered towels to their rooms, would hotel guests freak out? Would they try to speak to the robot? How much personality is too much in a machine? Those were the questions facing designers and engineers at Savioke as they put the finishing touches on Relay, a robot helper engineered for hotel delivery service. The company identified the problems, created a prototype with a touch screen and tested it with real people — and did it all in just five days. The idea that tough problems can best be solved by devoting a five-day sprint to nothing but finding their solutions is at the crux of “Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days” by Jake Knapp, who developed GV’s sprint process, along with John Zeratsky and Braden Kowitz, who also work at GV. It’s a do-it-yourself guide to conducting sprints anywhere. And although the approach might seem better suited for lean startups than federal agencies bogged down with red tape and bureaucratic procedures, the General Services Administration is already doing similar things with customer journey interviews and its own startup, 18F. Getting answers about the customer experience is a top priority for agencies, and the book’s rapid-fire, collaborative process shines in that area. “A sprint allows you to learn from the surface of a finished product — that’s where your product or service meets customers,” Knapp said. The book explains how to identify the most pressing problems first, sketch competing solutions, turn the ideas into a testable hypothesis, create a prototype and test it with actual people. To illustrate his points, Knapp uses examples of various startups backed by GV. Projects include figuring out a strategy for introducing the messaging service Slack to non-technology- minded customers and helping a health firm deal with the complexity of getting cancer patients into clinical trials. Comparing the sprint to “a perfectly orchestrated heist” like the one in the movie “Ocean’s Eleven,” Knapp said the organization’s “decider” must be in the room. That person could be the CIO or a project manager as long as she or he has the authority to make decisions. More broadly, the book makes a strong case for the value of a sprint rather than a marathon. — Bianca Spinosa Sprinting to solutions SHUTTERSTOCK/1105MEDIA 0715fcw_030-032.indd 31 6/28/16 9:34 AM
June 30, 2016
July 30, 2016