(Mt) – CU Earned Value Analysis Report Project

SOLUTION AT Academic Writers Bay

NearlyFree.com IT Governance The following is an excerpt from the NearlyFree.com IT Governance. Below you will find the IT policies for the Service Oriented Architecture and Enterprise, which is the basic framework and structure for all IT-related activities and customer and user interactions at NearlyFree.com. The philosophy here is service centered on customer satisfaction and quality. IT Governance Overview Governance policies provide guidelines to manage all IT programs and projects. Governance establishes clear roles, responsibilities, and accountabilities for all project team members including executive leadership and project managers. Industry best practices include the use of a governance process to oversee and manage project spending and to ensure there is an acceptable benefit or return on investment in all initiatives. The key to the NearlyFree.com IT governance is the creation of the IT Program Management Office (PMO). The PMO seeks to understand and integrate organizational business goals with all approved project definitions and objectives. The PMO has a set definition and objectives, which set the scope and boundaries to deliver project management methodologies, guidelines, training, and investment benefits. IT Service Oriented Governance Policies The following types of policies apply to all service-oriented IT projects. 1. Project life cycle (design, development, and implementation) policies. 2. Quality management policies. 3. Configuration and change management policies. All projects will have to adopt the project management office (PMO) quality management plan and policies. Project change requests must go through the process and gain approval of the change control board (CCB). Amendment History – Document Status (Release #7, 2008) Document Version # Approval Date Modified By Section, Page(s)and Text Revised 7.0 2/1/08 HGM Governance overview 7.1 2/7/08 HGM PMO definition update 1 PMO Quality Management Discipline and Policies Introduction The project management office (PMO) upholds the IT service-oriented architecture and enterprise, which is the basic framework and structure for all IT-related activities and projects. The philosophy is service, centered on customer satisfaction and quality. The PMO provides training and the quality management discipline to plan and control through testing and continuous improvement to ensure that each project satisfies the needs for which it was undertaken (PMBOK® measure of quality). The scope of quality management includes the following: • Quality planning. • Quality control. • Quality assurance. These quality elements interact with each other and with each of the project management disciplines. Concept Map of PMO Quality Management Tools and Techniques (Project Management Institute, 2004) TOOLS and TECHNIQUES *Benefit/Cost Analysis *Benchmarking *Flowcharting *Design of Experiments *Cost of Quality INPUTS OUTPUTS *Quality Policy *Quality Management Plan *Scope Statement *Product Description *Standards and Regulations *Other process outputs Quality Planning *Operational Definitions *Checklists *Inputs to other processes 2 Benefits The project management office: • • • • • Identifies the requirements that will satisfy the needs of the project. Identifies which quality standards are relevant to the project such as ISO 9001:2000 and CMMI. Measures and monitors specific project outputs to determine if they comply with relevant project quality metrics and standards and comply within the variance thresholds. Tests, evaluates, and validates all project outputs and overall project performance. Documents quality management strategies and measurements that can be collected, reviewed, and archived for reference in future projects. Guidelines and Procedures Step Action Responsible personnel 1 Review project scope and deliverable specifications. PM 2 Assemble organization quality policies, standards, and regulations. PM 3 Describe process using inputs and outputs in particular team disciplines (tools and techniques). PM and project team 4 Analyze outputs from steps 1, 2, and 3 and create a list of operational definition of quality. PM and project team 5 Compile items in a list and sort into logical groupings. PM and project team 6 Create the checklist that various project team members can use to inspect quality. PM and project team 7 Develop a quality statement on how quality management and quality plan will be implemented. PM and project team 8 Develop a quality control procedure on how to examine specific project results to see if they comply with the quality standards and to identify means to eliminate any error or unsatisfactory results. Quality audit team 9 Establish quality assurance by evaluating project performance on a regular basis to provide confidence that the project will satisfy the quality standards previously set. Quality audit team 3 Quality Assurance Template Quality Assurance Plan for [Project Name] Prepared by: Date: 1.0 Draft quality assurance plan. 1.1 Introduction. 1.2 Purpose. 1.3 Policy statement. 1.4 Scope. 2.0 Management. 2.1 Organizational structure. 2.2 Roles and responsibilities. 2.2.1 Technical monitor/senior management. 2.2.2 Task leader. 2.2.3 Quality assurance team. 2.2.3 Technical staff. 3.0 Required documentation. 4.0 Quality assurance procedures. 4.1 Walkthrough procedure. 4.2 Review process. 4.2.1 Review procedures. 4.3 Audit process. 4.3.1 Audit procedures. 4.4 Evaluation process. 4.5 Process improvement. 5.0 Problem reporting procedures. 5.1 Noncompliance reporting procedures. 6.0 Quality assurance metrics. Appendix. Quality assurance check list forms. 4 Configuration and Change Management Policies All projects will have to adopt the project management office (PMO) change control system process and procedures. Project change requests go through the process and approval of the change control board (CCB). PMO’s change control system is a formal process with documented procedures that defines how a project Scope Statement (original, defined, and signed by project sponsors) must be maintained when the need for changes occur. The process includes steps by which the official Project Scope Statement document may be changed. The process also includes all electronic/paperwork tracking systems, processes, and approval levels necessary for authorizing changes. Concept Map of PMO Change Control Tools and Techniques (Project Management Institute, 2004) TOOLS and TECHNIQUES *Scope Change Control *Performance Measurement *Additional Planning INPUTS OUTPUTS *WBS *Performance Reports *Change Requests *Scope Management Plan Scope Change Control *Scope Changes *Corrective Action *Lessons Learned *Adjusted Baseline Completing a change-request form template is a requirement for this process. User (Change) requests are submitted to the change control board (CCB) for approval. 5 Change Request Form Template Project Name: Date Request Submitted: Title of Change Request Change Order Number: 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 for the change/why it is needed/desired to continue/complete the project: 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 References Project Management Institute. (2004). A guide to the project management book of knowledge (3rd ed.). Newtown Square, PA: Author. Schwalbe, K. (2007). Information technology project management (5th ed.). Boston: Thomson. 6 Project Charter Project Title: New Employee Orientation Project Start Date: 10/09/2007 Projected Finish Date: 01/22/2008 Budget Information: $25,000.00 Project Manager: Jeremy Lee [email protected] ext 8000 Project Objectives To build an employee orientation learning module for the Human Resource department. It will be accessed through the company Intranet. This module will include at least one quiz and a signoff to document that new employees have completed their orientation and understood the training information. Approach The following is a list of milestones which represent success on this project • Kickoff meeting. • Requirements and Project Planning. • Design and Development. • Testing. • User Testing. • Stakeholder testing and presentation. • Design changes based upon testing information. • Final Integration Testing. • Roll out. • Project Close. Roles and Responsibilities Role Name Organization / Position Contact Information Project sponsor Jennifer Beal Project Sponsor E-mail: [email protected] Phone: X8999 Project manager Jeremy Lee Project Manager E-mail: [email protected] Phone: X8000 Team resource Alice Yee Software Specialist E-mail: [email protected] Phone: X8888 Page 1 of 2 Team resource Tom Johansen Webmaster E-mail: [email protected] Phone: X8777 Team resource John Sachs QA Administrator E-mail: [email protected] Phone: X8666 Cheryl Gladstone HR Manager E-mail: [email protected] Phone: X8555 Sign-off: The stakeholders initialed their names in table above. Comments: None. Page 2 of 2 Quality Statement To: Jennifer Beal, Alice Yee, Cheryl Gladstone, John Sachs, and Tom Johansen From: Jeremy Lee Re: NearlyFree.com NEO Project Quality Statement PMO Quality Management Discipline and Policies The PMO upholds the IT Service Oriented Architecture and Enterprise which is the basic framework and structure for all IT-related activities and projects. The philosophy is service, centered on customer satisfaction and quality. NEO Project will implement and abide by the PMO Quality Policies. Quality Policies will be implemented from the planning phase and throughout the different project phases to project close. Ensuring Process Quality Attention will be given to detailed documentation of the development process. Program code test and review meetings will be scheduled regularly to make the processes flow run smoothly and eliminate any misunderstandings from the team. Exit phase meetings will be scheduled for documentations and lessons learned for future use. Internal audits will be performed regularly. These are done not only for IT processes, but also for Finance and Human Resources as well. Quality Control Testing Techniques • • • Expert Review Inspections Audits Testing Cycles • • • • Unit testing Integration testing System testing User acceptance testing Conclusion Page 1 of 2 NEO Project will comply with the PMO quality policies and guidelines. The Project Manager will make sure all the project team and all resources are in compliance with these strict policies and guidelines. Jeremy Lee Signed by PM Page 2 of 2 Project Scope Statement Version History 1.01.0 10/25/2007 Project Name: Project NEO Prepared by: Jeremy Lee Date (MM/DD/YYYY): 10/25/2007 approved Project Scope Executive Summary The Scope of this project is to design an employee orientation module as requested by the Human Resource department to be used for new employee orientation. The information needs to be accessed through the company Intranet where new employees would review all company policies, take a quiz, and sign off on the new employee orientation process. The scope also includes successful testing and acceptance by the Human Resource department. Business Objectives 2.1 Product Description (Solution) A NearlyFree.com New Employee Orientation Module for the Human Resource department will be designed that can be accessed using the company Intranet for new employee orientations. During the orientation process, new employees will review the presentation presented by Human Resources followed by a quiz and sign off the orientation process. 2.2 Business Objectives The Human Resource department would like to automate the new employee orientation process by providing electronic documentation for orientation presentations, and maintain this database to track and document successfully completed orientations. Project Description Project Scope 3.1 Project Scope Includes (list Deliverables): • Design a web based Human Resource module for new employee orientations. • Integrate HR module with the company Intranet. Page 1 of 5 • • • • • Migrate existing hard copy presentations into electronic format. Create quiz to assess new employees on their understanding of HR processes. Create electronic sign-off for a successfully completed orientation. Create online help to assist new employees during the orientation process. Provide documentation to the Human Resource department to help with future changes to the orientation material. Does Not Include The scope of this project does not include anything that is not maintaining the website 3.2 External Dependencies All project requirements including the hard copy documents of the orientation material to be promptly provided by Cheryl Gladstone. 3.3 Assumptions All necessary hardware and software is already in place. The NearlyFree.com Employee Orientation module will be created and integrated into the Human Resource section of the Intranet. 3.4 Constraints No new requirements to be added by the sponsors without affecting the project timeline and budget. Project Milestone • • • • • • • • • • • • • • • Milestone Target Date Project Start Project Charter Work Breakdown Structure Project Scope Statement Project Schedule Responsibility Assignment Matrix Project Schedule Resources Project Cost Estimate Project Quality Statement Stakeholder Analysis Communication Plan Risk Matrix Final Project Plan Software Orientation Learning Module Complete Final Integration Testing Complete 10/09/2007 10/09/2007 10/19/2007 10/26/2007 11/01/2007 11/06/2007 11/09/2007 11/16/2007 11/23/2007 11/28/2007 11/30/2007 12/07/2007 12/13/2007 1/18/2008 1/17/2008 Page 2 of 5 • • • • Documentation provided to Human Resource department Training Human Resource on new module complete Project Complete Post Mortem Lessons Learned 1/21/2008 1/21/2008 1/21/2008 1/22/2008 Project Approach Standard 5.1 Primary Plans The nearlyfree.com project will have the following formal written plans: • Project schedule. A firm schedule of events will be provided when all the requirements have been satisfactorily met. • Cost Estimate. Cost estimates will also be provided when all requirements are met. • Responsibility Assignment Matrix. • Quality Statement. A list of quality objectives is provided in the Quality Statement. • Communication Plan. A spreadsheet of the communication plan is provided in the Communication Management Section. • Risk Analysis. A probability of risk associated with the project will be provided. • Change Management. The change control procedures are included in the project plan. Project-Specific Briefly describe how each of the following will be handled. Provide links to relevant documents as appropriate. Modify example text provided or enter your own. 5.2 Change Management The change control procedures as documented in the Change Management Plan will be consistent with the Project Management Methodology and consist of the following processes: • A Change Request Log will be established by the Project Manager to track all changes associated with the project effort. • All Change Requests submitted via Change Request Form will be assessed to determine possible alternatives and costs. • Change Requests will be reviewed and approved by the project owner. • The effects of approved Change Requests on the scope and schedule of the project will be reflected in updates to the Project Plan. • The Change Request Log will be updated to reflect current status of Change Requests. 5.3 Communication Management The following strategies have been established to promote effective communication within and about this project. Specific Communication policies will be documented in the Communication Plan. Page 3 of 5 • • • • • The Project Manager will present project status to the project Sponsors on a weekly basis; however, ad hoc meetings will be established at the Project Manager’s discretion as issues or change control items arise. The Project Manager will provide a written status report to the project Sponsors on a monthly basis and distribute the Project Team meeting minutes. The project Sponsors will be notified via e-mail of all urgent issues. Issue notification will include time constraints, and impacts, which will identify the urgency of the request for service. The Project Team will have weekly update and status meetings to review completed tasks and determine current work priorities. Minutes will be produced from all meetings. All electronic Project Documents will be maintained in central storage accessible by all project stakeholders. 5.4 Resource Management The project team will produce a Resource Management Plan that will document the following: • Lists all major goods and services required in the project along with cost estimates and quality information. • Indicates which goods and services will be obtained from sources outside the Organization. • Indicates who is assigned to the project and when. Authorizations The Scope Statement is approved by the: • Project Sponsor Jennifer Beal • Project Manager Jeremy Lee Project performance baseline changes will be approved by the: • Project Sponsor Jennifer Beal • Project Manager Jeremy Lee Project deliverables will be approved or accepted by the: • Project Sponsor Jennifer Beal • Key Stakeholders Cheryl Gladstone Specific task responsibilities of project resources will be defined in the Responsibility Assignment Matrix. Project Scope Statement Approval / Signatures Project Name: NEO Project Project Manager: Jeremy Lee The purpose of this document is to provide a vehicle for documenting the initial planning efforts for the project. It is used to reach a satisfactory level of mutual agreement between the Project Page 4 of 5 Manager and the Project Sponsors and Owners with respect to the objectives and scope of the project before significant resources are committed and expenses incurred. I have reviewed the information contained in this Project Scope Statement and agree: Name Role Signature Date Jeremy Lee Project Manager e-sig 11/01/2007 Jennifer Beal Project Sponsor e-sig 11/01/2007 Cheryl Gladstone HR Manager e-sig 11/01/2007 The signatures above indicate an understanding of the purpose and content of this document by those signing it. By signing this document, they agree to this as the formal Project Scope Statement document. Page 5 of 5 Statement-of-Work Template Table of Contents 1. 2. Executive Summary ……………………………………………………………………………………………………………. 1 Statement of Work …………………………………………………………………………………………………………….. 2 Work Location: Describe where the work must be performed. Period of Performance: Specify when the work is expected to start and end, working hours, number of hours that can be billed per week, and where the work must be performed. Deliverables Schedule: List specific deliverables, describe them in detail, and specify when they are due. Quality Standards: Specify any company- or industry-specific standards that are relevant to performing the work. Acceptance Criteria: Describe how the buyer organization will determine if the work is acceptable. Special Requirements: Specify any special requirements such as hardware or software, level of personnel experience, travel requirements et cetera. 3. Project Management Plan. 3.1 Scope Statement………………………………………………………………. Error! Bookmark not defined. 3.2 Components in scope and not in scope …………………………….. Error! Bookmark not defined. 3.3 Detailed Requirements and List of Deliverables ……………………. Error! Bookmark not defined. 3.4 Acceptance Criteria …………………………………………………………… Error! Bookmark not defined. 3.5 Definition of Fixed-Price Contract. 3.6 Incorporation of Project Schedule……………………………………….. Error! Bookmark not defined. 4. Change Management Plan …………………………………………………………………………………………………. 5 5. Organization Structure and Definition………………………………………………………………………..5 6. Client Team Roles and Responsibilities……………………………………… Error! Bookmark not defined. 7. Constraints, Dependencies, and Assumptions ……………………………. Error! Bookmark not defined. 8. Communications Plan ……………………………………………………………… Error! Bookmark not defined. 9. Resource Plan ………………………………………………………………………… Error! Bookmark not defined. 10. Risk Assessment Plan ……………………………………………………………. Error! Bookmark not defined. 11. Training and Technical Requirements ……………………………………….. Error! Bookmark not defined. 11.1 Training Costs ………………………………………………………………….. Error! Bookmark not defined. 11.2 Software/Hardware/Other Costs …………………………………………. Error! Bookmark not defined. 12. Quality Plan …………………………………………………………………………… Error! Bookmark not defined. 13. Project Handover ……………………………………………………………………. Error! Bookmark not defined. 13.1 Final delivery and Production ………………………………………………. Error! Bookmark not defined. 14. Problems After Client Acceptance …………………………………………….. Error! Bookmark not defined. 15. Client Inputs and Other Comments …………………………………………… Error! Bookmark not defined. 16. Glossary and Terminology List …………………………………………………. Error! Bookmark not defined. 17. Appendices ……………………………………………………………………………. Error! Bookmark not defined. A. Signature and Approvals ………………………………………………………. Error! Bookmark not defined. B. Change Control for the Statement of Work ……………………………… Error! Bookmark not defined. C. Distribution List ……………………………………………………………………. Error! Bookmark not defined. Page 1 of 5 Statement-of-Work Template Project Name: Prepared by: Date (MM/DD/YYYY): Version History (insert rows as needed): Version Date Comments (MM/DD/YYYY) 1.0 1. Executive Summary 2. Statement of Work Definition of Fixed-Price Contract Work Location Describe where the work must be performed. Period of Performance Specify when the work is expected to start and end, working hours, number of hours that can be billed per week, and where the work must be performed. Deliverables Schedule List specific deliverables, describe them in detail, and specify when they are due. Page 2 of 5 Statement-of-Work Template Quality Standards Specify any company- or industry-specific standards that are relevant to performing the work. Acceptance Criteria Describe how the buyer organization will determine if the work is acceptable. Special Requirements Specify any special requirements such as hardware or software, level of personnel experience, travel requirements et cetera. 3. Project Management Plan (You can use MS Project Schedule in this section.) 4. Change Management Plan 5. Organization Structure and Definition 6. Client Team Roles and Responsibilities 7. Constraints, Dependencies, and Assumptions Page 3 of 5 Statement-of-Work Template 8. Communications Plan 9. Resource Plan 10. Risk Assessment Plan 11. Training and Technical Requirements 12. Quality Plan 13. Project Handover 14. Problems After Client Acceptance Page 4 of 5 Statement-of-Work Template 15. Client Inputs and Other Comments 16. Glossary and Terminology List 17. Appendices Page 5 of 5 Assignment 2… Develop a comprehensive earned value analysis report. This portfolio work project, an earned value management analysis, is based on your selected business or IT project. You may choose to base your assessment on the Revive LLC case study for the development of a new online employee orientation module, or you may continue to use a company of your choice. Both human resource (HR) and information technology (IT) employees, as well as contractors, will be utilized in this project. Earned value management (EVM) is defined “as a methodology that combines scope, schedule and resource management to assess project performance and progress” (Project Management Institute, 2017, p. 705). Project managers examine cost control, tools, and techniques that define the procedures by which the cost baseline may be changed. They engage in performance measurement to assess the magnitude of variations that occur during project execution. EVM is used to measure project performance by comparing certain predefined variables. Microsoft Project is a tool used to track planned cost versus actual cost, calculate the earned value, and forecast the effects of some cost changes. Reference Project Management Institute. Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Sixth Edition and Agile Practice Guide. Newtown Square. PA. 2017. Scenario For this assessment, choose either Option A or Option B. You do not need to do both. Both options will be graded using the same scoring guide. Option A: Project Revive LLC is a consulting firm of highly charged and accomplished project managers whose main stream of revenue comes from managing the turnaround of failing projects. As a consultant with Project Revive LLC you will study, analyze, and manage a failed project from NearlyFree.com. NearlyFree.com is a fictitious company and the project documents for NearlyFree.com project scenario are linked below. The NearlyFree.com project was originally scoped to develop and deploy an automated web-based training system for new employees to reduce the workload and cut down personnel resources required to complete the new employee orientation (NEO) training. As a veteran member of the Project Revive team, you already know the value of continually examining performance throughout a project to further define and update project data. Special attention to documenting and identifying problems is required in time to make appropriate adjustments. The earned value management (EVM) technique is often used in this type of analysis. Continue your analysis of the failed project by applying the EVM technique to examine performance based on what was accomplished. Option A Resources: NearlyFree.com Organizational Background and IT Governance [DOCX]. Project Charter [PDF]. Project Schedule [MPP]. Project Scope Statement [PDF]. Quality Statement [PDF]. Statement of Work Template [DOC]. Task Costs [XLS]. Work Breakdown Structure [DOC]. Work Breakdown Structure [VSD]. Option B: You may choose a business of your own. It must include (but is not limited to) the following criteria: Clearly indicate the title of the project in every assessment. You must have access to the following documentation: Scope statement. Final deliverable and product definition. Project work-breakdown structure. Project schedule. Quality plan. Project costs (estimates and actuals). Your Role For both Option A, you are the project manager. Requirements Microsoft Project is the recommended software tool for this course due to its wide industry acceptance and its use in many project management professional roles. To make this easier, you have the ability to download and install your own version of MS Project for use in this course. See the Software Preparation and Technology Access activity in Assessment 1 for more information. Practice using MS Project in this course will prepare you for future professional PM roles and responsibilities; please use MS Project for those tasks supported by MS Project. If you have access to other tools such as MS Visio, MS PowerPoint, MS Word, or other project management software that you believe may still meet the requirements of this course, please discuss your selected alternative with faculty. Use the PMBOK® Guide as the model for developing the deliverables. Earned Value Analysis Deliverable: Develop an Earned Value Analysis report of the current failed project. Complete the following: Use Microsoft Project or different, faculty-approved software to show earned value in a list of tasks that measure the cost of the work performed up to a certain date (the current date) based on the Project Schedule [MPP]. Consider how you can apply this analysis of the failed project to a successful project turnaround. Address the following topics. Where necessary, define assumptions you made. Apply an earned value technique. Explain the value of the information provided through the EVM technique. Analyze project success based on earned value calculations. Base project decisions on earned value calculations. Explain how you will apply earned value calculations to a successful project turnaround. Use the MS Project functionality (or another software program) to: Display project summary information and report. Create project reports. Export project plan cost data into Excel. Deliverable Format References: There is no set number of references required for this assessment. Use scholarly or academic sources where applicable. Format: Use Microsoft Project to obtain project costs information. Use your choice of MS Word, MS Visio, or MS PowerPoint to develop the comprehensive analyses. These analyses are professional documents and should therefore follow the corresponding Academic and Professional Document Guidelines [PDF], including single-spaced paragraphs. Use APA style and format for references and in-text citations.

CLICK HERE TO GET A PROFESSIONAL WRITER TO WORK ON THIS PAPER AND OTHER SIMILAR PAPERS

CLICK THE BUTTON TO MAKE YOUR ORDER

error: Content is protected !!