John Garrigues' presentation: Project Intiation at the ...


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • &file
  • &file
  • John Garrigues' presentation: Project Intiation at the ...

    1. 1. Project Initiation at The Regence Group 06/03/10 John Garrigues
    2. 2. Presentation Goals <ul><li>Learn a little about different Project Life Cycle (PLC) methodologies </li></ul><ul><li>At a high level, understand the Project Life Cycle used by The Regence Group (TRG) </li></ul><ul><li>Learn about the Concept and Inception phases </li></ul><ul><li>Understand how a project is initiated </li></ul>06/03/10 John Garrigues
    3. 3. John Garrigues (sounds like Syracuse) <ul><li>Information Technology (IT) positions </li></ul><ul><ul><li>Project Manager </li></ul></ul><ul><ul><li>Systems Administrator </li></ul></ul><ul><ul><li>Database Administrator </li></ul></ul><ul><ul><li>Network Administrator </li></ul></ul><ul><ul><li>Programmer/Analyst </li></ul></ul><ul><li>Managed IT projects for 20+ years </li></ul><ul><li>Managing projects for The Regence Group (TRG) since 1999 </li></ul><ul><li>PMP certification in January, 2001 </li></ul>06/03/10 John Garrigues
    4. 4. PLC Methodologies <ul><li>PMI Project Life Cycle </li></ul><ul><ul><li>Initiation </li></ul></ul><ul><ul><li>Planning </li></ul></ul><ul><ul><li>Execution & Control </li></ul></ul><ul><ul><li>Closure </li></ul></ul>06/03/10 John Garrigues
    5. 5. PMI Phases 06/03/10 John Garrigues
    6. 6. PLC Methodologies <ul><li>Rational Unified Process (RUP) </li></ul><ul><ul><li>An iterative software development process framework </li></ul></ul><ul><ul><li>An adaptable process framework </li></ul></ul><ul><ul><li>Developed by Rational Software Corporation, now a division of IBM </li></ul></ul><ul><ul><li>Includes artifacts (documents) to support each activity of the process </li></ul></ul><ul><ul><li>Phases include </li></ul></ul><ul><ul><ul><li>Inception phase </li></ul></ul></ul><ul><ul><ul><li>Elaboration phase </li></ul></ul></ul><ul><ul><ul><li>Construction phase </li></ul></ul></ul><ul><ul><ul><li>Transition phase </li></ul></ul></ul>06/03/10 John Garrigues
    7. 7. RUP Phases 06/03/10 John Garrigues
    8. 8. PLC Methodologies <ul><li>Enterprise Unified Process (EUP) </li></ul><ul><ul><li>RUP with 2 additional phases </li></ul></ul><ul><ul><ul><li>Production </li></ul></ul></ul><ul><ul><ul><li>Retirement </li></ul></ul></ul>06/03/10 John Garrigues
    9. 9. PLC Methodologies <ul><li>Regence PLC </li></ul><ul><ul><li>Developed by Enterprise Program Management Office (EPMO) </li></ul></ul><ul><ul><li>Phases </li></ul></ul><ul><ul><ul><li>Concept </li></ul></ul></ul><ul><ul><ul><li>Inception </li></ul></ul></ul><ul><ul><ul><li>Elaboration </li></ul></ul></ul><ul><ul><ul><li>Construction </li></ul></ul></ul><ul><ul><ul><li>Transition </li></ul></ul></ul><ul><ul><ul><li>Closure </li></ul></ul></ul>06/03/10 John Garrigues
    10. 10. Regence PLC Phases <ul><li>Concept: Project ideas are considered. Those that are approved become projects and continue in the lifecycle. </li></ul><ul><li>Inception: Business requirements are identified and scope is set for the project. Initial project planning is done. </li></ul><ul><li>Elaboration: System requirements are defined and the plan for the remainder of the project is set. </li></ul>06/03/10 John Garrigues
    11. 11. Regence PLC Phases <ul><li>Construction: The solution is built, testing is performed, and preparation for rollout is complete. </li></ul><ul><li>Transition: Final acceptance of the product, readying the organization, and rollout. </li></ul><ul><li>Closure: Administrative shut-down of the project. </li></ul>06/03/10 John Garrigues
    12. 12. Project Initiation at Regence <ul><li>Includes the Concept and Inception phases </li></ul><ul><li>Each phase has entrance criteria and exit criteria </li></ul><ul><li>Each phase has objectives </li></ul><ul><li>Each phase has activities to be completed by </li></ul><ul><ul><li>Portfolio or project management </li></ul></ul><ul><ul><li>Regence IT Services (RITS) Solution Development </li></ul></ul><ul><ul><li>Business </li></ul></ul><ul><ul><li>Finance </li></ul></ul>06/03/10 John Garrigues
    13. 13. 06/03/10 John Garrigues EPM Standards Regence Project Lifecycle (PLC) Concept Phase Definition Entrance Criteria Portfolio Management Activities Phase Objectives Business Activities Finance Activities EPMO Project Compliance Criteria <ul><li>Business Case is approved </li></ul><ul><li>Project is Staged </li></ul><ul><li>Start date is defined </li></ul><ul><li>Project Manager is assigned </li></ul><ul><li>Project Core team identified </li></ul><ul><li>Business need identified </li></ul><ul><li>Business proposal created </li></ul><ul><li>Business case created </li></ul><ul><li>Determine if project idea aligns with corporate strategies and key initiatives </li></ul><ul><li>Develop the high-level budget and define the high-level benefits </li></ul><ul><li>Assess the business case; approve or reject the project </li></ul><ul><li>Evaluate the project against the portfolio; determine the project’s start date </li></ul>Primary Phase Roles Business Sponsor SPG Decision Support RITS Delivery Manager EPMO Management <ul><li>None </li></ul>RITS Solution Development Activities Idea, Proposed or Staging State <ul><li>SPG reviews and approves Project Proposal </li></ul><ul><li>SPG reviews and approves Business Case </li></ul><ul><li>EPMO stages project </li></ul><ul><li>EPMO assigns Project Manager </li></ul><ul><li>Define high-level product/project requirements </li></ul><ul><li>Identify business mandates </li></ul><ul><li>Define member, employer, and provider experience features </li></ul><ul><li>Create Project Proposal </li></ul><ul><li>Create and Present Business Case for approval </li></ul><ul><li>Participate in Business Case development </li></ul><ul><li>Participate in OOM estimate </li></ul><ul><li>Create OOM estimate for entire project </li></ul><ul><li>Assign PeopleSoft ID and TKC when Project Proposal approved </li></ul><ul><li>Disable PeopleSoft ID and TKC when Business Case is approved </li></ul><ul><li>Reactivate PeopleSoft ID and TKC once project is staged </li></ul>Supporting Groups SPG PrOps Decision Support Project Accounting Portfolio Team Phase Exit Criteria
    14. 14. Conception Phase Artifacts <ul><li>Business Case </li></ul>06/03/10 John Garrigues
    15. 15. 06/03/10 John Garrigues EPM Standards Regence Project Lifecycle (PLC) Inception Phase Definition Phase Exit Criteria Project Management Activities Phase Objectives Business Requirements Activities Estimating / Budgeting Activities EPMO Project Compliance Activities <ul><li>Charter and Scope is approved </li></ul><ul><li>Project staged for RITS work. </li></ul><ul><li>Schedule for Elaboration created </li></ul><ul><li>Risk Assessment performed </li></ul><ul><li>Approx. 80% of Business Requirements defined </li></ul><ul><li>Context diagrams </li></ul><ul><li>Identify Primary Development Process </li></ul><ul><li>Non-functional requirements </li></ul><ul><li>Development case matrix updated </li></ul><ul><li>Budget and ROI revised/rebaselined </li></ul><ul><li>Business Case is approved </li></ul><ul><li>Project has been staged </li></ul><ul><li>Start date is defined </li></ul><ul><li>Project Manager is assigned </li></ul><ul><li>Project Core team named </li></ul>Primary Phase Roles Project Sponsor Business SME Project Manager Enterprise Analyst Systems Analyst* Solutions Engineer* Test Analyst* Lead Developer* Infra/ Env Lead* Secondary roles Delivery Manager/ Track Manager RITS Solution Development Activities Active State <ul><li>Establish the project's scope and acceptance criteria and accepted by Stakeholders </li></ul><ul><li>Capture the business context and the most important business requirements and constraints to such an extent that you can derive acceptance criteria for the end product </li></ul><ul><li>Identify the critical use cases of the system, the primary scenarios that will drive the major design tradeoffs </li></ul><ul><li>Estimate overall cost and schedule for the entire project; create definitive level estimates for Elaboration Phase </li></ul><ul><li>Identify and estimate potential risks and architecture tradeoffs </li></ul><ul><li>Prepare the supporting environment for the project (processes, templates, tools) </li></ul><ul><li>Plan, validate, and format requirements </li></ul><ul><li>Understand current state </li></ul><ul><li>Architect process flows </li></ul><ul><li>Organize requirements into groups; estimate and staff </li></ul><ul><li>Define future state </li></ul><ul><li>Model and decompose processes </li></ul><ul><li>Define non-functional requirements and business rules </li></ul><ul><li>Review Lessons Learned repository for similar projects </li></ul><ul><li>Create the project’s Charter and Scope and WBS </li></ul><ul><li>Create the detailed project schedule thru Elaboration; high-level thru remainder of project </li></ul><ul><li>Create the project management plans: schedule, cost, risk, requirements, communications, quality </li></ul><ul><li>Conduct Phase-Gate Review </li></ul><ul><li>Define the problem, alternative solutions and collaborate on business requirements </li></ul><ul><li>Assign RITS Core Team* (see primary roles) </li></ul><ul><li>Initial draft of functional specs, Master Test Approach, Integration Test Cases, Test Plan, and SAD document </li></ul><ul><li>Identify primary Process for Agile and/or Waterfall </li></ul><ul><li>High level story cards defined with TDD cases </li></ul><ul><li>Initial draft of Solution Map completed </li></ul><ul><li>Agile Development Team identified </li></ul><ul><li>Initial Integrated interfaces and high level architecture identified </li></ul><ul><li>Status report submitted on time </li></ul><ul><li>Development Case Matrix created thru Elaboration </li></ul><ul><li>Charter and Scope created </li></ul><ul><li>Communications, Risk, Quality, and Requirements Management Plans created </li></ul><ul><li>Budgetary estimate defined </li></ul><ul><li>DIRs in ClearQuest </li></ul><ul><li>Detailed project schedule created thru Elaboration </li></ul><ul><li>No later than 30 days after Inception starts: </li></ul><ul><ul><li>Create definitive Project Management estimates for the entire project </li></ul></ul><ul><ul><li>Create definitive Inception Phase / Business Requirements estimates </li></ul></ul><ul><ul><li>Confirm OOM estimates for remainder of project </li></ul></ul><ul><li>By End of Inception: </li></ul><ul><ul><li>Create definitive level estimates for Elaboration </li></ul></ul><ul><ul><li>Create budgetary level estimates for Construction thru Closure </li></ul></ul><ul><ul><li>Baseline project budget </li></ul></ul>Supporting Groups SPG/PrOps Decision Support Project Accounting Portfolio Team Entrance Criteria Agile-only activities shown in italics
    16. 16. Inception Phase Artifacts <ul><li>Charter and Scope </li></ul><ul><li>Initial Risk Assessment </li></ul><ul><li>Development Case Checklist </li></ul><ul><li>Budget and ROI </li></ul><ul><li>Benefit Realization </li></ul>06/03/10 John Garrigues
    17. 17. Summary <ul><li>Project Life Cycle (PLC) methodologies </li></ul><ul><ul><li>PMI, RUP, RSLC </li></ul></ul><ul><li>The TRG Project Life Cycle has phases </li></ul><ul><ul><li>Concept, Inception, Elaboration, Construction Transition, Closure </li></ul></ul><ul><li>Projects at are initiated by completing </li></ul><ul><ul><li>Concept phase </li></ul></ul><ul><ul><li>Inception phase </li></ul></ul>06/03/10 John Garrigues
    18. 18. Questions