Shows & Panels
- Accelerate and Streamline for Better Customer Service
- Ask the CIO
- The Big Data Dilemma
- Carrying On with Continuity of Operations
- Client Virtualization Solutions
- Data Protection in a Virtual World
- Expert Voices
- Federal Executive Forum
- Federal IT Challenge
- Federal Tech Talk
- Feds in the Cloud
- Health IT: A Policy Change Agent
- Improving Healthcare Outcomes through IT Policy
- IT Innovation in the New Era of Government
- Making Dollars And Sense Out of Data Center Consolidation
- Navigating the Private Cloud
- One Step to the Cloud, Two Steps Toward Innovation
- Path to FDCCI Compliance
- Take Command of Your Mobility Initiative
- 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.