ERP Proposal ProjectPart B: Samples for each

section

• 2

For each of the items under A through H be sure to have:1) Heading2) Introductory paragraph3) Some explanation, discussion, and/or analysis4) And document all non-original work.

• Information Technology Project Management, Seventh Edition

• 3

Table 4-1. Project Charter for the DNA-Sequencing Instrument Completion Project

• Information Technology Project Management, Seventh Edition

• 4

Table 4-1. Project Charter (cont.)

• Project scope statements should include at least a product scope description, product user acceptance criteria, and detailed information on all project deliverables. It is also helpful to document other scope-related information, such as the project boundaries, constraints, and assumptions. The project scope statement should also reference supporting documents, such as product specifications

• As time progresses, the scope of a project should become more clear and specific

Defining Scope

• 5

Table 5-3: Further Defining Project Scope

6

Figure 5-4. Sample Intranet WBSOrganized by Phase

7

Figure 5-5. Intranet WBS and Gantt Chart in Microsoft Project

8

Figure 6-5. Gantt Chart for Project X

9

Figure 6-4. Sample PDM Network Diagram

10

• PERT weighted average = optimistic time + 4X most likely time + pessimistic time

6

• Example:PERT weighted average = 8 workdays + 4 X 10 workdays + 24 workdays = 12 days

6where optimistic time= 8 daysmost likely time = 10 days, andpessimistic time = 24 days Therefore, you’d use 12 days on the network diagram instead of

10 when using PERT for the above example

PERT Formula and Example

• 11

Figure 7-4. Surveyor Pro Project Cost Baseline

12

Earned Value Calculations for a One-Year Project After Five Months

• 13

Figure 9-3. Sample Organizational Chart for a Large IT Project

14

Figure 9-4. Work Definition and Assignment Process

15

• A responsibility assignment matrix (RAM) is a matrix that maps the work of the project as described in the WBS to the people responsible for performing the work as described in the OBS

• Can be created in different ways to meet unique project needs

Responsibility Assignment Matrices

• 16

Figure 9-5. Sample Responsibility Assignment Matrix (RAM)

17

1. Stakeholder communications requirements2. Information to be communicated, including format, content, and level of detail3. Who will receive the information and who will produce it4. Suggested methods or technologies for conveying the information5. Frequency of communication6. Escalation procedures for resolving issues7. Revision procedures for updating the communications management plan8. A glossary of common terminology

Communications ManagementPlan Contents

• 18

Table 10-1. Sample Stakeholder Analysis for Project Communications

19

• A statement of work is a description of the work required for the procurement

• If a SOW is used as part of a contract to describe only the work required for that particular contract, it is called a contract statement of work

• A SOW is a type of scope statement

• A good SOW gives bidders a better understanding of the buyer’s expectations

Contract Statement of Work (SOW)

• 20

Figure 12-3. Statement of Work (SOW) Template

21

• Request for Proposals: Used to solicit proposals from prospective sellers– A proposal is a document prepared by a seller when there

are different approaches for meeting buyer needs • Requests for Quotes: Used to solicit quotes or

bids from prospective suppliers– A bid, also called a tender or quote (short for quotation), is a

document prepared by sellers providing pricing for standard items that have been clearly defined by the buyer

Procurement Documents

• 22

Figure 12-4. Request for Proposal (RFP) Template

23