FCW: ‘Agile development requires agile developers’

FCWA post from FCW contends that a crucial key to successful agile development projects for agencies is to seek out teams of developers that are truly skilled and efficient — not just the ones with the lowest price tag. This could cost more time and money up front, but in the long run it’s the only way to leave behind the “startup curve” and allow organizations to reach their full potential.

From the article:

The latest trend in agile contracting is creating contract mechanisms that allow the government to buy teams of programmers and coders for short periods of time.

For example, an agency might want an agile team of seven or eight people for the next six months. But there is no ready “bench” of agile teams (much less high-performing teams) waiting to ship out whenever the government decides it needs them. Building productive teams takes time, because they need to learn to work together and to learn the mission and problem domain.

Also, leadership needs to frequently make adjustments in staffing in response to changing conditions or to correct a bad fit. Only rarely does a team become high-performing in less than six months. The result: organizations never reach their potential — which keeps costs higher and quality lower. I equate it to feeling like you’re stuck in first gear.

. . .

The lesson is clear. To improve contracting for agile development in the federal government, organizations should seek small- to medium-sized, multi-year contracts for small, high-performing teams. Hold the contractor accountable for timely, incremental delivery of quality software. Multi-year contracts allow the vendor community to hone the team over time, bring the best possible skilled team members to the mission, and deliver savings, innovation and quality to the government.

Read the full article: Agile development requires agile developers | FCW

2017-04-23T23:02:53+00:00 July 7th, 2015|Categories: Agile government|Tags: |

About the Author:

Agile Government Leadership is a community-powered network of agile government professionals. Subscribe to our newsletter or connect on LinkedIn and Twitter.

One Comment

  1. Cliff Berg July 7, 2015 at 5:01 pm - Reply

    The challenge is that short term commitments demand a higher rate, and government is generally unwilling to pay for quality teams. Government usually seeks the lowest cost bidder – and that ends up being someone who says all the right Agile buzzwords but actually does not have people who are senior and experienced with Agile methods and tools, especially in the devops realm. Those people demand a premium, and vendors increasingly release people who are on the bench, so you are asking senior in-demand people to commit to doing work without a long-term commitment, but for a budget rate. Doesn’t work.

Leave a Reply