@valleyr1 You are correct that companies need to remain agile. But when USAA decides to implement an API which breaks all budgeting tools ability to gather credit card transactions, Mint and other budgeting tools can't be expected to be agile to that type of change without notification. Screen scraping technology which was previously used by Mint and other budgeting tools, this allowed them flexibility when companies like USAA changed the layout of the data they present. That allowed them the ability to be somewhat agile in there support of financial data interfaces. This is one of the main reasons why companies use screen scraping versus an API for data gathering, especially for applications which they have no control over. I am not saying mint is blameless in their response to to this almost 6 months old issue, but USAA was not upfront with information to other vendors nor their customers about the change to their interface. It took months for USAA to acknowledge that they even made the change. Then it took months after that for USAA to provide the necessary information to Mint to allow them to attempt to code to this new API. I know of one free budgeting tool that is now getting USAA credit card transactions.
If you are familiar with agile development, then it likely means you understand that software change control takes time and planning to implement new features, which is what is happening based on the new USAA API. This is not a change, this was a new feature that Mint did not have on their project plans.
