10 ways to make agile development work for you

Need a tip or two for how to make the best of an agile approach? How about 32?

The Government Accountability Office has released a report of best practices and approaches for applying agile software development methods to IT projects.

Agile development has been touted as a remedy to drawn-out IT projects that go over budget and lag behind schedule. The Office of Management and Budget recently began advocating for an agile approach, which calls for producing software in increments. The idea is that agile will improve the way in which the federal government develops and implements IT.

Several agencies have already started trying agile development. The Veterans Affairs department, for example, used agile to develop software to support a new benefit for veterans. The Defense Department developed the Global Combat Support System-Joint using agile.

In its newly released report, GAO identified best practices and approaches as effective for taking an agile approach. The practices align with five key software development project management activities: strategic planning, organizational commitment and collaboration, preparation, execution and evaluation. Ten practices were identified as particularly effective:

1. Start with agile guidance and an agile adoption strategy.
2. Enhance migration to agile concepts using agile terms and examples.
3. Continuously improve agile adoption at project and organization levels.
4. Look to identify and address impediments at the organization and project levels.
5. Get stakeholder/customer feedback often.
6. Empower small, cross-functional teams.
7. Include requirements related to security and progress monitoring in your queue of unfinished work.
8. Gain trust by showing value at the end of each iteration.
9. Use tools and metrics to track progress.
10. Track progress daily and openly.

The report also found more than a dozen challenges with the agile approach for federal agencies, including collaboration issues, mistrust in iterative solutions and unclear agile guidance. Other concerns entailed how projects are managed differently in an agile approach as opposed to a more traditionally used waterfall development environment.

But those challenges could potentially fade away as agile becomes more a standard. Agencies in the early phases of adopting this approach can then draw from the knowledge of those with more experience. The Federal CIO Council is currently working to create a policy on modular development, which the GAO report said will provide an opportunity to share experiences. 

About the Author

Camille Tuutti is a former FCW staff writer who covered federal oversight and the workforce.

Cyber. Covered.

Government Cyber Insider tracks the technologies, policies, threats and emerging solutions that shape the cybersecurity landscape.


Reader comments

Tue, Aug 7, 2012 John US

How about automated testing? Nothing sheds light on the status of a unit of work or project/program like granular red/green pass fail or rolled up meaningful test metrics. What better way for a developer to document a requirement than with a plain english expression of what the story/task needs to do to be done that the stakeholder can read and say YES. Lack of a statement about automated testing in the GAO report suggest the public sector is going to repeat mistakes made by 1st generation agile adoption efforts by a limited focus on qualitative management techniques and not enough on quantitative engineering metrics produced by automated processs. . The most highly reliable metrics are the system generated ones that came from a proper automated testing infrastructure. The results can not be manipulated to make things look better than they are. It is the most important and most overlooked area of new agile projects. Even if a team does not follow XP to the zealotous letter they should understand it and at least try implementing basic continuos integration process. Lots of great free tools out there. Some are open source. It is the ice burge of success hiding under the surface.

Mon, Aug 6, 2012

How about impressing upon the agile developers the importance of documenting requirements and code. Agile has much to offer if the perception of creating artifacts is included in the methodology (needed for auditing, baseline control, IA and security purposes).

Wed, Aug 1, 2012

How about adding a step for security?

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group