Changes in software development

October 4, 2011 — The traditional way to develop software is to create an exhaustive list of requirements, write the code, test and deliver.

This can take years.

Today’s rapidly changing technology marketplace is forcing managers of large projects to look at ways that are more flexible.

For example, what if you had defined project requirements one year ago without even considering mobile devices?

If you read Vivek Kundra’s 25 points carefully, you will see a reference to changing the way software development takes place.

To wit:

  • Deliver new working functionality to users at least every 12 months
  • Deliver capabilities in small chunks frequently
  • Capture and incorporate feedback during the process.

Agile software development incorporates all of these concepts.

Today’s interview is with Richard Cheng, who is the lead of the Agile Center of Excellence at Excella.

Cheng will define confusing terms like “sprint,” “product backlog,” and “time box.”

He also enumerates examples of successful agile software deployment in many agencies, including the F.B.I, NASA, and the Department of Veteran Affairs.

Copyright © 2023 Federal News Network. All rights reserved. This website is not intended for users located within the European Economic Area.

Federal Tech Talk

TUESDAYS at 1:00 P.M.

Host John Gilroy of The Oakmont Group speaks the language of federal CISOs, CIOs and CTOs, and gets into the specifics for government IT systems integrators. Follow John on Twitter. Subscribe on Apple Podcasts or Podcast One.