Development

Agile comes with pressure and pain

Agile development often takes federal employees out of their comfort zones, which is precisely why it's so beneficial, IT leaders say.

During a panel discussion sponsored by the Association for Federal Information Resources Management, Environmental Protection Agency CTO Greg Godbout said agile's short delivery cycles require regular meetings and demand accountability.

"You know you will see them every two weeks," he said, and "the group will ask, 'Who didn't deliver?'"

That kind of pressure can produce results, said David Shive, CIO at the General Services Administration.

He added that GSA adopted agile development several years ago and retooled some of its acquisition and business operations using the techniques. The improvements did not come without pain, however. He said 60 percent of the people involved were wary of agile development, but the other 40 percent were ready to get their hands dirty in the "scrums" that set the agenda for agile development.

Shive said the techniques have soaked deeply into GSA and transformed business services delivery by making IT a "shared outcome" for the staff and its agency customers.

Implementing agile development for the first time, however, can be messy and uncomfortable. Peggy Stroud, deputy CIO in the Agriculture Department's Rural Development office, said she was responsible for adopting agile techniques under the watchful eye of Agriculture Secretary Tom Vilsack.

The process involved getting people out of their comfortable cubicles and into conference rooms, which she said she "stuffed with buffet tables" to lure dozens of employees together to hash out needs and expectations.

"The first six months are hard," she said, but eventually people are forged into teams working toward the same goal.

She cautioned that adopting agile "doesn't happen overnight." But USDA officials persevered and used the techniques to develop an online application that speeds rural loan applications.

Technology comes and goes, she said, but people and teamwork are the keys to agile success.

About the Author

Mark Rockwell is a senior staff writer at FCW, whose beat focuses on acquisition, the Department of Homeland Security and the Department of Energy.

Before joining FCW, Rockwell was Washington correspondent for Government Security News, where he covered all aspects of homeland security from IT to detection dogs and border security. Over the last 25 years in Washington as a reporter, editor and correspondent, he has covered an increasingly wide array of high-tech issues for publications like Communications Week, Internet Week, Fiber Optics News, tele.com magazine and Wireless Week.

Rockwell received a Jesse H. Neal Award for his work covering telecommunications issues, and is a graduate of James Madison University.

Click here for previous articles by Rockwell. Contact him at mrockwell@fcw.com or follow him on Twitter at @MRockwell4.


Featured

  • FCW PERSPECTIVES
    sensor network (agsandrew/Shutterstock.com)

    Are agencies really ready for EIS?

    The telecom contract has the potential to reinvent IT infrastructure, but finding the bandwidth to take full advantage could prove difficult.

  • People
    Dave Powner, GAO

    Dave Powner audits the state of federal IT

    The GAO director of information technology issues is leaving government after 16 years. On his way out the door, Dave Powner details how far govtech has come in the past two decades and flags the most critical issues he sees facing federal IT leaders.

  • FCW Illustration.  Original Images: Shutterstock, Airbnb

    Should federal contracting be more like Airbnb?

    Steve Kelman believes a lighter touch and a bit more trust could transform today's compliance culture.

Stay Connected

FCW Update

Sign up for our newsletter.

I agree to this site's Privacy Policy.