1 / 10

Project Management the ITSD Way

Project Management the ITSD Way. What is project management in ITSD? Why do we need it? How does it work? Pros and Cons Tips and Tricks. What is Project Management?. Baseline vs Project Work Routine vs unique Production Desktop Services, Data Center Development

hop
Download Presentation

Project Management the ITSD Way

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 Management the ITSD Way • What is project management in ITSD? • Why do we need it? • How does it work? • Pros and Cons • Tips and Tricks

  2. What is Project Management? • Baseline vs Project Work • Routine vs unique • Production • Desktop Services, Data Center • Development • Information Services, Technology Systems Development • Basic Elements of Project Mgmt • Initiating, Planning, Execution, Monitoring, Closeout

  3. Why do we need it? • Communication • Planning • Ensure appropriate hardware is in house to complete project • Identify all foreseeable risks and account for them • Identify and plan for contingencies • Identify objectives and work towards them • Scheduling • Ensure project has an end • Ensure resource agreement and availability

  4. How does it work? • Overview • Example: Network upgrade

  5. Ideas for Projects ED01/M&E Grants Keep the lights on Evaluations Strategic planning Scoping Skills needed? Hardware needed? Timeframe? Deadlines? Why or business case? Identify opportunities Definition Who will be on project and for how long? What charge number? Procedures/Training Schedule? Objectives? Possible approaches Risk assessment Architecture (ITARB) What has changed? Diagrams updated? Standards followed/if not, why not? Deployment What is the plan? When? Who? Back out plans? Announcement to staff? Closeout 30 day warranty Close out charges, etc. Lessons Learned Basic PM

  6. Planning Phase • Scope • Monitoring • Management authorizes official start • PMO assigns a rep to mentor pm • Project scheduled for bi-weekly reporting • Definition • See handout • Resources assigned • Rough schedule provided

  7. Execution • Implementation • Schedule developed • Tasks assigned • Deployment procedures are developed • Training and Testing procedures are developed • Deployment Meeting • Architecture changes • Time agreed upon • All staff message written • Back out plan is discussed

  8. Close out • Warranty period of 30 days begins • Identify follow on projects • All test accounts, test environments, replaced hardware shutdown or closed out • Charge numbers closed out • Lessons Learned held • By email or in person and posted to web

  9. Pros and Cons • Pros • Better planning means standardization, execution moves more quickly and smoothly with fewer mistakes, thus fewer remedy calls, • Easier to identify training goals • Repeatable processes – procedures developed • Control • Cons • More writing, reading, meetings/discussions/status • Takes greater time to start up • Can invest time in startup and project may be scrapped in the end • Culture change

  10. Tips and Tricks • Templates and checklists • Training • Flow Charts • QuickBase

More Related