{"title":"Surviving the Economic Downturn","authors":"J. Davis, T. J. Andersen","doi":"10.1109/AGILE.2009.40","DOIUrl":null,"url":null,"abstract":"The national financial market turmoil that began in 2008 and continues to this day forced Iowa Student Loan and other student loan providers to make significant changes. This is a story about how Iowa Student Loan found innovative ways to continue to meet the need for private student loans and how the technical changes needed to accomplish this were implemented with relative ease. Three different periods of time are analyzed from 2007-2009 and conclusions are drawn to determine possible sources of our success. The main conclusions are: ensuring the business and development teams are speaking the same language, writing tests in a way that is easy to understand, having business-savvy developers and tech-savvy business analysts, paying down technical debt is a necessary and continual aspect of system design, the importance of prioritization, and making undefined requirements as configurable as possible.","PeriodicalId":280848,"journal":{"name":"2009 Agile Conference","volume":"23 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-08-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Agile Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AGILE.2009.40","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 7
Abstract
The national financial market turmoil that began in 2008 and continues to this day forced Iowa Student Loan and other student loan providers to make significant changes. This is a story about how Iowa Student Loan found innovative ways to continue to meet the need for private student loans and how the technical changes needed to accomplish this were implemented with relative ease. Three different periods of time are analyzed from 2007-2009 and conclusions are drawn to determine possible sources of our success. The main conclusions are: ensuring the business and development teams are speaking the same language, writing tests in a way that is easy to understand, having business-savvy developers and tech-savvy business analysts, paying down technical debt is a necessary and continual aspect of system design, the importance of prioritization, and making undefined requirements as configurable as possible.