Académique Documents
Professionnel Documents
Culture Documents
YEAR 1, SEMESTER 1
30 Sept 2013- 24 Feb 2014
Dr Leang Khim 23/02/2014
CONTENTS
I. Project Initiation II. Project Planning III. Project Execution IV.Project Closure
9. Poorly defined requirements 10. Scope creep 11. Stakeholders have different expectations 12. Stakeholders have unrealistic expectations 13. There is no real need or demand for the product 14. There is a lack of user involvement in the project 15. Change management is lacking or ineffective
I. Project Initiation
I. Project Initiation
Develop a case Undertake a feasibility study
Start
Appoint a project team Perform phase review
I. Project Initiation
Develop a case is created to define the problem or opportunity
in detail and identify a preferred solution for implementation. A detailed description of the problem or opportunity; A list of the alternative solutions available; An analysis of a business benefits, cost, risks, and issues; A description of the preferred solutions; A summarized plan for implementation.
I. Project Initiation
Feasibility study is to:
Assesses the likelihood of each alternative solution option Investigate if the forecast costs are reasonable Find out if the solution, risks and issues are achievable, acceptable and avoidable, respectively.
I. Project Initiation
Terms of reference (TOR) a document that outlines the purpose
of the project, the manner in which the project will be structured and how it will be implemented. It defines: The vision, objectives, scope, and deliverable for the project. Organization structure, activities, resources, funding required to undertake the project.
I. Project Initiation
Terms of reference may include:
1. The vision, objectives, scope and deliverables (that is what the project will actually produce). 2. Stakeholders, authority, roles and responsibilities (that is, who will take part in it) 3. Resource, financial (costs and budgets) and quality plans (that is, how it will be achieved)
I. Project Initiation
Terms of reference may include:
4. Work breakdown structure and schedule (that is, when it will be achieved) 5. Identification of the customer 6. Major assumptions and constraints 7. Key risk areas 8. Project approach or strategy used
I. Project Initiation
Project team
Appointment of Project Manager Job description Financial and accounting systems, etc.
Project office
Office furniture Communication infrastructure Financial and accounting systems, etc.
Description
Milestone date
DD/MM/YY A quality plan has been documented and approved by the project sponsor. It identifies the quality assurance and quality control techniques required to ensure and control the quality of all project deliverables and processes. A formal tender process is undertaken to identify a short-list of capable suppliers and select a preferred supplier. The tender process involves creating a statement of work, a request for information...... DD/MM/YY
Responsibility
Delivering the approved solution to meet the full requirements of the customer Executing activities to accomplish the project objectives
Skills
Stat date
End date
DD/MM/YY
Supervisor
DD/MM/YY
Recruit skilled We will recruit skilled staff to assure deliverable quality by: staff o Ensuring staff having at least 3 year experience in finance and accounting in similar projects. o Appointing 2 technical consultants to ensure that the technology deliverables of this project meet the quality standards.
Undertake We will review the quality of deliverable by: Monthly quality review o Appointing an independence resource to perform monthly quality review.
Risk description
The requirement have not been clearly specified The requirements specified do not match the customers need. The business benefits have not been identified The final solution delivered does not achieve the required benefits The project exceeds the budget allocated There is unaccounted expenditure on the project The deliverables required by the project are not clearly defined. The deliverable produced does not meet the quality criteria defined.
Risk ID
1.1 1.2 2.1 2.2 3.1 3.2 4.1 4.2
Benefits
Budget Deliverables
Score
100 80 60 40 20
Description
Highly likely to occur Very likely to occur, based on the circumstances of the project Likely to occur. Unlikely to occur. However needs to be monitored.. Highly unlikely to occur based on current information.
Acceptance milestones
Milestone
Name Financial system upgraded Description Implement the software package on new hardware
Deliverable
Name Software package installed Description Implement General Ledger (GL), Accounts Payable (AP) and Accounts Receivable (AR) software
Standards
System functionality GL operational with no errors. AP operational with no errors. AR operational with no errors. System performance 99.9% system uptime <1 second response times 100% data accuracy
Project board (chaired by the project sponsor) decides whether to cancel or undertake further work or grant approval to begin the next phase
Build deliverables
Benefits
Y?N
Deliverables
DD/MM/YYYY