Project Review Checklist.docx

1、Project Review ChecklistProjectProject Audit & Review ChecklistThe following provides a detailed checklist to assist the PPO with reviewing the health of a project:Relevance (at this time)Theory & Practice(How relevant is this attribute to this project or audit?)(An indication of this attributes str

2、ength or weakness)ReviewReviewItemAttributeRelevancePracticeAssessment1Project Planning1.1Does the project have a formal Project Plan?1.2Are the key elements of a Project Plan present?a. Project Definition & Scope?b. Project Objectives?c. Cost / Benefit Analysis?d. Staffing Requirements?e. Time Line

3、?f. Risk Analysis?g. Critical Success Criteria (if we meet these, weve met our goals?51.3Have all stakeholders been identified?1.4Is a Stakeholder Management plan in place? Have project accountabilities & responsibilities been clearly defined?1.5Have the scope, objectives, costs, benefits and impact

4、s been communicated to all involved and/or impacted stakeholders and work groups?1.6a) Have all involved stakeholders and work groups committed to the project? b) Have all necessary approvals been obtained?1.7Has a project Communications Plan been developed?1.8Are funding and staffing resource estim

5、ates sufficiently detailed and documented for use in planning and tracking the project?1.9Does a documented project organizational policy & plan (i.e. governance model) exist?1.10Have adequate resources been provided by management to ensure project success?1.11Is current scope of the project substan

6、tially different than that originally defined in the approved project plan?1.12Has the approach and development strategy of the project been defined, documented and accepted by the appropriate stakeholders?1.13Have project management standards and procedures been established and documented?1.14Is th

7、ere a Steering Committee in place?1.15Is the Steering Committee active in project oversight?1.16Are there procedures in place to effectively manage interdependencies with other projects / systems?2Project Management2.1Have the key elements of a coherent project management strategy been established?a

8、. Project tracking plan & methodologyb. Project status reporting structure & processc. Change Management plan & trackingd. Issues Management process & tracking plane. Risk Management Planf. Software Quality Assuranceg. Software Configuration Management2.2Project Scheduling & Tracking2.2.1Has a struc

9、tured approach been used to break work effort into manageable components?2.2.2Are team members involved in the development of activity & task decomposition?2.2.3Are individual tasks of reasonable duration (840 hrs)?2.2.4Are milestone deliverables effectively tracked and compared to project plan?2.2.

10、5Does the detailed project plan identify individual responsibilities for the next 46 weeks?2.2.6Have activity relationships and interdependencies within tasks been adequately identified?2.2.7Are target dates established for each milestone deliverable?2.2.8Are corrective actions taken when actual res

11、ults are substantially different from detailed project plan? Describe.2.2.9Are changes in deliverable commitments agreed to by all affected groups & individuals?2.2.10Is the organization structure for both tracking & controlling project activities work products & costs (effort, schedule & budget) we

12、ll defined and assigned to a specific individual?2.2.11Are measurements and feedback mechanisms incorporated in tracking work effort & refining work estimating techniques?2.2.12Have procedures for identifying variances from estimates & adjusting the detailed work program been established?2.2.13Is pr

13、oject work proceeding in accordance with the original project schedule?2.2.14If not, have all project delays been adequately accounted for, communicated to all stakeholders and adjustments made in overall project schedule?2.2.15Is there general agreement & acceptance of the current status and progre

14、ss of the project?2.2.16Is PERT / Critical Path or equivalent methodology being used? Can you see the critical path on the plan?2.2.17Is an industry recognized mechanized support tool(s) being used for project scheduling & tracking?2.2.18Is it possible to track all classes of project work (e.g. sche

15、duled, un-scheduled, defect repair, etc.)? Can you compare work done to the baseline?2.3Project Status Reporting2.3.1Is project status reviewed with senior management at appropriate intervals? What are they?a. Overall statusb. Project performance (achievements & milestones)c. Open issuesd. Riskse. A

16、ction itemsf. Cost & time performance against plang. Quality metricsh. Client involvement2.3.2Are internal project status meetings held at reasonable intervals?2.3.3Are sub-project reviews held at reasonable intervals?2.3.4Have adequate procedures been put in place for project coordination and statu

17、s reporting across project boundaries (ie. interdependent software development among interfacing systems)?2.3.5Do project teams & team members report on status / activities / progress?2.4Project Estimating2.4.1Are multiple estimation methods being employed?2.4.2Are current project time & resource es

18、timates reasonable based on the current project stage?2.4.3Are actuals compared against estimates to analyze and correct variances?2.4.4Are software metrics formally captured, analyzed and used as a basis for other project estimates?2.4.5Is the PPO estimating methodology being used and followed?2.4.

19、6Do the estimating techniques include any of the following features:a. Ranged estimates?b. Sensitivity analysis?c. Risk rating?d. Quality Assurance overheads?e. Contingency?2.4.7Are project team members involved in detailed estimating and scheduling?2.4.8Are stakeholders aware and supportive of the

20、principles and practices of modern software estimation?2.5Risk Management2.5.1Was an original risk assessment completed?2.5.2Is there a process in place to monitor project risks?2.5.3Has provision been made to reassess project risks at various project stages?2.5.4Have all unresolved risks been docum

21、ented?Have all unimplemented risk strategies been escalated to an issues log?3Quality Management3.1Does the project have a Quality Culture?3.2Is there a Quality Plan covering all Policies, Guidelines and Procedures?3.3Quality Assurance3.3.1Has an overall Quality Assurance Plan been developed for the

22、 project?3.3.2Does the plan address key project elements?a. Project Planning?b. Project Management?c. Software Quality Assurance (SQA)3.3.3Does the SQA process provide objective verification of adherence to applicable standards, procedures & requirements?3.3.4Are all key components of an SQA plan pr

23、esent?a. SQA Planb. Software Configuration Management (SCM)c. Software development standards & methodsd. Methodologye. Testing Standards & Methodologyf. Data Architecture Standardsg. Data Naming Conventionsh. Technology Architecturei. Software Metrics3.3.5Are the results of SQA reviews provided to a

24、ffected groups & individuals?3.3.6Are adequate resources provided for the SQA function? Are SQA resources experienced?3.3.7Are the SQA processes in place and being effectively used?3.4Is there a set of procedures defining the scope, procedures and deliverables defining Quality Control?3.5Are quality

25、 metrics defined?3.6Is there a set of procedures to capture, analyze and act on quality metrics?3.7Software Configuration Management (SCM)3.7.1Has SCM been implemented for this project?3.7.2Has an industry recognized SCM software version management & control tool been implemented?3.7.3Is SCM version

26、 management and control effectively linked with the testing function to ensure integration and regression testing have been performed?3.7.4Has an automated Change Management tool been implemented?3.7.5Is the SCM function adequately staffed?3.7.6Is the Testing Coordination function separate from the

27、development staff?4.0Management Procedures4.1Vendor Management4.1.1Is there a formal set of procedures (for status reporting, contract negotiation & review, time/invoice reconciliation, etc.) supporting Vendor Management?4.2Issues Management4.2.1Is there a formal set of procedures supporting Issues

28、Management?4.2.2Is there any form of automated support for Issues Management?4.2.3Are issues raised, assessed, actioned, and resolved in a timely and efficient manner?4.3Stakeholder Management4.3.1Is there a formal set of procedures supporting Stakeholder Management?4.3.2Is it standard practice to f

29、ormally commit stakeholders to the project via agreements?4.3.3Does a comprehensive set of Stakeholder Agreements exist? Do we have statements delineating what each stakeholder has agreed to do?5.0Resourcing5.1Are all resource assumptions documented?5.2Does the project team have the skills necessary to successfully complete current project(s) and support the application?5.3Have arrangements been made to obtain special expertise or competence by consulting or referencing:a. Similar projects?b. Published materials?c. Perso