!!! PLEASE ANSWER, VERY URGENT !!!

In 2008, PCWorld magazine named Copland to a list of the biggest project failures in IT history. Apple's Copland Operating System It's easy to forget these days just how desperate Apple Computer was during the 1990s. When Microsoft Windows 95 came out, it arrived with multitasking and dynamic memory allocation, neither of which was available in the existing Mac System 7. Copland was Apple's attempt to develop a new operating system in-house; actually begun in 1994, the new OS (Operating System) was intended to be released as System 8 in 1996. Copland's development could be the poster child for feature creep. As the project gathered momentum, a furious round of empire building began. (In business, empire-building is demonstrated when individuals or small groups attempt to gain control over key projects and initiatives to maximize job security and promotability) As the new OS came to dominate resource allocation within Apple, project managers began protecting their fiefdoms* by pushing for their products to be incorporated into System 8. New features began to be added more rapidly than they could be completed. Apple did manage to get one developers' release out in late 1996, but it was wildly unstable and did little to increase anyone's confidence in the company. Before another developer release could come out, Apple made the decision to cancel Copland and look outside for its new operating system; the outcome, of course, was the purchase of NeXT, which supplied the technology that became OS X. *Fiefdom: a territory or sphere of operation controlled by a particular person or group. Question #1: What went wrong for Apple's Copland Operating System Project? What would be the primary lesson learned for this project? In 2008, PCWorld magazine named Copland to a list of the biggest project failures in IT history. Apple's Copland Operating System It's easy to forget these days just how desperate Apple Computer was during the 1990s. When Microsoft Windows 95 came out, it arrived with multitasking and dynamic memory allocation, neither of which was available in the existing Mac System 7. Copland was Apple's attempt to develop a new operating system in-house; actually begun in 1994, the new OS (Operating System) was intended to be released as System 8 in 1996. Copland's development could be the poster child for feature creep. As the project gathered momentum, a furious round of empire building began. (In business, empire-building is demonstrated when individuals or small groups attempt to gain control over key projects and initiatives to maximize job security and promotability) As the new OS came to dominate resource allocation within Apple, project managers began protecting their fiefdoms* by pushing for their products to be incorporated into System 8. New features began to be added more rapidly than they could be completed. Apple did manage to get one developers' release out in late 1996, but it was wildly unstable and did little to increase anyone's confidence in the company. Before another developer release could come out, Apple made the decision to cancel Copland and look outside for its new operating system; the outcome, of course, was the purchase of NeXT, which supplied the technology that became OS X. *Fiefdom: a territory or sphere of operation controlled by a particular person or group. Question #1: What went wrong for Apple's Copland Operating System Project? What would be the primary lesson learned for this project