Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
Shows & Panels
Changes in software development
Tuesday - 10/4/2011, 8:57pm EDT
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.
- 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.
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.