As states warm to agile, agency adoption pays dividends from continuous improvement

On the second episode of this season of StateScoop’s Priorities podcast, leaders from Colorado, Vermont and North Carolina weigh in on their agile methodology efforts.

Ryan Johnston
Ryan Johnston Editorial Intern

Ryan Johnston is an editorial intern for Scoop News Group. Johnston contributes content to all SNG publications.


Agile software development is one of the most exciting advancements in government IT, but officials from Vermont, North Carolina and Colorado are becoming more familiar with the hurdles — and benefits — to implementing it.

In a survey conducted in 2017 by the National Association of State Chief Information Officers, 70 percent of state government IT professionals reported that agile development processes are strongly supported and have mitigated ineffective IT projects and project failures. The development process, which calls for more frequent communication and collaboration between vendors and customers, is quickly becoming the standard for state officials.

“The state of Vermont is in its early stages of adopting and implementing agile methodologies, and we’re currently engaging in statewide lean process improvements through the governor’s program to improve Vermont outcomes together initiative, which began in about 2017,” says Sandra Vachon, enterprise project management office director for the state of Vermont. “Many folks in the state are getting trained on lean methodology and I do believe that this has been extremely helpful to begin setting the tone for the direction that we want to go in — becoming more focused on continuous improvement in an agile environment.”

Vachon’s experiences with early implementations of agile methodologies mirror those of Glenn Poplawksi, chief solutions officer of North Carolina’s IT department. Poplawski says that he’s seen businesses get usable products sooner as the state has adopted the methodology incrementally over the last few years. Training the project stakeholders — on all sides — in agile has also been key to effective adoption, Poplawski says.

“We’ve also seen in the last five years agile adoption where there’s more of a centralized development team doing custom development again using Scrum and some Kanban in their operations. In both cases, where it worked well, training was given to all the key project stakeholders, including the business, which obviously fills the product owner role going forward,” he says.

The benefits have been clear to Stacy Moore and William Chumley, Colorado’s project manager and chief customer officer, as well.

“We are able on our projects to see risks, issues, bugs a lot quicker and continuously on these projects so we’re able to look at them and resolve them and address them as we go, so when we deploy, instead of deploying a big bang solution, it’s something that we do continuously and we’re more on track when we do finally deploy,” Moore says.

On the podcast:

  • Sandra Vachon, enterprise project management office director, Vermont Agency of Digital Services
  • Glenn Poplawksi, chief solutions officer, North Carolina Department of Information Technology
  • William Chumley, chief customer officer, Colorado Governor’s Office of Information Technology
  • Stacy Moore, PMO governance portfolio manager, Colorado Governor’s Office of Information Technology
  • Jake Williams, associate publisher and director of strategic initiatives, StateScoop

Things to listen for:

  • When businesses get on board with the methodology early on, it’s a much smoother process to cultivate trust between the vendor and the customer, Chumley says.
  • Every stakeholder involved — in both parties — should understand the processes, terminology and roles within agile as a methodology. When each stakeholder knows the correct approach is when Poplawski has seen success.
  • The most challenging aspect of agile to get everybody speaking the same language, Vachon says, and sometimes you have to walk before you can run — that means working in a hybrid waterfall-scrum model before going all-agile.
  • The idea that there’s no schedule in agile is a myth, Vachon says. The schedule is a cadence, with minor and major releases regularly scheduled on a weekly or quarterly basis. When customers realize this, they see the value in coming to the table.
  • Agile has saved money, delivered things faster and hastened results, which citizens will continue to demand as the appetite for IT continues to grow, Chumley said.

Priorities is StateScoop's podcast chronicling the top 10 priorities of state chief information officers. The show is based on the National Association of State Chief Information Officers' annual list of top 10 priorities, and produced in partnership with the association. Listen to Season 1 (2016) and Season 2 (2017).

Join the Conversation