1 / 18

Project Initiation at The Regence Group

Project Initiation at The Regence Group. Presentation Goals. Learn a little about different Project Life Cycle (PLC) methodologies At a high level, understand the Project Life Cycle used by The Regence Group (TRG) Learn about the Concept and Inception phases

tyra
Download Presentation

Project Initiation at The Regence Group

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 Initiation at The Regence Group John Garrigues

  2. Presentation Goals • Learn a little about different Project Life Cycle (PLC) methodologies • At a high level, understand the Project Life Cycle used by The Regence Group (TRG) • Learn about the Concept and Inception phases • Understand how a project is initiated John Garrigues

  3. John Garrigues (sounds like Syracuse) • Information Technology (IT) positions • Project Manager • Systems Administrator • Database Administrator • Network Administrator • Programmer/Analyst • Managed IT projects for 20+ years • Managing projects for The Regence Group (TRG) since 1999 • PMP certification in January, 2001 John Garrigues

  4. PLC Methodologies • PMI Project Life Cycle • Initiation • Planning • Execution & Control • Closure John Garrigues

  5. PMI Phases John Garrigues

  6. PLC Methodologies • Rational Unified Process (RUP) • An iterative software development process framework • An adaptable process framework • Developed by Rational Software Corporation, now a division of IBM • Includes artifacts (documents) to support each activity of the process • Phases include • Inception phase • Elaboration phase • Construction phase • Transition phase John Garrigues

  7. RUP Phases John Garrigues

  8. PLC Methodologies • Enterprise Unified Process (EUP) • RUP with 2 additional phases • Production • Retirement John Garrigues

  9. PLC Methodologies • Regence PLC • Developed by Enterprise Program Management Office (EPMO) • Phases • Concept • Inception • Elaboration • Construction • Transition • Closure John Garrigues

  10. Regence PLC Phases • Concept: Project ideas are considered. Those that are approved become projects and continue in the lifecycle. • Inception: Business requirements are identified and scope is set for the project. Initial project planning is done. • Elaboration: System requirements are defined and the plan for the remainder of the project is set. John Garrigues

  11. Regence PLC Phases • Construction: The solution is built, testing is performed, and preparation for rollout is complete. • Transition: Final acceptance of the product, readying the organization, and rollout. • Closure: Administrative shut-down of the project. John Garrigues

  12. Project Initiation at Regence • Includes the Concept and Inception phases • Each phase has entrance criteria and exit criteria • Each phase has objectives • Each phase has activities to be completed by • Portfolio or project management • Regence IT Services (RITS) Solution Development • Business • Finance John Garrigues

  13. EPM Standards Regence Project Lifecycle (PLC) Concept Phase Definition Idea, Proposed or Staging State Phase Exit Criteria Phase Objectives Entrance Criteria • Determine if project idea aligns with corporate strategies and key initiatives • Develop the high-level budget and define the high-level benefits • Assess the business case; approve or reject the project • Evaluate the project against the portfolio; determine the project’s start date • Business Case is approved • Project is Staged • Start date is defined • Project Manager is assigned • Project Core team identified • Business need identified • Business proposal created • Business case created Portfolio Management Activities Business Activities • SPG reviews and approves Project Proposal • SPG reviews and approves Business Case • EPMO stages project • EPMO assigns Project Manager • Define high-level product/project requirements • Identify business mandates • Define member, employer, and provider experience features • Create Project Proposal • Create and Present Business Case for approval RITS Solution Development Activities • Participate in Business Case development • Participate in OOM estimate Primary Phase Roles Business Sponsor SPG Decision Support RITS Delivery Manager EPMO Management Supporting Groups SPG PrOps Decision Support Project Accounting Portfolio Team EPMO Project Compliance Criteria Finance Activities • None • Create OOM estimate for entire project • Assign PeopleSoft ID and TKC when Project Proposal approved • Disable PeopleSoft ID and TKC when Business Case is approved • Reactivate PeopleSoft ID and TKC once project is staged John Garrigues

  14. Conception Phase Artifacts • Business Case John Garrigues

  15. EPM Standards Regence Project Lifecycle (PLC) Inception Phase Definition Active State Entrance Criteria Phase Exit Criteria Phase Objectives • Establish the project's scope and acceptance criteria and accepted by Stakeholders • 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 • Identify the critical use cases of the system, the primary scenarios that will drive the major design tradeoffs • Estimate overall cost and schedule for the entire project; create definitive level estimates for Elaboration Phase • Identify and estimate potential risks and architecture tradeoffs • Prepare the supporting environment for the project (processes, templates, tools) • Charter and Scope is approved • Project staged for RITS work. • Schedule for Elaboration created • Risk Assessment performed • Approx. 80% of Business Requirements defined • Context diagrams • Identify Primary Development Process • Non-functional requirements • Development case matrix updated • Budget and ROI revised/rebaselined • Business Case is approved • Project has been staged • Start date is defined • Project Manager is assigned • Project Core team named Project Management Activities Business Requirements Activities • Review Lessons Learned repository for similar projects • Create the project’s Charter and Scope and WBS • Create the detailed project schedule thru Elaboration; high-level thru remainder of project • Create the project management plans: schedule, cost, risk, requirements, communications, quality • Conduct Phase-Gate Review • Plan, validate, and format requirements • Understand current state • Architect process flows • Organize requirements into groups; estimate and staff • Define future state • Model and decompose processes • Define non-functional requirements and business rules RITS Solution Development Activities • Define the problem, alternative solutions and collaborate on business requirements • Assign RITS Core Team* (see primary roles) • Initial draft of functional specs, Master Test Approach, Integration Test Cases, Test Plan, and SAD document • Identify primary Process for Agile and/or Waterfall • High level story cards defined with TDD cases • Initial draft of Solution Map completed • Agile Development Team identified • Initial Integrated interfaces and high level architecture identified 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 Estimating / Budgeting Activities EPMO Project Compliance Activities • No later than 30 days after Inception starts: • Create definitive Project Management estimates for the entire project • Create definitive Inception Phase / Business Requirements estimates • Confirm OOM estimates for remainder of project • By End of Inception: • Create definitive level estimates for Elaboration • Create budgetary level estimates for Construction thru Closure • Baseline project budget • Status report submitted on time • Development Case Matrix created thru Elaboration • Charter and Scope created • Communications, Risk, Quality, and Requirements Management Plans created • Budgetary estimate defined • DIRs in ClearQuest • Detailed project schedule created thru Elaboration Agile-only activities shown in italics Supporting Groups SPG/PrOps Decision Support Project Accounting Portfolio Team John Garrigues

  16. Inception Phase Artifacts • Charter and Scope • Initial Risk Assessment • Development Case Checklist • Budget and ROI • Benefit Realization John Garrigues

  17. Summary • Project Life Cycle (PLC) methodologies • PMI, RUP, RSLC • The TRG Project Life Cycle has phases • Concept, Inception, Elaboration, Construction Transition, Closure • Projects at are initiated by completing • Concept phase • Inception phase John Garrigues

  18. Questions

More Related