PMP Critique 2000 words report ? for project management

example_of_pmp_critque.pdf

Home >Business & Finance homework help >Management homework help >PMP Critique 2000 words report ? for project management

Project Management Plan (PMP)

University of Ballarat

Team x Project Plan

Developing a customised finance application

Team Members:

Dianne Kankas

xxxxxx

Terry Goldham

Yohan Naddam

Carren Gerden

Contents 1.0 Executive summary

2.0 Introduction

2.1 Project Overview 4

2.2 Evolution of SPMP 4

2.3 References 5

2.4 Definition and acronyms 6

3.0 Project Organisation 7

3.1.1 Organisational charts 14

3.1.2 Project responsibilities 15

4.0 Managerial Process 20

4.1 Management Objectives and Priorities 20

4.2 Assumptions, Dependencies, and Priorities 20

4.3 Risk Management 21

4.3.1 Probability Matrix 22

4.3.2 Risk Response Plan 23

4.3.3 Risk Register 24

4.4 Technical process 26

5.0 Work to be done 27

5.1 Scope of the Project 27

5.2 Work Breakdown Structure port 27

6.0 package, Schedule and Budget 28

6.1 Work Packages 28

6.2 Resource requirements 28

7.0 Budget 30

7.1.1 Detailed Budget 30

7.1.2 Other Budget Related Information 32

8.0 Conclusion 33

9.0 Bibliography

Appendix 1- Status Report Template 34

Appendix 2- Gantt chart 35

Appendix 3- WBS 18

Appendix 4- Internal Organizational Chart 10

Preface

This document, the Project Management Plan (PMP) .This

project will be used for managing the project. The Project Management Plan

outlines the scope of the project, deliverables of the project, structure of the

team, roles and responsibility of each member in the team. The Managerial

and Technical Processes have been outlined as well identification of any risks.

It also outlines the schedule and budget for each resource required.

Finally, the project plan results in conclusion and recommendations for the

reference of the project team.

1.0 Executive summary:

The project is about creating a finance application for feed

franchise. The Management Team members have strong computer

backgrounds. The information collected from the members and the sponsor

thus assigning work to each individual. The objective of the project is:-

� Creating a customized finance application contains payroll, debtors,

creditors, BAS calculation, bank reconciliation, stock control, reports

etc...

� Application should support the multi user operating system.

� Application should be web-based, running on current browsers and the

Windows Vista operating system. .

The scope of the project which defines what the project

boundaries, the project clearly and explicitly defines what the project is to

cover and not to cover. It states hardware, deliverables, assumptions and

constraints of the project. The project gives a precise definition of the

purpose and scope of the project to ensure that both Business Partners and

Technical personnel are clear about the field of reference. It explains about

the number of phases in the project. All of which creates schedule and

budget of the project. The schedule creates a timeline for each individual

phase which has to be completed by the milestone and critical path for the

project. The schedule of the projects is breaking down of work into various

categories which also brings the budget; it creates an estimate of cost for

each phase and estimate for completion date for the project.

2.0 Introduction “A project is complete when it starts working for you, rather than you

working for it.”(Scott Allen). The project clearly explains the name of the

project which is a positive aspect but it doesn’t say much of the feed

franchise and the layout. The description of the project gives a clear

statement objective of the project which very much useful for the sponsor so

that he can what is the project is all about. The sponsors detail is provided in

the project which is very essential to the project. The sponsor has to know

who has been appointed as a team for this project where the sponsor has to

be informed about the team member’s details which are done in the project

.This is a positive thing in the project. Each team member’s details like phone

number and email address is provided to contact which is very useful. The

deliverables and the documentation of the project are explained in detail

which gives a clear understanding of the project. The Reference details has

been left out or omitted in the project which is a negative aspect of the

project. The project should have references where the material was taken or

cited from which gains knowledge in order for preparing the project. The

phase review of each stage is completed at each stage and asked for

acceptance for the project which is omitted in the project which is not a good

thing in the project. However this list would be more helpful if it contained a

greater number of references.

Project manager and team details:

The Project Management Plan (PMP) outlines the project.

Project team members are responsible for documentations, which show team

has worked on PMP. Through out the development cycle all team members of

the project are responsible for updating and maintaining the Plan. At weekly

team meetings will be discussed about the various issue and motivate the

group by participating in the problem solving. If there is necessary to make

changes in the plan then it is done.

Project Deliverables

Project Management Deliverables

The major project deliverables for the project include:

Project Management Deliverables

� A completed PMP document

� A Gantt Chart

� A completed and signed-off Design document

� A completed and signed-off Test plan document

� Test reports

� A presentation to key stakeholders

� A working prototype(s)

� A project customises finance application containing all documents and

information relating to the project for team and client to view.

Application Deliverables

� Completed Customized finance application

Definitions / Acronyms

The team will apply a process models to the Customised finance

application project .The prototype model were chosen for the design of the

Term Meaning

PMP

A PMP stands for Project Management Plan. A PMP is a plan for a project

Java

Programming code

Personal Computer

Project Manager

Change Initiator

Change Sponsor

WBS

Work Breakdown Structure

RPM

Risk Probability Matrix

application because the application is planned to be built in stages. Building

the application in stages allows testing during each stage to find bugs early

and also allows the client to approve the prototype and allows the developers

to implement changes early and more efficiently then waiting till the

application is finished.

The three phases of the prototype model have been briefly described below:

Figure 1: Prototype model

Design: This is a design phase where the planning of the prototype is

done and the design of the prototype is defined...

� Implement: After the design phase, the implement phase where the

applications coding is done for the prototype and implemented.

Testing: This phase is where prototype is checked whether it is working

properly or not and check for any bugs in the application

Design

Implement

Test

References Schwalbe. K. (2004). Information Technology Project Management. (3rd Ed.). Canada: Thomson

Project Smart. (2008). Project Management Success with Top 7 Best Practices, viewed

April15th, 2008, from

http://www.projectsmart.co.uk/project_management_success.html

Method123. (2003). Project Management Life Cycle Methodology, viewed April 15,

2008, from

http://www.method123.com/project-lifecycle.php

Berkun, Scott (2005). Art of Project Management. Cambridge, MA: O'Reilly Media.

Brooks, Fred (1995). The Mythical Man-Month, 20th Anniversary Edition, Adison

Wesley. I

Comninos D &, Frigenti E (2002). The Practice of Project Management - a guide to the

business-focused approach. Kogan Page.

Heerkens, Gary (2001). Project Management (The Briefcase Book Series). McGraw-Hill.

Kerzner, Harold (2003). Project Management: A Systems Approach to Planning,

Scheduling, and Controlling, 8th Ed., Wiley.

Lewis, James (2002). Fundamentals of Project Management, 2nd ed., American

Management Association.

Meredith, Jack R. and Mantel, Samuel J. (2002). Project Management: A Managerial Approach, 5th ed., Wiley.

3.0 Organisational

Internal Organisation

Project Manager Carren Gerden

Research Specialist

Carren Gerden

Programmer Yohan Naddam

System Analyst Tanya Gillham

Consultant Tanya Gillham

Tester Yohan Naddam

Purchasing Specialist Dianne

Marketing Specialist Dianne

Business Analyst Dianne

Documenter Tanya Gillham

Tester 1 Tanya Gillham

Tester 2 Dianne

Organisational Boundaries and Interfaces Overall Project Management

Client

Project Responsibilities Roles Member Responsible

Role Definitions

Project Sponsor

A role of a Project Sponsor is to offer strategic business leadership and

directions. Some of the roles of a project sponsor are approve changes in

scope, approve budget variance and remove project barriers.

Project Manager

A role of the Project Manager is to determine and implement exact needs of

the client. Some of the roles of a project management team management,

communication, decision making. The project manager is responsible for

reducing risk significantly, ensuring that every significant participant has an

opportunity to express opinions and concerns.

Business Analyst

The role of the Business Analyst is to analyze the needs of the client and

stakeholder and provide solutions. Some of the roles are to find out the risks

and business case for the project.

Project Sponsor Sally Firmin

Project Manager Carren Gerden

Business Analyst Dianne

Systems Analyst Terry Goldham

Developer/ Programmer Yohan Naddam

Research Specialist Terry Goldham

Tester Yohan Naddam

Documenter Terry Goldham

Marketing Specialist Terry Goldham

Purchasing Specialist Dianne

Consultant Terry Goldham

System Analyst

A role of System Analyst is designing computer information systems; identify

the system requirements, modifying systems to improve the work flow or

expanding systems for new purpose.

Developer/ Programmer

The role of the programmer is to create and manage the program code.

Some of the roles of the programmer are to create prototypes and to

implement the design of the designer and test the prototypes and the final

product.

Research Specialist

The role of the Research Specialist is to research product relevant with the

project. The team are assigned to do research on similar product designed by

the competitors and collect the results to create a product to suit the

customer needs.

Tester

The role of the tester is to test the program ensure that the program is

working as expected and make appropriate changes and recheck the

program until it produces correct results.

Documenter

The role of the Documenter is to create documentation process of the entire

project. Documenter checks the integrity of the documents before the sign

off. Some of the roles of the documenter is status reports, build document,

design document, test document and ensures the standards required for the

project.

Marketing Specialist

The role of the Marketing Specialist is to create innovative ways to advertise

the products. To create an advertise campaigns for the project.

Purchasing Specialist

The role of the Purchasing Specialist is to research and purchase the

required equipments within the budget for the project. The purchasing

specialist is also responsible for the delivery of the product.

Consultant

The role of the Consultant is to provide expertise to the project team. The

consultant also provides new experiences and techniques.

Contacts

4.0 Management and Technical Process

Management Objectives and Priorities

Each project team member has their own roles

and responsibility and the manager’s role is to manage the objectives and

priorities of the team. Each member of the project team has been assigned

roles and the project manager should have an overall understanding on how

the project will operate. The project team will work solely on this project, if

more personal are required to meet the project deadline, Ms. Carren Gerden

will interview available personal and select the most suitable candidate for

the roles available. All the team members have to achieve their goals and

objective for the project. Each task is broken down to phases which are

Name Role Phone Number Email

Sally Firmin Project Sponsor 5327 9878 [email protected]

Dianne Kankas Team Member 9343 3736 [email protected]

Terry Goldham Team Member 8323 7982 [email protected]

Carren Gerden Team Member 8232 8755 [email protected]

Yohan Naddam Team Member 8563 5345 [email protected]

displayed in the Gantt chart. To identify the risk factors in the project, the

team members have to follow the procedures to identify and to resolve the

risks.

Assumptions, Dependencies and Constraints

� It is assumed the application will be need coding from various other

software’s

� It is assumed that the client will provide an adequate connection to

the internet at the installation premises once the implementation

phase is reached and suitable testing have been performed.

� It is assumed that the client will supply and be responsible for physical

maintenance of a desktop computer to act as an application/ database

server for the solution once the implementation phase of the project is

reached.

� Project Team members will be committed 10 hours per week for 7

weeks of the project which equates to 70 hours over the entire

duration of the project

� Project has a number of dependencies such as the SRS document

cannot start until the completion of the PMP document.

� The tests documents cannot start until the prototype has commenced.

� The application cannot be delivered to the client until it is completed.

� The project has to be completed within 4 months and should come in under the

budget of $180,000. If the project faces a risk that could jeopardize the deadline

of 10months.

Risk Management

Throughout the project, procedures will need to be followed in relation

to risk management. If a new threat to the project arises, the team member

is required to follow these procedures. As this document is a ‘live’ document,

it is important that the process below is followed so that this document can

remain up-to-date.

Risk Management Procedures

In the event of a member discovering a new threat they must notify the PM

with the following details:

F Risk

A title that describes the risk.

F Description

A description of the risk explaining how it is a risk to the project.

F Probability (High/Medium/Low)

An estimation of the chance of this risk occurring.

High – This constitutes that the risk identified is very likely to happen and it

should be tracked very carefully

Medium – Constitutes that the risk has an average chance of occurring and it

should be tracked if suspicions are aroused.

Low – Means that the risk is unlikely to happen but nevertheless it must be

identified and watched for.

F Damage (High/Medium/Low)

Probability Matrix

Prepared By Dianne Kankas

Dated By: 16-05-2008

Potential Risk

1. Standard Application that are bring used.

2. Feasibility of the Project.

3. Availability of the resources at the proper time.

4. Will the Application for a period of time without

any major modification or Upgradation.

5. Affordability of the project.

6. Usage of Financial resources

7. Future Sustainability of the project.

8. Competency of the Team Members

9. Risk of Over Budget

10. Risk of non completion of the project.

High Probability Medium Low Low Medium High

Impact

10 9 3 7, 8 6 1,2,4,5

Risk Response Plan:

1. Standard Application that are bring used.

The Application used is compatible so there

won’t any problem occurring at this area. If

problems did occur then we have to choose

other similar technologies.

2. Feasibility of the Project

The project feasibility should be positive.

3. Availability of the resources at the proper

time.

Most of the resources like software are readily

available in the market and free to download. On

the other hand supplier of the hardware has to be

sought upon the quality of the product and detail

specifications of the product from various suppliers

to keep the option open.

4. Will the application for a period of time

without any major modification or

Upgradation.

Application is created with using latest

technologies however the I.T keeps blooming , if

there is any changes need to be made or

Upgradation it can be done in the future.

5. Affordability of the project.

The forecasting of the product shows positive

signs so it is affordable for the prospective.

6. Usage of Financial resources

Ongoing of the project will take some resources

from each of the departments to complete the

project efficiently.

7. Future Sustainability of the project.

The business will pay for itself with the

developed Application

Risk Register Risk register identifies the risk at the beginning and during the life of the project,

their grading in terms of likelihood of occurring and seriousness of impact on the

project, initial plans for mitigating each high level risk, and subsequent results.

8. Competency of the Team Members

Check on the background of each team before

the project Charter, regular meeting will provide

insight of the project and any of the team

member breaches the contract, the project

leader can replace that person with a new

member.

9. Risk of Over Budget

Regular meeting and the status report of the

project how the project is moving on and regular

checks will ensure the progress of the project

and cost analysis will tell us whether the project

is meeting the cost goals.

10. Risk of non completion of the project

Controlling the budget of the project will also

control the project over run time.

It usually includes:

� Unique identifier for each risk

� Description of each risk and how it will affect the project

� Assessment of the likelihood it will occur and the possible

seriousness/impact if it does occur (low, medium, high)

� Grading of each risk according to a risk assessment table

� Responsibility of managing the risk

� An outline of proposed mitigation actions (preventative and contingency).

Risk Identification

Risk register

Rating for likelihood and seriousness for each risk

L Rated as low E Rated as extreme (used for seriousness only)

M Rated as medium NA Not assessed

H Rated as high

Grade: Combined effect of likelihood/seriousness

Seriousness

low medium high EXTREME

low E D C A

medium D C B A Likelihood

high C B A A

Recommended actions for grades of risk

Grade Risk actions

A Actions to reduce the likelihood and seriousness to be identified and implemented as soon as the project commences.

B Actions to reduce the likelihood and seriousness to be identified and appropriate actions implemented during project execution.

C Actions to reduce the likelihood and seriousness to be identified and costed for possible action if funds permit.

D No action is needed unless grading increases over time.

E No action is needed unless grading increases over time.

Ref: Description of risk

Likelihood

Seriousness

Grade

Actions Responsible officer

1 Inadequate funding to complete the project

M M B Re-scope project, focusing on time and resourcing

Project Manager

2 Lack of technical skills in staff H H A Develop training plan Consultant

Adequate Use of financial resources

M H B Creating plan to segregate resource from each of the department to the project.

Project Manager

Over Time M H A Create an cost analysis Project Manager, Marketing Specialist, Business Analyst

Over Budget

H H A

Project Reports

In the Project report, each have there assigned role and responsibility which

each they have to prepare each week to what is the current status of the

project. It has to be submitted every Monday 4.30 p.m. The status report

has to be either handed over to the project manager or contact via email to

send in the status report. The report will include name, role and current job,

any issues they are facing and the percentage of work has been done...

Technical Process

Methods

The project will be using the prototype approach will be used for developing

the application.

Tools and Techniques

Document Management

Microsoft Word XP will be used for all documentation creation.

Project Development

In design phase of the project we will be using Microsoft Project

to create the Gantt charts. CASE diagrams will be created using Enterprise

Architect. We will also use security software to create a secure subscription

service for the user. The CASE Tools required for the project are Use-Case

diagrams, Sequence diagrams and Class Diagrams.

Communications:-

It is a set of channels which will be used to communications between the

team and the project manager. The project team will meet every Monday at

3.30 p.m. In the Monday meeting the will be set the schedule of the week

and the deliverables and the requirements that have to be met during the

week. If any problem arises the team will discuss about the issue and the

project manager decides how the project should be progressed. Outside the

meeting hours the team members will be able to communicate via email and

telephone.

5.0 Work Breakdown Structure

Task ID

Task Name Start Date Finish Date Predecess ors

1. Initializing Mon 14/05/08 Wed 16/05/08

2. Assign Project Manager Mon 14/05/08 Mon 14/05/08

3. Form Project Team Mon 14/05/08 Mon 14/05/08

4. Develop Project charter Tue 15/05/08 Wed 16/05/08 3

5. Planning Thu 17/05/08 Mon 21/05/08 1

6. Develop Standard Documentation Thu 17/05/08 Fri 18/05/08

7. Define user requirements Fri 18/05/08 Fri 18/05/08

8. Define Risks and risk management approaches

Fri 18/05/08 Mon 21/05/08 7

9. Design Tue 22/05/08 Wed 23/05/08

10. Research Similar Customize finance application

Tue 22/05/08 Tue 22/05/08

11. Develop design document Wed 23/05/08 Thu 24/05/08 6

12. Develop Thu 24/05/08 Mon 29/05/08

13. Develop Prototype Thu 24/05/08 Fri 25/05/08 14. Define Project Management Related

Deliverables

Fri 25/05/08 Fri 25/05/08

15. Create Project Management Plan Mon 28/05/08 Mon 28/05/08 6

16. Scope Statement Tue 29/05/08 Tue 29/05/08 6

17. Work Breakdown Structure Wed 30/05/08 Wed 30/05/08 6

18. Implementation Thu 31/05/08 Thu 31/05/08 19. Testing Thu 31/05/08 Fri 01/06/08 20. Develop a Test Plan Thu 31/05/08 Fri 01/06/08 21. Develop a Usability Test Plan Fri 01/06/08 Fri 01/06/08 6

22. Controlling Mon 14/05/08 Mon 04/06/08

23. Team Meeting Mon 14/05/08 Mon 04/06/08

24. Risk Management Plan Review & Update Mon 14/05/08 Mon 04/06/08

25. Control Changes Mon 14/05/08 Mon 04/05/08

26. Closing Mon 04/06/08 Thu 07/06/08 1,5,9,12

27. Final Project Report Mon 04/06/08 Mon 04/06/08

28. Present Final Application of Project Tue 05/06/08 Tue 05/06/08

29. Produce Lesson Learnt Document Wed 06/06/08 Wed 06/06/08

30. Project completed Thu 07/06/08 Thu 07/06/08 29

Summary of Project Deliverables:-

Project Management –

Related Deliverables:

� Project Charter

� Team Contract

� Scope Statement

� WBS ( Work Breakdown Structure)

� Gantt Chart

� Responsibility Matrix Diagram

� Risk Management Plan

� Milestone Report

� Change Request

� Lesson Learned

Project Success Criteria: - Our objective is to complete the application

within the duration which is 10 months for no more than $ 180,000. The

project provide various purpose like payroll, debtors, creditors, BAS calculation,

bank reconciliation, stock control, reports etc… We must also develop a method

for capturing the benefits in the application being developed, tested, and

altered. Even if the projects take little more in cost and time the project still

will be success as it helps out various developers do coding. It will benefit the

organizations

Schedule

6.1 Work Packages For more information relating to work packages refer to 3.2

Resource Requirement

In this Customized Finance Application there are 11 roles which have to be

equally delegated to each member of the team. Each member is requested to

have a desktop computer, a laptop for demonstration of the prototype. Each

laptop should have Microsoft Office for documentation, IDE and Microsoft

Project for creating a work breakdown structure and Gantt chart.

6.0 Schedule

Task ID Task Name Duration Start Date Finish Date

31. Initializing 3days Mon 14/05/08 Wed 16/05/08

32. Assign Project Manager 1day Mon 14/05/08 Mon 14/05/08

33. Form Project Team 1day Mon 14/05/08 Mon 14/05/08

34. Develop Project charter 1day Tue 15/05/08 Wed 16/05/08

35. Planning 2days Thu 17/05/08 Mon 21/05/08

36. Develop Standard Documentation 1day Thu 17/05/08 Fri 18/05/08

37. Define user requirements 1day Fri 18/05/08 Fri 18/05/08

38. Define Risks and risk management approaches

2days Fri 18/05/08 Mon 21/05/08

39. Design 3days Tue 22/05/08 Wed 23/05/08

40. Research Similar Customise finance application

1day Tue 22/05/08 Tue 22/05/08

41. Develop design document 2days Wed 23/05/08 Thu 24/05/08

42. Develop 6days Thu 24/05/08 Mon 29/05/08

43. Develop Prototype 2days Thu 24/05/08 Fri 25/05/08

44. Define Project Management Related 1day Fri 25/05/08 Fri 25/05/08

Deliverables

45. Create Project Management Plan 1day Mon 28/05/08 Mon 28/05/08

46. Scope Statement 1day Tue 29/05/08 Tue 29/05/08

47. Work Breakdown Structure 1day Wed 30/05/08 Wed 30/05/08

48. Implementation 1day Thu 31/05/08 Thu 31/05/08

49. Testing 2days Thu 31/05/08 Fri 01/06/08

50. Develop a Test Plan 2days Thu 31/05/08 Fri 01/06/08

51. Develop a Usability Test Plan 1day Fri 01/06/08 Fri 01/06/08

52. Controlling 16days Mon 14/05/08 Mon 04/06/08

53. Team Meeting 16days Mon 14/05/08 Mon 04/06/08

54. Risk Management Plan Review & Update 16days Mon 14/05/08 Mon 04/06/08

55. Control Changes 16days Mon 14/05/08 Mon 04/05/08

56. Closing 4days Mon 04/06/08 Thu 07/06/08

57. Final Project Report 1day Mon 04/06/08 Mon 04/06/08

58. Present Final Application of Project 1day Tue 05/06/08 Tue 05/06/08

59. Produce Lesson Learnt Document 1d Wed 06/06/08 Wed 06/06/08

60. Project completed 1d Thu 07/06/08 Thu 07/06/08

7.0 Budget

Any expenses encountered by the project team will be divided between the

team members. This project is not expecting large costs however small costs

(such as printing and binding) are to be expected. Any team member that

spends money on the project should keep the receipt and give it to the PM at

the next meeting. The PM will keep a tab of all costs incurred by each

member and at the end of each semester will add up all costs of the team.

Each member will pay or be reimbursed accordingly, with a goal of each

team member paying an equal amount.

Detail Budget

Total Budget Summary Cost Management Total Cost

Wages $128,480.00

Software $3563.00

Hardware $5630.00

Office Supplies $2450.00

Other $1000.00

Total Cost $178,000.00

6.3.1.2Resource Sheet

Project Roles Number of Employees

Days Working (9am – 5pm)

Hourly Rate Total Duration

Project manager 1 120 days $ 130/hour $81,600.00

Programmer 1 100 days $ 77/hour $48,000.00

System Analyst 1 25 days $ 82/hour $13,000.00

Business Analyst 1 10 days $ 87/hour $5600.00

Research Specialists 1 10 days $ 102/hour $6800.00

Testers 2 40 days $ 72/hour $35,200.00

Documenters 1 12 days $ 74/hour $4800.00

Purchasing Specialist 1 5 days $ 82/hour $2600.00

Marketing Specialist 1 12days $ 102/hour $8160.00

Consultant 1 4 days $102 /hour $2720.00

Total Cost 78000.00

*Assumed that working hours from 9 a.m to 5 p.m

* Assumed all products purchased in Australian Dollars

Software Name Quantity Total

Windows XP Professional 4 $1,912.00

Microsoft XP office 4 $1152.00

Microsoft Project 4 ----------

Microsoft excel 1 $499.00

Java Standard 1 ------

Total Cost

Hardware Budget:

Software Name Quantity Total

Windows XP Professional 4 $1,912.00

Microsoft XP office 4 $1152.00

Microsoft Project 4 ----------

Microsoft Excel 1 $499.00

Java Standard 1 ------

Total Cost $3,563.00

Software Name Quantity Total

Windows XP Professional 4 $1,912.00

Microsoft XP office 4 $1152.00

Microsoft Project 4 ----------

Microsoft Excel 1 $499.00

Java Standard 1 ------

Total Cost $3,563.00

Hardware Name

Quantity

Total Item Cost

Dell OptiPlex 4 $4632.00

Dell Inspiron 1300 1 $998.00

Total Cost $5630.00

Supplies Budget Materials and Supplies

Total Item Cost

General office supplies $400.00

Photocopying $1000.00

Printing $1000.00

Blank CDs $50.00

Total Cost S2,450.00

Other Budget Other items Total Item costs

Deliveries $1000.00

Total Cost $1000.00

Conclusion:- The Project Management Plan gives an idea what the

project is about and what is on the process for a completion of a project. The

Scope pf the project is mad with assumptions creates the project plan. Even

if there is a slight change in the assumptions and the project deliverables will

change drastically. The creation of Customized financial application with the

secure subscription is to be created in the project. The over all budget for the

creation of customize finance application was $ 180,000.00, the figures

where quite under the budget. Even though the project is under budget the

project will be successful with the help of well assessed cope statement

defining the client needs.

Change Request Form

Change Request Form Project Name: Date Request Submitted: Submitted by: (name and contact information) Change Category: � Scope � Schedule � Cost � Technology � Other Description of change requested: Events that made this change necessary or desirable: Justification : Impact of the proposed change on: Scope: Schedule: Cost: Staffing: Risk: Other: Suggested implementation if the change request is approved: Required approvals:

Name/Title Date Approve/Reject

Gantt chart

Bibliography :

Project Smart. (2007). Project Management Success with Top 7 Best Practices. Retrieved

April15th, 2008, from

http://www.projectsmart.co.uk/project_management_success.html

Method123. (2003). Project Management Life Cycle Methodology. Retrieved April 15,

2008, from

http://www.method123.com/project-lifecycle.php

Berkun, Scott (2005). Art of Project Management. Cambridge, MA: O'Reilly Media.

Brooks, Fred (1995). The Mythical Man-Month, 20th Anniversary Edition, Adison

Wesley. I

Comninos D &, Frigenti E (2002). The Practice of Project Management - a guide to the

business-focused approach. Kogan Page.

Heerkens, Gary (2001). Project Management (The Briefcase Book Series). McGraw-Hill.

Kerzner, Harold (2003). Project Management: A Systems Approach to Planning,

Scheduling, and Controlling, 8th Ed., Wiley.

Lewis, James (2002). Fundamentals of Project Management, 2nd ed., American

Management Association.

Meredith, Jack R. and Mantel, Samuel J. (2002). Project Management: A Managerial

Approach, 5th ed., Wiley.