JoseCaeresy

A project is of high quality as long as it delivers a product that meets the requirements on time and within budget Effective project management requires a project management team that understands and utilises knowledge and skills in the following areas of expertise Project management body of knowledge Application area knowledge, standards and regulations Project as a means of managing day-to-day operations Interpersonal skills 4. Project objectives are clarified when

Developing plans and specifications that meet the project manager's expectations 2. All of the following statements about project management are true Uncertain events or conditions can pose a project risk even if they do not affect any one of the "triple constraints" If one of the "triple constraints" changes, at least one of the other factors The project manager is the individual responsible for achieving the project objectives

Regularly assess the impact of requirements changes on project performance Requirements version control Requirements version control: ensure that everyone gets the latest version and record the historical version of requirements Requirements tracking 1. managing a project involves the following, in addition to (). a. identifying requirements b. defining clear and achievable objectives c. weighing quality, scope, time and cost requirements

to requirements changes; signed agreements for change control Good change implementation based on baselines; supported by good change control tools; integration of project changes into the project plan; timely release of change information Procedures for managing and controlling requirements changes: Establishing a requirements baseline, change control strategy and change control system; requirements changes are presented in a defined specification; requirements are as

analysts present the researched user requirements to the user in an appropriate manner Organisation of requirements acquisition by relevant development staff: set up a requirements analysis team; prepare; interview users to obtain questions; analyse requirements; prepare requirements specification; validate and review requirements; finalise requirements to establish a baseline; manage and control requirements changes Requirements change control Principles of requirements change control: treat change requests with care and control changes as far as possible

To select the appropriate timing; The person responsible for the configuration audit Work-in-progress process support, construct management, team support, status reporting, audit control for configuration audits 2.15 Requirements management Requirements baseline interviews User acquisition issues: to understand and classify all user types, and potential types, on the customer side;; to select representatives of each type of user to interview and research;; requirements analysts to further analyse and collate the collected user requirements

that the original estimate is completely out of date ⊙ Conditions change that the original estimate is not suitable 2) Equation 2: EAC = AC + BAC-EV (actual expenditure + budgeted BAC-EV for the remaining work) Application: The current deviation is considered exceptional and a similar deviation will not occur again. (where BAC-EV is the remaining budget3) Equation 3: EAC = AC + (BAC-EV)/CPI

CPI=EV/ACCPI>1.0 (cost savings) CPI<1.0 (cost overrun) SPI (schedule performance index): SPI=EV/PVSPI>1.0 (ahead of schedule) SPI<1.0 (behind schedule) Project performance assessment methods: deviation analysis, trend analysis, earned value analysis Estimate of completion (EAC): 1) Equation 1: EAC=AC+ETC (actual expenditure + new estimate for remaining work)

alue of work actually completed i.e. the amount of money that should be invested in the completed work up to a certain point.ETC (Estimated cost of remaining work) ETC = total PV - EV completed or ETC = PV of remaining work x CPI2) Most common yardsticks: CV (Cost deviation): CV = EV - ACCV>0 (Cost saving) CV<0 (Cost overrun) SV (Schedule deviation). SV=EV-PVSV>0 (over schedule) SV<0 (behind schedule)

easure of whether the project scope is complete Customer feedback Work Breakdown Structure Work Breakdown Structure Dictionary Project Scope Statement 1. control account (ontrolount) is used primarily for. The general ledger of resources allocated to each unit of the project The sub-ledger for each element of the work breakdown structure 2. All of the following statements are true What is produced by a project is usually a single product, but the product can include several subordinate parts

structures, change requests, scope management plans Performance reportingResponsibility matrixPareto chartMonte Carlo simulation method24. The work breakdown structure chart should be refined to. Levels determined by the sub-project project office can be sufficiently estimated levels cost centre levels 25. Develop a detailed scope description is in. Activity Definition Scoping 26. subdivision of key project deliverables called

project must be drawn up. Input Tools and Technical Outputs Procurement Management Plan Statement of Work (SOW) Project Management Plan Standard Forms for Home-made/Outsourced Decisions Expert Judgement Procurement Documentation Evaluation Criteria Statement of Work (updated) 13.4 Tendering Input Tools and Technical Outputs Procurement Documentation Organisational Process Assets Bidders' Conference Advertisement List of Qualified Vendors Procurement Documentation Package Proposal