1 / 20

Tools and Measures: Project Planning and Control

Tools and Measures: Project Planning and Control. Presented to the NIH Project Management Community October 10, 2007 Michele Duell, VP, Apptis Healthcare Solutions.

renata
Télécharger la présentation

Tools and Measures: Project Planning and Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tools and Measures: Project Planning and Control Presented to the NIH Project Management Community October 10, 2007 Michele Duell, VP, Apptis Healthcare Solutions

  2. The chilly ice cube department needed an enterprise software program to control routine and special ice cube maintenance and procurement procedures Beltway custom systems integrations (CSI Beltway) brought a COTS application to chilly and managed the project COST-LOTS owned a proprietary client-server ice cube maintenance program Case Study – Ice Cube Maintenance System

  3. Chilly presented their 307 system requirements CSI beltway’s project manager accepted the requirements and agreed to the FFP costs and the schedule COTS-LOTS agreed to modify their client-server architecture to a browser-based solution (at no cost) Project Kick-off

  4. Meltdown in Progress • Software configuration – now development – continued for months beyond the original schedule • Testing failed • Progress reports were missed or misleading • Cost overruns were at 300%

  5. What’s Missing? • Project Plans/Lifecycle – loose/non-existent • WBS - missing • Progress Measurements/Reviews – missing • Requirements Stability – missing

  6. Establishes vision and scope Establishes budget and schedule Identifies risks and their mitigations Project resource identification (time, money, staff) Stakeholder involvement (reviews, change management) A Detailed Project Plan Is the First Line of Defense Against Project Problems

  7. Simulation of the project Approval document Internal contract Budget document Reality check Gaining Benefit From the Project Plan

  8. To start very simply, go with the rule of thirds Iterations = phases = milestones Divide and conquer How to Simulate the Project?

  9. High Level Work Breakdown Structure

  10. Detailed Work Breakdown Structure

  11. Assign staff to tasks Record the costs for using each resource Earned value is now easy to calculate Use the Resource Tab in the WBS to Track Budget

  12. Steps to view earned value totals for a task: On the view menu, click more views. In the views list, click task sheet, and then click apply. On the view menu, point to table, and then click more tables. In the tables list, click earned value, and then click apply. Project Plan May Be Used to Track Earned Value

  13. All the Earned Value Formulas Will Be Displayed • Tip: To get detailed information about each Earned Value field, hover over its heading to see more information.

  14. Earned Value is a standardized method for measuring performance Common Earned Value measurements across PMO Used consistently, Earned Value contributes to success Why Earned Value?

  15. BCWS – Budgeted Cost of Work Scheduled BCWP – Budgeted Cost of Work Performed ACWP – Actual Cost of Work Performed EAC – Estimate at Complete Most Common Earned Value Formulas

  16. Quality requirements and avoiding mistakes Provide for negotiation and iteration Discover missing information or incorrect assumptions Define relative priorities Eliminate ambiguous language Ice Cube Maintenance – Gap From Requirements to Solutions

  17. Gain agreement on requirements between all stakeholders Provide a basis for software design Produce a specification for testing Three Purposes of Requirements Management

  18. Many other aspects of project management Balancing act Confusing process with goals More Than Project Planning and Requirements Management

  19. Adoption of a known model is a highly effective method of determining performance measures All of the formal models provide the ability to measure ROI Continuous improvement is inherent in the formal models, allowing for increased service without increasing resources Formal models include the CMMI, ITIL, EVMS, PMI, NIST 800-26 One Framework for Assessing Current and Future Needs Is the Maturity Model Approach

  20. Joyce Hunter 703.332.9868 Joyce.hunter@apptis.com Michele Duell 703.625.0057 micheleduell@apptis.com Contact Information

More Related