The existing accounting system resides mainframe

Problems with costs come about for many reasons, including

Mustang Enterprise’s New Accounting System
You are a stakeholder of the New Accounting System project for Mustang Enterprises. The existing accounting system resides on a mainframe, and some of the programs used to process data are more than 15 years old. Your company decided to hire a contract software services firm to write a thin-client, browser-based version of the accounting system so that the mainframe programs could be retired. You’ve also assigned a senior programmer to act as the project manager on behalf of your organization.

The project is in the Monitoring and Controlling process

After further investigation, you discover that the project manager changed the database from SQL to Oracle midway through the project and didn’t tell anyone except the project team. The project scope stated specifically that project development required a SQL database. The change in database products changed the project scope and product scope without letting the stakeholders know.

This change has caused schedule delays because the project team members have told you they need to be trained to use the new database development tools before they can proceed. Additionally, many of the programs have already been written to interface with SQL, not Oracle, and will have to be modified. To add insult to injury, the database switch will impact the project budget in two ways. First, purchasing the Oracle database involves substantially more money than purchasing the SQL database, and it requires the purchase of new development tools for the programming team. Second, several members of the programming staff will have to attend multiple training sessions on the new database product to fully integrate the programs and system. Training is currently running $2,200 per session per person.