Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Financial services firm adopts agile for digital development

Clint Boulton | June 24, 2016
Principal Financial Group turned to agile to quickly build more software for its insurance, retirement planning and asset management customers.

Financial services companies have traditionally shrunk from the notion of releasing applications that haven't been thoroughly baked and battled tested. But in today's digital world, companies that agonize over building the perfect app risk losing out to more nimble competitors. That's why many companies are turning to agile software development to push more products out the door and rescue other projects from oblivion.

This is certainly true for Principal Financial Group, a provider of insurance, retirement planning and other asset management services for corporate employees. In 2013, the Des Moines, Iowa, (needed?) company was struggling to prioritize and complete software projects. One insurance business unit in hyper-growth mode couldn't get group benefits products to market fast enough. A services unit was slogging through a project that had gone on for too long and had no end in sight.

The units rescued their respective projects with an agile methodology in which IT and business unit leaders collaborate on feature requirements in bi-weekly sprints, after which they are regularly refined and upgraded. A feature here and a feature there enable the app to be built iteratively. If some features don't work, they can be nipped and tucked without breaking the app. "Two different strategies for two different business units and both were very successful," Principal CIO Gary Scholten tells CIO.com.

Neither group would have achieved success continuing to build software with the waterfall development model, in which IT would spend several months building software based on business requirements. But in a world where consumers prefer to interact with brands online and from mobile devices, time-to-market velocity and minimum viable products are prized over deliberation and polished code.

Agile begets business agility

Scholten knows the value of agile full well and so did his software engineers, who in 2013 began hosting internal hackathons and invited employees to submit ideas for projects they should work on and vote on them. These hackathons, along with the company's increased focus on building digital products that enable customers to better manage their money, paved the path for broader agile adoption at Principal. "It really helped to accelerate the 'Oh, you can do things differently here and helped drive the concept of agile’," Scholten says.

Doing things differently can be code for striving for more nimble product development and continuous deployment. But agile also poses a cultural shift for organizations whose employees are unaccustomed to moving faster. It's best to start slowly, according to a Gartner report published in March. The researcher firm cautioned against "big bang" approaches to agile that could trigger significant cultural disruption, particularly among the IT team. For example, an overemphasis on subject matter expertise, or role specializations can lead to feelings of inequality on the agile team, leading to bottlenecks in deliverables.

 

1  2  Next Page 

Sign up for Computerworld eNewsletters.