Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Connected Government
- Consolidating Mission-critical Systems
- Constituent Servicing
- Continuous Monitoring: Tools and Techniques for Trustworthy Government IT
- The Data Privacy Imperative: Safeguarding Sensitive Data
- Eliminating the Pitfalls: Steps to Virtualization in Government
- Federal Executive Forum
- Federal Tech Talk
- Government Cloud Brokerage: Who, What, When, Where, Why?
- Government Mobility
- Mission-critical Apps in the Cloud
- Mobile Device Management
- The Modern Federal Threat Landscape
- The Path from Legacy Systems
- Understanding the Intersection of Customer Service and Security in the Cloud
Shows & Panels
Agile software development in the federal government
Tuesday - 12/3/2013, 7:26pm EST
Today on "Federal Tech Talk", host John Gilroy interviews two proponents of agile software development who will detail how to apply it to a federal agency.
In the studio are Mehul Sanghani, CEO, and Jeremy Kolonay, development manager, at the Octo Consulting Group.
During the interview, they discuss several aspects of agile software development.
The team from Octo talked about federal reporting practices, traditional artifact review, and the difficulty in getting timely and frequent input.
Two key concepts are cultural readiness and the language of agile.
Every profession seems to develop a specific language.
Lawyers are famous for idiosyncratic terminology, but federal workers are certainly famous for their abbreviations and acronyms.
Terms like "Spring" and "Product Manager" are defined and applied to the federal space.
It is one thing to change the wording process, a completely different task to change the culture of a federal agency when it comes to defining requirements.
Some lack trust in iterative solutions.
During the interview, Sanghani gives success stories from federal agencies that have made the switch.