Mike's Tees, a relatively large company that prints T-shirts, is developing a system that allows customers to upload their image files on a server and have them printed on T-shirts. The project was drafted and planned to start several months ago; however, the key stakeholders decided that it would have to wait while they remodeled their IT infrastructure. It is now time to pick up where they left off.

Recent budget cuts have decreased the amount of money allocated for this project by 45% from the original estimates. Also, because of the late start, the development schedule has been shortened by about 40%.

The IT manager wants this system fully integrated with the new IT framework. The CEO would like to automate the process as much as possible. The lead programmer thinks some of the requests are not logically or physically feasible. He is also concerned that the new time constraints are woefully inadequate. He proposes licensing a similar system owned by an IT solutions company, but warns that this system only meets 65% of the key stakeholders' requirements.

The PM has to orchestrate a significant project with little time and money and a small development team of three members. It is a very tough situation, especially considering it is her first job after her promotion to PM. She does not want to let any key stakeholders down by cutting their requirements.

What trade off would you make? Go with an alternative? Go into debt? Ask for a loan?