1 / 10

Project Planning: 2005

Project Planning: 2005. Vision Statement. Develop a documented planning process that will provide a standards-based workflow Extend the Niku plant’s contributions IT governance -support the workflow

mariko
Download Presentation

Project Planning: 2005

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. Project Planning: 2005

  2. Vision Statement • Develop a documented planning process that will provide a standards-based workflow • Extend the Niku plant’s contributions IT governance -support the workflow • Implement metrics to gauge project success and relative profitability and conformance to the workflow

  3. Goal and Objective • Align with a Standard PM process and SDLC models appropriate to EHIT • Reduce dependence on paper and use electronic distribution with version control. • Develop program to reach CMM and/or ISO certification as a marking tool

  4. Today’s Situation • Identify issues using the Mon, Wed, Fri status meeting to collect this information. Done • Do we use Gantt charts, Fishbone diagrams, LRC, Process Flowcharts, PERT charts, WBS or EVM ? No • Is the meeting the only source of status information? No !

  5. How Do Project Start? • Operating Units obtain funding for Products and Services and EHIT installs • Facilities performs a build out and EHIT installs the network • Operating units request custom interfaces which EHIT builds.

  6. Analysis of ACN • State the alternative strategies • List advantages & disadvantages of each • State cost of each option

  7. 2005 Recommendations/Status • Automate the workflow making increased use of GroupWise – No. • Keep documents in organized Project repositories reducing paper usage - No • Develop estimation policies and procedures to support Paul better – Barely Started • Increase use of Niku for scheduling - Done.

  8. Recommendations ( Status ) • Reduce text in the status reports replacing the text with rollup milestones in Niku – Started.

  9. Recommendations ( Scoping ) • Put the reason Scopes were not signed by Brian somewhere, possibly cover sheet, so patterns can be identified – Not Done.

  10. Recommendation ( Closure ) • Track actual costs versus planned and develop standard estimates for Labor – in progress - Started • Develop Niku report for tasks not starting on time, manage by exception – started.

More Related