This case is based on a true story and illustrates some of the key challenges that IT organizations face when they attempt to develop solutions for clients. Many of these clients understand their problems but don$$t see how to create an appropriate solution. Others, however, think they understand their needs but find the solutions generated for them to be inadequate or simply addressing the wrong issues. It is a classic story of cope definition that many IT organizations routinely deal with when trying to satisfy the needs of clients.

Questions:

How would you begin redesigning Dotcom.com$$s project management processes to minimize the problems they are experiencing with poor scope management?

How do the company$$s consulting clients contribute to the problems with $$scope creep?$$ If you were to hold a meeting with a potential customer, what message would you want them to clearly understand?

How do you balance the need to involve clients with the equally important need to freeze project scope in order to complete the project in a timely fashion?

Why are configuration management and project change control so difficult to perform in the midst of a complex software development project such as those undertaken by Dotcom.com?