...for a Project Charter document, as described in the PMI Project Management Body of Knowledge (PMBOK® Guide, Third Edition). This template provides suggestions designed to prompt the Project Manager and help in the creation of the Project Charter document. The information for the Project Charter is located on pages 81-86, of “A Guide to the Project Management Body of Knowledge” (PMBOK® Guide), Third Edition. Deleting the [....] text When the template is complete, the Project Charter document can be printed and approved. Prior to printing, you should delete all [....] prompt text (in italics and blue text). Saving the Project Charter document under its own name Save the Project Charter document by selecting the “SAVE-AS” command; this will avoid overwriting this template. Remember to specify your own Project Directory. Once your Project Charter document is completed check the document against the following Quality Criteria: • Is the level of authority of the Project Sponsor commensurate with the anticipated size, risk and cost of the project? • Is there sufficient detail to allow the appointment of an appropriate Project Manager? • Have the project budgets received preliminary review and approval from the executive management team? • Are all the known stakeholders identified? • Does the Project Charter describe the “project success criteria”? NOTE: Remember to delete this page of instructions from your final document. ...
Words: 1410 - Pages: 6
...To: Audit Senior From: Sara Smith Date: 09/14/2014 RE: Testing the NRV of Inventory The focus of this audit is to determine the appropriateness of company XYZ’s inventory on hand. By doing so, the audit will focus on testing the net realizable value of inventories on hand as of December 31,2007 using IDEA. The assertions tested in evaluating the net realizable value of inventory include the following, valuation, rights & obligations, completeness and existence. But, due to the limited amount of information provided by the client, only the valuation assertion will be tested using IDEA. When testing the NRV of inventory, first one should obtain the following files from the client, the inventory final 2007, Sales 2007, Sales 2008, and the Sale pricing master file 2007. It is imperative to obtain these files so that one can match certain files to each other and extract data. The next step is to review unique and unusual items in the different source files. For example, its is crucial for one to understand the data being tested before importing it into IDEA. Therefore, in order to understand the data one should scan and review the files for unusual items. Then one should analyze the source files and compute the net realizable value in IDEA. Once the various source files have been matched, the following question should be considered, are there items with no recent sales?, are there items with quantities in excess of sales activities?, are there items that were sold doing...
Words: 2931 - Pages: 12
...[pic] Project Plan Template Document Control Document Information |© |Information | |Document Id |[Document Management System #] | |Document Owner |[Owner Name] | |Issue Date |[Date] | |Last Saved Date |[Date] | |File Name |[Name] | Document History |Version |Issue Date |Changes | |[1.0] |[Date] |[Section, Page(s) and Text Revised] | | | | | | | | | | | ...
Words: 1186 - Pages: 5
...Project Charter Document Project Name: Department: Focus Area: Product/Process: Prepared By Document Owner(s) | Project/Organization Role | | | | | | | Project Charter Version Control Version | Date | Author | Change Description | | | [Replace this text with the name of the Document Owner.] | Document created | | | [Replace this text with the name of the Change Owner.] | [Replace this text with a list of changes for this Owner on this Date and Version.] * [Change 1] * [Change 2] * [Change n] | TABLE OF CONTENTS 1 PROJECT CHARTER PURPOSE 3 2 PROJECT EXECUTIVE SUMMARY 3 3 PROJECT OVERVIEW 3 4 PROJECT SCOPE 3 4.1 Goals and Objectives 3 4.2 Departmental Statements of Work (SOW) 3 4.3 Organizational Impacts 3 4.4 Project Deliverables 3 4.5 Deliverables Out of Scope 3 4.6 Project Estimated Costs & Duration 3 5 PROJECT CONDITIONS 3 5.1 Project Assumptions 3 5.2 Project Issues 3 5.3 Project Risks 3 5.4 Project Constraints 3 6 Project Structure Approach 3 7 Project Team Organization Plans 3 8 PROJECT REFERENCES 3 9 APPROVALS 3 10 APPENDICES 3 10.1 Document Guidelines 3 10.2 Project Charter Document Sections Omitted 3 PROJECT CHARTER PURPOSE [Replace the following text with your own statement of the Project Charter Purpose, or use the provided sample text.] The project charter defines the scope, objectives, and overall approach for the work to be completed. It is a critical element for...
Words: 784 - Pages: 4
...com Phone: 0904324282 2/ Tran Thi Thu Trang (M.A) Email: trang.tranthithu@gmail.com Phone: 0989886107 3/ Nguyen Bich Ngoc (PhD. Fellow) Email: bichngoc159@gmail.com Phone: 0919956929 CLASS HOURS: | 1-3, Monday, D2-203 | OFFICE: | Building 7, Room 307 & 310 | OFFICE HOURS: | Appointments are usually available | ------------------------------------------------- | | Course Description: This course is designed for International Business Management major who will ultimately be engaged in doing business internationally. In this course, students will learn the basis of writing business letters and the purpose of writing a business letter; draft a plan for the letter; write the letter; and edit the letter to ensure it fulfills your purpose. Particularly, an introduction to international business letter with some typical correspondence such as Enquiries, Replies and Quotations, Orders, Complaints and Adjustments will be delivered to the students. The course aims to document international standard banking practice for examination of commercial documents under the UCP 600, including a general overview of import – export, commercial documents, the principles of the UCP 600, the international standard banking practice to examine these documents according to the UCP 600. The class also will discuss and review a few case studies that epitomize the issues involved in preparing documents for presentation and examining documents for honor in doing business...
Words: 987 - Pages: 4
...[pic] Project Charter Document [pic] Project Name: Department: Focus Area: Product/Process: [pic] Prepared By |Document Owner(s) |Project/Organization Role | | | | | | | | | | Project Charter Version Control |Version |Date |Author |Change Description | | | |[Replace this text with the |Document created | | | |name of the Document Owner.] | | | | |[Replace this text with the |[Replace this text with a list of changes for this Owner on | | | |name of the Change Owner.] |this Date and Version.] | | | | |[Change 1] | | ...
Words: 785 - Pages: 4
...CIS 517 WK 6 CASE STUDY 2 To purchase this visit here: http://www.activitymode.com/product/cis-517-wk-6-case-study-2/ Contact us at: SUPPORT@ACTIVITYMODE.COM CIS 517 WK 6 CASE STUDY 2 CIS 517 WK 6 Case Study 2 - Green Computing Research Project – Part 2 Read the Green Computing Research Project, Part 2 in Appendix C. Document the requirements and develop a scope statement. Write a two to three (2-3) page paper in which you: 1. Document the requirements based on the information provided and assumptions that you have made, including a requirements traceability matrix. 2. Include a list of questions to ask the sponsor about the project scope. Include at least six (6) questions for full credit. 3. Develop a scope statement for the project. More Details Included... Activity mode aims to provide quality study notes and tutorials to the students of CIS 517 WK 6 Case Study 2 in order to ace their studies. CIS 517 WK 6 CASE STUDY 2 To purchase this visit here: http://www.activitymode.com/product/cis-517-wk-6-case-study-2/ Contact us at: SUPPORT@ACTIVITYMODE.COM CIS 517 WK 6 CASE STUDY 2 CIS 517 WK 6 Case Study 2 - Green Computing Research Project – Part 2 Read the Green Computing Research Project, Part 2 in Appendix C. Document the requirements and develop a scope statement. Write a two to three (2-3) page paper in which you: 1. Document the requirements based on the information provided and assumptions that you have made, including a requirements traceability...
Words: 649 - Pages: 3
...GenRays Matrix Template Project Management Knowledge Areas Recommended Tool(s) Project Charter, Facilitation Technique Project Integration Management Interviews, Product Analysis Project Scope Management Justification for Tool The project charter will be used for this knowledge management area because it defines the HRIS projects purpose, objectives, requirements, risks, and budget, which is important for this top-down, overall view of the project. The Facilitation Technique will also be used because it not only facilitates the development of the project charter, but will help the project team members accomplish their tasks through brainstorming, problem solving, meeting management, and conflict resolution. Interviews with GenRays senior leaders, department heads, and staff will be used for this knowledge management area to determine what the most beneficial aspects of an HRIS system are to the company. The results of the interviews will be used to help identify and define the features and functions of the project’s deliverables. Product Analysis will also be used to help determine which vendor’s pre-packaged HRIS system best meets the company’s needs, by analyzing the HRIS requirements, the product breakdown, the systems required, and the value of the product, and comparing to the offerings and information provided by the potential vendors that have already been identified. Decomposition, Expert Judgment, Gantt Chart Decomposition will be used for Project Time Management in...
Words: 14782 - Pages: 60
...[pic] Project Plan For [Project Name] Document Control Document Information |© |Information | |Document Id |[Document Management System #] | |Document Owner |[Owner Name] | |Issue Date |[Date] | |Last Saved Date |[Date] | |File Name |[Name] | Document History |Version |Issue Date |Changes | |[1.0] |[Date] |[Section, Page(s) and Text Revised] | | | | | | | | | | ...
Words: 1170 - Pages: 5
...Project Charter Document Project Name: Department: Focus Area: Product/Process: Prepared By Document Owner(s) | Project/Organization Role | | | | | | | Project Charter Version Control Version | Date | Author | Change Description | | | [Replace this text with the name of the Document Owner.] | Document created | | | [Replace this text with the name of the Change Owner.] | [Replace this text with a list of changes for this Owner on this Date and Version.] * [Change 1] * [Change 2] * [Change n] | TABLE OF CONTENTS 1 PROJECT CHARTER PURPOSE 3 2 PROJECT EXECUTIVE SUMMARY 3 3 PROJECT OVERVIEW 3 4 PROJECT SCOPE 3 4.1 Goals and Objectives 3 4.2 Departmental Statements of Work (SOW) 3 4.3 Organizational Impacts 3 4.4 Project Deliverables 3 4.5 Deliverables Out of Scope 3 4.6 Project Estimated Costs & Duration 3 5 PROJECT CONDITIONS 3 5.1 Project Assumptions 3 5.2 Project Issues 3 5.3 Project Risks 3 5.4 Project Constraints 3 6 Project Structure Approach 3 7 Project Team Organization Plans 3 8 PROJECT REFERENCES 3 9 APPROVALS 3 10 APPENDICES 3 10.1 Document Guidelines 3 10.2 Project Charter Document Sections Omitted 3 PROJECT CHARTER PURPOSE [Replace the following text with your own statement of the Project Charter Purpose, or use the provided sample text.] The project charter defines the scope, objectives, and overall approach for the work to be completed. It is a critical element for...
Words: 784 - Pages: 4
...DOCUMENT TEMPLATES FOR STUDENT PROJECTS IN SOFTWARE ENGINEERING Declan Delaney and Stephen Brown Department of Computer Science, National University of Ireland, Maynooth Date: August 2002 Technical Report: NUIM-CS-TR2002-05 Abstract This technical report outlines the contents of a minimal set of software development documents, tailored for use by students in software engineering projects, and firmly based on IEEE standards. The document set is designed to support software development activities. It provides a framework for use in undergraduate software engineering projects, both individual and team-based, that helps students to learn best practice. A supplementary report describes the content of each document in more detail. 1. Background. Projects form an important part of the education of software engineers. They form an active method of teaching, as defined by Piaget, leading to a "training in self-discipline and voluntary effort" [1], which is important to software engineering professionals. Two purposes served by these projects are: education in professional practice, and outcomes-based assessment, as identified in the ACM/IEEE Computing Curricula 2001 [2]. An infrastructure must be provided whereby the students are well guided in their learning, yet have an opportunity to display their individual achievements for the purposes of assessment. This corresponds to the ‘ integrational’ and ‘ differential’ modes of education as described by Cook in ...
Words: 1741 - Pages: 7
...______________________________________________________________________________ Project Name NSA Capstone Project Charter ______________________________________________________________________________ Prepared By: [insert name] Date of Publication: [insert date] Revision History Version | Date | Author(s) | Revision Notes | 1.0 | | (Original author) | (original document) | | | | | | | | | | | | | | | | | Table of Contents Project Description 3 Project Objectives 3 Project Scope 4 In Scope: 4 Out of Scope: 4 Deliverables Produced: 4 Stakeholders: 5 Requirements: 5 Acceptance Criteria:Project Estimated Effort/Cost/Duration 5 Estimated Cost: 6 Estimated Effort Hours: 6 Estimated Duration: 6 Project Assumptions 7 Project Risks 7 Project Constraints 8 Project Dependencies 8 Project Approach 8 Project Organization 9 Communication Plan: 9 Project Guidelines: 9 Project Approvals 10 Project Description * On a large scale, summarize the case scenario or business case. Be specific in the background and why this project is necessary for the overall business value of the company * (Remove this comment section from the final document.) Project Objectives Objectives are statements that describe what this project will achieve and deliver. Objectives may be written using a technique called “SMART”: Specific, Measurable, Achievable, Realistic, and Timebound. To...
Words: 1740 - Pages: 7
...AIPM Website Membership Engagement Project Plan AIPM Website Membership Engagement Project Plan Approvals Name, Project Role & Position Project Manager Sponsor Senior User Representative CEO & Senior Supplier Document Role Date Signature Recommender Approver Approver Reviewer Document administration Development history Version Date Description Created by 0.1 13/02/2014 First Draft – Dissemination to Project Sponsor for review John Walker 0.2 15/02/2014 Second Draft – Inclusion of Business Case David Bryant 0.3 20/02/2014 Third Draft – Update from Margie’s feedback Lee Edmondson 1.0 24/02/2014 First release, reviewed and approved John Walker Contributors The following people provided information and / or were interviewed while preparing this document: Contributor Position & organisation John Walker Project Manager David Bryant Project Sponsor Nicole Walker AIPM Membership Development Manager Linda Chiarella AIPM National Events Manager Lee Edmondson AIPM Communications Manager Margie O’Tarpey AIPM CEO & Senior Supplier Kayleen Lenzo AIPM Finance and Operations Manager Document distribution history The following describes the distribution history of the document: Version Date Distribution recipients 0.1 13/02/2014 Sponsor 0.2 15/02/2014 Project Manager 0.2 15/02/2014 AIPM CEO & Senior Supplier 0.3 ...
Words: 8451 - Pages: 34
...Contents Introduction 2 The Project Office: Configuration Management Plan 3 Section 1: Introduction 3 Purpose 3 Project Framework 3 Section 2: Configuration Identification 4 Configuration Items 4 Baseline Documents produced in a typical project 4 Naming Convention for Project Documentation 5 Document Format 5 Section 3: Configuration Organisation 6 Section 4 Configuration Management Phasing and Milestones 8 Section 5: Data Management 8 Section 6: Change Control 9 Change Control Process 9 Change Control Board 10 Change Manager 10 Duties of a CCB Member 11 Change categorization 11 CAB meetings 12 Section 7: Interface Management 13 Section 8: Configuration Status Accounting 13 Status Account Data 13 Configuration Management Database 13 Section 9: Verification 13 CM Process Audits 13 CM Baseline Audit 13 Section 10: Reference Documents 14 Introduction The South African Post Office (SAPO) is constantly under pressure to reduce cost whilst improving its profit margin through innovative products and effective service delivery. SAPO is a multifaceted organisation which operates in various industries e.g. Logistics, IT and Cash Collection etc. Hence SAPO, at any given moment in time, has a large number of projects that are in various stages of execution. These projects consume a large amount of capital resources as well as human resources. In an attempt to reduce the risk of unexpected costs and project cancellations, improve...
Words: 3446 - Pages: 14
...Template for IDA Project (Project Id) Template for specific development (Contract Id) Technical Design Document Issue 1 TABLE OF CONTENTS 0 Preface 1 0.1 PURPOSE OF THIS DOCUMENT 1 0.2 Use of this document 1 0.3 Overview 2 0.4 Basis of this Document 2 0.5 A Reference Architecture for the IDA Programme 3 0.6 Specific Design Considerations 3 1 Introduction 5 1.1 PURPOSE 5 1.2 Scope 5 1.3 Definitions, Acronyms and Abbreviations 5 1.4 References 6 1.5 Overview 6 2 System Overview 7 2.1 SYSTEM CHARACTERISTICS 7 2.2 System Architecture 7 2.3 Infrastructure Services 9 3 System Context 10 4 SYSTEM DESIGN 11 4.1 DESIGN METHOD AND STANDARDS 11 4.2 Documentation Standards 12 4.3 Naming conventions 13 4.4 Programming Standards 13 4.5 Software development tools 13 4.6 Outstanding Issues 14 4.7 Decomposition Description 14 5 Component Description 15 5.1 COMPONENT IDENTIFIER 16 6 Software Requirements Traceability Matrix 19 DOCUMENT CONTROL 20 DOCUMENT SIGNOFF 20 DOCUMENT CHANGE RECORD 20 0 PREFACE 0.1 PURPOSE OF THIS DOCUMENT 1. THIS DOCUMENT IS A GENERIC TECHNICAL DESIGN DOCUMENT DOCUMENT FOR USE BY IDA PROJECTS. IT PROVIDES GUIDANCE AND TEMPLATE MATERIAL WHICH IS INTENDED TO ASSIST THE RELEVANT MANAGEMENT OR TECHNICAL STAFF, WHETHER CLIENT OR SUPPLIER, IN PRODUCING A PROJECT-SPECIFIC TECHNICAL DESIGN DOCUMENT DOCUMENT. IT IS ALSO USEFUL BACKGROUND READING FOR ANYONE INVOLVED IN DEVELOPING OR MONITORING...
Words: 6668 - Pages: 27
