Project Management <br />Intake workflow Process<br />
Glossary<br />Implementation Methodology (IM)<br />Vendor Selection Methodology (VSM)<br />Project Acceptance Documentatio...
Goals<br />3<br /><ul><li> “ Value Added”
 Better Communication
 Tools to Enhanced the process
 Accountability of service</li></li></ul><li>4<br />
5<br />IT PROJECT REQUEST<br />**Please note that in some point in the process you may be asked to present your request to...
6<br />
7<br />
8<br />
PART 1:  Business Case<br /> <br />Complete the business case describing the problem or opportunity, proposal, budget and ...
For System Implementation or FD&C Move:  Planning, Design, Build, Testing, Training, Go Live, Post Go Live Transition to S...
ESTIMATE <br />SUPPORTING DETAIL ON ESTIMATED COST<br />Cost and/or Pricing Assumptions (if any) <br />Hardware, Software,...
11<br />
12<br />
Shared Point<br />Store documents<br />Final Project name Project Charter<br />Final Project name Project Plan<br />Projec...
Upcoming SlideShare
Loading in...5
×

Intake Process Itpmo

7,018

Published on

Intake Process

Published in: Technology
8 Comments
4 Likes
Statistics
Notes
No Downloads
Views
Total Views
7,018
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
113
Comments
8
Likes
4
Embeds 0
No embeds

No notes for slide
  • Enhancement Goals
  • Intake Process Itpmo

    1. 1. Project Management <br />Intake workflow Process<br />
    2. 2. Glossary<br />Implementation Methodology (IM)<br />Vendor Selection Methodology (VSM)<br />Project Acceptance Documentation (PADS)<br />Operational Acceptance (OA)<br />Quality Assurance (QA)<br />Methodologies – A publication including reusable documents such as work plan, guidebook, knowledge tips, sample deliverables and training. <br />SharePoint - Internet technology tool that delivers applications for project planning and collaboration among projects. <br />SME – Subject Matter Expert<br />2<br />
    3. 3. Goals<br />3<br /><ul><li> “ Value Added”
    4. 4. Better Communication
    5. 5. Tools to Enhanced the process
    6. 6. Accountability of service</li></li></ul><li>4<br />
    7. 7. 5<br />IT PROJECT REQUEST<br />**Please note that in some point in the process you may be asked to present your request to the IT Subcommittee.<br />
    8. 8. 6<br />
    9. 9. 7<br />
    10. 10. 8<br />
    11. 11. PART 1: Business Case<br /> <br />Complete the business case describing the problem or opportunity, proposal, budget and potential benefits. Clearly describe the key business and scope assumptions. If this is an implementation, briefly describe how vendor selection was done or refer to the VSM project. Include the Description of Benefits template. <br /> <br />What business opportunity or problem are you addressing?<br />What are you proposing?<br />What budget is needed?<br />What are the potential benefits (including the estimated Return on Investment)?<br />PART 2: Operational Impacts<br /> <br />Describe any operational impacts that are important to consider as part of this project. Clearly describe any operational assumptions that are critical to success.<br /> <br />Workflow – Implications / Considerations<br />Training Requirements<br />Out of Scope / Dependencies<br />PART 3: High-Level Project Schedule<br /> <br />Complete and attach a high level project schedule that includes – at a minimum – the following phases:<br /><ul><li>For Vendor Selection: Planning, Requirements Definition, Request for Proposal, Finalize Selection, Contracting (VSM template)
    12. 12. For System Implementation or FD&C Move: Planning, Design, Build, Testing, Training, Go Live, Post Go Live Transition to Support (HPS template)</li></ul>Duration and level of detail about the phases is only expected to be very high level in a sizing. <br /> <br />9<br />
    13. 13. ESTIMATE <br />SUPPORTING DETAIL ON ESTIMATED COST<br />Cost and/or Pricing Assumptions (if any) <br />Hardware, Software, Resource Cost Estimates – Project and Ongoing Maintenance<br />Resource Requirements (Vendors, Roles, FTEs)Document what people resources are needed. Identify the vendors, roles and FTE levels needed to implement the project and maintain the deliverables. If appropriate to the level of certainty achieved during the sizing, include a Resource Planning Grid(s), SOW(s), etc.<br />10<br />Include the appropriate Technology Resource Planning Questionnaire(s):<br />
    14. 14. 11<br />
    15. 15. 12<br />
    16. 16. Shared Point<br />Store documents<br />Final Project name Project Charter<br />Final Project name Project Plan<br />Project Basic Information<br />Timeline<br />Scope<br />13<br />
    17. 17. Benefits<br />Better Quality <br />Improve thoroughness and consistency of deliverables by following standard, step-by-step approach<br />Increase quality of work by leveraging best practices and learning's of previous Initiatives and research<br />Gain in Productivity of Existing Resources<br />Increase accountability of project team members since deliverables and objectives are clearly defined<br />Increase productivity since materials are reusable and can be tailored to suit specific project needs<br />Better Communication<br />Standardize Documentation Tools <br />14<br />
    18. 18. How do we make it work?“Educate, Educate, Educate” Obtain Full Management Support<br />15<br />
    19. 19. Questions?<br />
    1. Gostou de algum slide específico?

      Recortar slides é uma maneira fácil de colecionar informações para acessar mais tarde.

    ×