Agility has been a key attribute for success over the past year and a half. Everyone had to quickly adapt in their personal and professional lives to do things in new ways to keep business and society running. Even the great bureaucracy of government found itself pivoting and quickly changing "how it's always been done" to meet the needs of the day. This should not end with the return to what feels like pre-pandemic normal. In the form of Agile methodology, Agility will play a huge role in the government's ability to continue the fast-forwarded digital push as a result of the pandemic.
Just as government pushed agencies to try Cloud with the "Cloud First" initiative, some are suggesting the same approach for Agile. An "Agile-First" evolution would have a huge impact on IT modernization efforts, accelerating the move from legacy processes and technology to a modern digital approach. The response to COVID-19 showed that the government can move quickly in changing how they do work (across all areas of government). An Agile-first "mandate" could institutionalize that speed and make it the rule rather than the exception.
DevOps, a combination of the words development and operations, is designed to smooth the frequently problematic handoff between an organization's developers and its operations staff. It is an operational philosophy that has technology developers and the operational team who will use the technology working together closely through the entire development of a technology solution. The goal of this approach is quick releases of solutions that have an immediate impact on how people do their jobs.
On the surface this sounds like a perfect fit for government, an "industry" in need of fast digital transformation to meet citizen needs. The DevOps promise of making application development quicker and cheaper is incredibly attractive to the government. However, the third part of the promise, collaboration, proves to be the most problematic as culture and process stand in the way.
From a culture perspective, organizations need to break down silos and create brand new teams focused on an application's output, rather than on tactical roles. To achieve this goal, individuals need to be empowered with autonomy and be enabled with strong communication skills to ensure everyone understands their roles and buys into the overall project objective. As U.S. Special Operations Command CIO Lisa Costa described it, "creating a DevOps culture is akin to practicing tactical shooting. You remove all extraneous movement, and that's how you get efficiency." She said her team focused on stripping away processes that had accumulated over the years but were not serving the objective of getting solutions out to the field quickly. Continue reading →
As government agencies look to respond to modernization calls from the executive branch as well as citizens at large, agile and DevOps practices are being employed to help speed time to "market" with new applications. A report issued in early 2019 found that sixty-nine percent of respondents said that their organizations are piloting agile, if not partially or fully adopting it. But, the same report also saw a significant percentage of respondents say that agile met their expectations "less than expected" and "much less than expected." So, if agile is seeing an uptick in use, why is it not meeting expectations?
The issue may lie heavily in training and understanding. Agile is not just a new process; it's a new mindset. It requires a new organizational structure that is a departure from the traditional command and control hierarchy of government. Agile teams are relatively flat with everyone holding interconnected and equally important roles. There's not only a logistical change that needs to happen in terms of org charts and structures, but also a cultural shift to a collaboration-driven rather than command-driven environment.
To begin really seeing the benefits of adaptability, speed, and cost efficiencies agile promises, people need to be trained not only on the process but on the softer skills of communication and collaboration that power the process. We've pulled together a collection of upcoming events that may help. Continue reading →
There's a huge buzz and movement about opening up government. There are three phrases that are used frequently in relation to openness in government but each mean something a bit different.[Tweet "The focus on openness is changing the way IT is designed, developed, and implemented. #GovEventsBlog"]
Open Government - This is a core tenant of our democracy, the belief that citizens have the right to access the documents and proceedings of the government to allow for effective public oversight. While this has always been a practice of government (via the Freedom of Information Act), with the move to digital records the way people want to receive and the way the government can share information has changed dramatically.
Open Data - This is data that can be freely used, re-used and redistributed by anyone. Much of the information the government holds should be open data, but giving people the access they require has been a stumbling block to open government.
Open Source - This is the technical piece of the "open" puzzle. Open Source is software for which the code is made freely available and may be used and changed. Open Source solutions allow people to not only get at the data but also work with that data in new ways.
Code-a-thons and hack-a-thons have moved out of the basements of Silicon Valley and into ballrooms across the country. These events are usually one or two day intensive sessions where software developers work in teams to develop a technology solution to a stated challenge.
Recently, the Department of Health and Human Services (HHS) hosted one as part of their efforts around the national opioid crisis. The Opioid Symposium and Code-a-Thon allowed HHS to educate attendees on their five-part strategy for combatting opioid abuse. The event posed three challenge questions to programmers from private industry, academia, and government. From there, the 50 teams began designing solutions for the next 24 hours. Winners in each of the three tracks were selected the following day.[Tweet "New #GovEventsblog article: Adding Code-A-Thons to the Event Mix"]
While this in-person event was specific to a single government agency, the federal government as a whole has been hosting virtual code-a-thons since the launch of challenge.gov in 2010. This site allows federal agencies to submit a problem that needs a technical solution. Prize money is offered, and a time frame is given for the development of working code. Both individuals and companies are eligible to participate in solving complex, mission-centric problems. Continue reading →