CASE: PETRIES ELECTRONICS Systems Planning and Selection Now that the No Customer 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 plan. He first drafted the project scope statement and posted it on the projects intranet (see PE Figure 4-1). Once posted on the intranet, he sent a short e-mail message to all team members requesting feedback. Minutes after sending the e-mail, Jims office phone rang. Jim, its Sally. I just looked over the scope statement and have a few comments. Great, replied Jim, its 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. How- ever, the scope statement is a pretty high-level document and doesnt get into too much detail. Basi- cally, its 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 be coming next. Oh, OK, that makes sense. I have never been on a project like this, so this is all new to me, said Sally. Dont 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 develop the baseline project plan, we do a very thorough feasibility analysiswe examine financial, technical, operational, schedule, legal and contractual feasibility, as well as potential political issues my last job was that there are great benefits to following a fairly formal project management process with a new system. By moving forward with care, we are much more likely to have the right system, on time and on budget. So, asked Sally, what is the next step? Well, we need to do the feasibility analyses I just mentioned, which become part of the projects base- line project plan. Once this is completed, we will have a walkthrough presentation to management to make sure they agree with and understand the scope, risks, and costs associated with making No Customer Escapes a reality, said Jim. This is going to be a lot of work, but I am sure I am going to learn a lot, replied Sally. So, let me get to work on the feasibility analyses, said Jim. I will be sending requests out to all the team members to get their ideas. I should have this e- mail ready within an hour or so. Great, Ill look for it and respond as soon as I can, answered Sally. Thanks, the faster we get this background work done, the sooner we will be able to move on to what the system will do, replied Jim. Sounds good, talk to you later. Bye, Sally said. Bye Sally, and thanks for your quick feedback, answered Jim.

1. What are some of the specific feasibility issues the team could run into during this project?