Shows & Panels
- AFCEA Answers
- Ask the CIO
- The Big Data Dilemma
- Carrying On with Continuity of Operations
- Connected Government
- Constituent Servicing
- Continuous Monitoring: Tools and Techniques for Trustworthy Government IT
- The Cyber Imperative
- Cyber Solutions for 2013 and Beyond
- The Data Privacy Imperative: Safeguarding Sensitive Data
- Expert Voices
- Federal Executive Forum
- Federal IT Challenge
- Federal Tech Talk
- Mission-critical Apps in the Cloud
- The Modern Federal Threat Landscape
- The Path from Legacy Systems
- The Real Deal on Digital Government
- The Reality of Continuous Monitoring... Is Your Agency Secure?
- Veterans in Private Sector: Making the Transition
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.