CASE: PETRIE’S ELECTRONICS
Systems Planning and Selection

Now that the “No Costumer Escapes “project team has been formed and a plan has been developed for distributing project information, Jim began working on the project scope statement,workbook,and baseline project pan. He first drafted the project scope statement and posted it on the project’s intranet (see PE Figure 4-1).Once posted on the intranet, he sent a short e-mail, Jim’s office phone rang.
“Jim, it’s Sally. I just looked over the scope statement and have a few comments.”
“Great, “replied Jim, “it’s just a draft. What do you think?”
“Well,I think that we need to explain more about how the system will work and why we think this new system will more than pay for itself.”
“Those are good suggestions; I am sure many others will also want to know that information. However, the scope statement is a pretty high-level document and doesn’t get into too much detail. Basically, it’s purpose is to just formally announce the project, providing a very high-level description as well as briefly listing the objectives, key assumptions, and stakeholders. The other documents that I am working on, the workbook and the baseline project plan are intended to provide more details on specific deliverables, costs, benefits, and so on. So, anyway, that type of more detailed information will becoming next.”
“Oh, OK, that makes sense. I have never been on a project like this, so this is all new to me,” said Sally.
“Don’t worry, “replied Jim, “getting that kind of feedback from you and the rest of the team will be key for us doing a thorough feasibility analysis. I am going to need a lot of your help in identifying possible costs and benefits of the system. When we developed the baseline project plan, we do a very thorough feasibility analysis-we examine financial, technical, operational, schedule, legal and contractual