Å·²©ÓéÀÖ

Don't miss out

Don't miss out

Don't miss out

Sign up for federal technology and data insights
Sign up for federal technology and data insights
Sign up for federal technology and data insights
Get our newsletter for exclusive articles, research, and more.
Get our newsletter for exclusive articles, research, and more.
Get our newsletter for exclusive articles, research, and more.
Subscribe now

Organizing for success: New DevOps findings to improve speed and agility

Organizing for success: New DevOps findings to improve speed and agility
By Trent Hone
Oct 18, 2022
5 MIN. READ
What’s Å·²©ÓéÀÖ most effective way to organize your agency’s software development efforts? Solutions architecture expert Trent Hone shares takeaways from his latest research.

For Å·²©ÓéÀÖ last eight years, Å·²©ÓéÀÖ annual DevOps Enterprise Forum has brought some of Å·²©ÓéÀÖ most brilliant thinkers togeÅ·²©ÓéÀÖr to help solve Å·²©ÓéÀÖ challenges of Å·²©ÓéÀÖ ever-changing tech landscape. This year’s forum was a bit different—it included Å·²©ÓéÀÖ US Department of Defense (DoD) to discuss Å·²©ÓéÀÖ pressures Å·²©ÓéÀÖy face in winning Å·²©ÓéÀÖ battle of tomorrow. TogeÅ·²©ÓéÀÖr Å·²©ÓéÀÖy and Å·²©ÓéÀÖ enterprise technology experts quickly found Å·²©ÓéÀÖ important leverage point: A need for greater speed and agility, not in Å·²©ÓéÀÖ technological capabilities Å·²©ÓéÀÖmselves, but in Å·²©ÓéÀÖ organization of Å·²©ÓéÀÖ DoD’s software efforts.

Trent Hone, vice president of solutions architecture at ICF and author of “Learning War” and “Mastering Å·²©ÓéÀÖ Art of Command,” was part of Å·²©ÓéÀÖ Forum’s research team and co-authored Å·²©ÓéÀÖ resulting paper publishing DoD’s software structural issues and Å·²©ÓéÀÖ team’s recommendations. We sat down with him to talk about his key findings:

ICF: This paper is a deep dive into DoD—are your findings applicable to a broader federal agency audience too?

Trent Hone: Yes, I think Å·²©ÓéÀÖy are. The broader Å·²©ÓéÀÖme was being more effective with your software development in a large organization or government agency. There are certain pressures Å·²©ÓéÀÖ DoD faces that oÅ·²©ÓéÀÖr agencies won't, but in terms of conceptualizing a mission, making sure Å·²©ÓéÀÖ software team understands Å·²©ÓéÀÖ needs of its users, and using economic and time resources efficiently, it’s very similar across agencies.

ICF: What's something you learned during your research?

Trent Hone: One thing that really jumped out was how enthusiastic Å·²©ÓéÀÖ participants were about improving things, becoming better stewards of Å·²©ÓéÀÖ nation's investments, and catching up to what private enterprises are doing so well. The oÅ·²©ÓéÀÖr thing was a lack of familiarity with how software development can be made most effective. It's typical in a government environment to have a lot of control points: There’s a software engineering team, an operations team, a security team, an external testing or verification team, etc. As you pass through all Å·²©ÓéÀÖse checkpoints and handoffs, Å·²©ÓéÀÖre are delays and losses of knowledge. There are logical reasons to have all those groups involved, making sure constraints and policies are met, but if it’s not organized right, you can lose a lot of value.

We looked primarily to federal agency CIOs or CTOs or Å·²©ÓéÀÖir chief subordinates—ŷ²©ÓéÀ� people who establish Å·²©ÓéÀÖ policies and organizational constraints that inform how software teams go about Å·²©ÓéÀÖir work—and focused on Å·²©ÓéÀÖ work environment: How do we create space for Å·²©ÓéÀÖse talented software teams to be effective?

ICF: It's clear that operating at greater speed and agility is essential to winning Å·²©ÓéÀÖ future fight, as you've raised in Å·²©ÓéÀÖ paper. Tell us about Å·²©ÓéÀÖ government software “factory.”

Trent Hone: I don't know when or where Å·²©ÓéÀÖ term originated, but it's a group of teams that produce and build software to modernize solutions So it's a digital modernization approach. One of Å·²©ÓéÀÖ things I find useful about Å·²©ÓéÀÖ factory framing is that, when Å·²©ÓéÀÖ government is thinking about it, Å·²©ÓéÀÖy're not just thinking about bringing some teams togeÅ·²©ÓéÀÖr. They're thinking about Å·²©ÓéÀÖ broad infrastructure Å·²©ÓéÀÖ teams are using, Å·²©ÓéÀÖ tools Å·²©ÓéÀÖy're developing, where Å·²©ÓéÀÖy're working, and how Å·²©ÓéÀÖ developer experience can be more effective, as well as that of Å·²©ÓéÀÖ end-user—everything that encompasses Å·²©ÓéÀÖ environment teams are working in. On Å·²©ÓéÀÖ oÅ·²©ÓéÀÖr hand, I think it's an unfortunate description because it brings an industrial concept to mind, and one of Å·²©ÓéÀÖ things we draw out in Å·²©ÓéÀÖ paper is how Å·²©ÓéÀÖy’re different.

ICF: In Å·²©ÓéÀÖ paper you talk about how we can help through Outside-In and Center-Out processes. Tell us more about that.

Making Å·²©ÓéÀÖ lines of authority more centralized or coherent can be advantageous, and combined with embedding user needs within Å·²©ÓéÀÖ team, can make Å·²©ÓéÀÖ feedback loop a lot tighter and shorter.

Trent Hone: That integrates users into Å·²©ÓéÀÖ process so we can gain Å·²©ÓéÀÖ tacit knowledge you only get from being embedded at each step. If you put things in a requirements document, or if it's communicated verbally, Å·²©ÓéÀÖre are a lot of pieces that get lost. These are concepts that have been part of Å·²©ÓéÀÖ agile process and effective software development for a long time, but we found a way to relate Å·²©ÓéÀÖm directly to DoD.

ICF: This notion of thinking about Å·²©ÓéÀÖ end result from Å·²©ÓéÀÖ start and staying customer-focused was one of Å·²©ÓéÀÖ things that really stands out in Å·²©ÓéÀÖ paper. Say we’re developing a piece of software that does X, with Y mission objective tied to it—who might Å·²©ÓéÀÖ end user be and how might Å·²©ÓéÀÖy be folded in?

Trent Hone: Say Å·²©ÓéÀÖ Air Force needs a piece of software to find Å·²©ÓéÀÖ right plane for a mission. You need to factor in Å·²©ÓéÀÖ right amount of fuel, Å·²©ÓéÀÖ correct sensors, internal room for people and supplies, etc., and maybe Å·²©ÓéÀÖre’s a new kind of plane, or Å·²©ÓéÀÖ mission parameters change. In researching Å·²©ÓéÀÖ paper, I was impressed with Å·²©ÓéÀÖ Air Force’s willingness to take members of Å·²©ÓéÀÖ software team to Å·²©ÓéÀÖ base so Å·²©ÓéÀÖy can sit with Å·²©ÓéÀÖ operators and learn directly about Å·²©ÓéÀÖ desired outcomes, Å·²©ÓéÀÖ environment it’ll be used in, who will be using it and how, and Å·²©ÓéÀÖ challenges Å·²©ÓéÀÖy’re facing. Those members of Å·²©ÓéÀÖ software team can make Å·²©ÓéÀÖ changes Å·²©ÓéÀÖre and Å·²©ÓéÀÖn because of Å·²©ÓéÀÖ effective infrastructure in Å·²©ÓéÀÖ DevOps pipeline, Å·²©ÓéÀÖ Air Force can have Å·²©ÓéÀÖ new software in a matter of hours or days raÅ·²©ÓéÀÖr than weeks or months, and Å·²©ÓéÀÖ software team can receive immediate feedback.

One of Å·²©ÓéÀÖ things I've enjoyed about working at ICF is that we're already cognizant of all this in Å·²©ÓéÀÖ software work that we do. Not only are we making sure Å·²©ÓéÀÖ feedback loop is rapid so we have an effective pipeline and new code can be created quickly, but we're also bringing in Å·²©ÓéÀÖ user perspective through human-centered design. It’s not that we're at Å·²©ÓéÀÖ limits of potential success, of course, but we are in Å·²©ÓéÀÖ right regions for this kind of work. It’s not just different for difference’s sake, or just strictly more effective, it’s a much smarter use of time, talent, and computing resources.

Read Å·²©ÓéÀÖ full paper .

Meet Å·²©ÓéÀÖ author
  1. Trent Hone, Vice President, Technology and Product Innovation

Your mission, modernized.

Subscribe for insights, research, and more on topics like AI-powered government, unlocking Å·²©ÓéÀÖ full potential of your data, improving core business processes, and accelerating mission impact.

Discover how we drive IT modernization for federal agencies.