Project Management Office (PMO) Overview DOM Administration Grand Round June 17, 2014

1. Project Management Office (PMO)Overview DOM Administration Grand Round June 17, 2014

2. Project Management Office: Purpose • The BMC PMO is a dedicated business unit, which defines and maintains standards for project management within the organization • The primary goal of BMC PMO is to achieve benefits from developing and following standardized project management policies, processes and methods  • Projects and project management are carried out in an environment broader than that of the project itself • The project management team must understand this broader context so it can select the life cycle phases, processes, documents and tools that appropriately fit the project • Project management is the discipline of planning, organizing, motivating, and controlling resources to achieve specific goals, related to managing and implementing projects within the organization

3. Project Management Office: Mission Statement • The BMC Project Management Office provides a standardized approach to identify, • prioritize, and successfully execute a project portfolio.  Project management leadership • is responsible for establishing and implementing best practices to encourage • collaboration, standardization, and overall improvement to managing and prioritizing • projects.The primary focus is to manage and control projects to ensure they are • implemented on schedule, within scope, and budget. • Goal: Complete a successful project for our customers!

4. Project Management Office: Organization

5. Project Management Office - Governance • ITS Prioritization Committee: Meet Bi-Monthly • Key strategic and policy decisions – approach, direction, priorities, rules, governance • Implementation, oversight and conflict resolution • Strategic level coordination among BMC entities • Committee Members: BMC Vice Presidents • Clinical – Physician, Clinical – Nursing, Financial, Strategic, Operations, Information Technology Services • ITS Internal Governance Committee: Meet Weekly • Affinity groups formed to research key issues • Champions from functional area working groups to drive development of business cases • Implementation of decisions made by Operations Group • Liaison to end users • Approved VP Projects review of required resources/timelines • Project Phase Change Requests (e.g. Assessment to Planning) • Committee Members: • IT Directors, IT Leadership, PMO Staff, other ITS staff as needed

6. ITS Internal Governance Committee ITS Director Monthly Roadmap End User Weekly Roadmap Workgroups • Project Management Office - Governance ITS Prioritization Committee Chair and Facilitator

7. Project Manager Assignment Criteria • Project Size: • Small Project: 5 to 25 FTE days • Medium Project: 26 to 75 FTE days • Large Project: 76+ FTE days • Timeline: • Project defined start and end date • Exception Criteria: • Several of these should be met to drive the assignment of a PM (subjective decision)

8. Timeline: 01.02.13 01.15.13 02.01.13 03.12.13 <Project Kick - Off> <Project Go - Live> Costs: PROJECT COSTS PROJECT COSTS PER YEAR Year 1 Year 2 Year 3 Total 1. Hardware $ 36,208 $ - $ - $ 36,208 2. Software $ 479,095 $ - $ - $ 479,095 3. Other $ 100,861 $ - $ - $ 100,861 Totals $ 616,164 $ - $ - $ 616,164 Cumulative Total $ 616,164 Example Where Project Manager IS Assigned Problem Statement: There is currently no pharmacy in the Shapiro building and patients either have to walk to other BMC buildings (YACC or DOB) or go to other pharmacies outside the hospital resulting in hospital revenue loss

9. Resources: Example Where Project Manager IS Assigned • Challenges: • Timeline – Mid March timeline is very aggressive • New Vendors and Applications – Eight of the vendors and products are new to BMC • Coordination between vendors has been a challenge • Training – Staff must be trained on a number of new equipment and software in a short period of time

10. Timeline: 12 - Oct 12 - Dec 02/21/13 03/21/13 - <Project Kick - Off> <Project Go - Live> Example Where Project Manager NOT Assigned Problem Statement: Portal 1.0 due to its use of SSO does not allow users at BMC public computers to access the portal’s dashboards and reports. In addition, the loss of the consultants who wrote 1.0, has caused us to rebuild as to allow for the access above and ongoing support Resources: • Costs: • None – No server costs, no consultant costs • Challenges: • Beta Sign-Off

11. Why Projects Fail? • The following is a list of primary project failure causes: • Poor Planning • Unclear Goals and Objectives • Objectives changing during the project • Unrealistic time or resource estimates • Lack of executive support and user involvement • Failure to communicate and act as a team • Inappropriate skills Engage a Project Manager

12. Project Life Cycle: Overview • Traditional project management life cycle consists of a number of phases • Regardless of the methodology or terminology used, the same basic management processes are utilized • Connects the beginning of the project to its end completion • PMO utilizes 6 basic phases to direct and control projects: • Request • Assessment • Planning • Implementation • Go Live • Closure

13. Project Life Cycle: Phase Definitions • Request • Reviewed via the VP Governance Process; ITS Prioritization Committee (approves, denies, additional information) • Assessment • Careful examination of whether or not the project benefits the organization and can realistically be completed given budget, timeline, resource constraints, etc • Planning • Detailed planning of time, cost, and resources to estimate the work needed and manage risk during project execution • Failure to adequately plan greatly reduces the project's chances of successfully accomplishing its goals • Implementation • Coordinating people and resources, as well as integrating and performing the activities of the project in accordance with the project management plan • Deliverables are produced as outputs from the processes performed as defined in the project management plan and other frameworks • Go-Live • Project is moved into production • Project Closure • Evaluation conducted to highlight project success and lessons learned • Transitioned to appropriate operations resources 2 weeks post go-live

14. Project Life Cycle: Generic Life Cycle Structure • Typical Cost and Staffing Levels Across a Generic Project Life Cycle Structure • Projects vary in size and complexity, but can be mapped to this generic life cycle structure • Referenced when communicating to upper management or others less familiar with project details • High level view provides common frame of reference for comparing projects • Does not apply to all projects

15. Project Life Cycle: Summary • Defined as the completion and approval of one or more deliverables • Phase can be closed and no additional phases initiated (i.e. assessment is • completed and determines the risk or cost is too great for the project to continue • Phases could be further subdivided into sub-phases for reasons of size, complexity, • risk, or cash flow constraints • PMO Governance Process is utilized to transition projects from one phase to another • The ITS PMO Toolkit and Project Document Life Cycle were developed to assist the • management of ITS projects

16. PMO Toolkit • Project Management Office Team has developed a standardized set of tools to assist in the management of Initiatives/Projects • The toolkit is a guide to assist in the management of projects across all phases of the project lifecycle • The PMO Toolkit helps standardize how a project’s scope, timeline, requirements and strategies are documented • The tools build upon each other as the project moves from Request to Go Live (Project Document Lifecycle) • Some tools will be used throughout a project’s lifecycle • Contact List • Sign In Sheet • Meeting Agenda • Meeting Minutes • Status Report • Resource Tracking • Other tools are used during a specific phase (i.e. Assessment) • Many tools are started in one phase, refined throughout the project and closed at the conclusion (i.e. Project Plan)

17. Project Document Lifecycle • Request • Assessment • Planning • Implementation • Go Live • Project Closure

18. ProjectDocument Lifecycle Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking • Project Request: • The ServiceNow PPM module is the mechanism used to Request an ITS project • Pertinent information is to be completed on the request form, for submittal to the ITS PMO • Initiation*: • This tool initiates the process of data gathering and refining the core project information such as the problem statement, goal, known constraints and dependencies along with any identified risks/concerns. • Roadmap Presentation (Based on Phase): • This document is a means of requesting to move the project through the Project Lifecycle Phases and request resources. • Upon completion of the document, it is subsequently submitted to the PMO to be reviewed and included in the next Roadmap Meeting. *Gathering the desired signatures when these documents are complete ensures key project members are all aware and agree with the content of the document.

19. ProjectDocument Lifecycle • Charter*: • Cornerstone of the project • Lays the groundwork for informed decisions and planning regarding project direction, outcomes, and delivery • Managing expectations of all project stakeholders • Formal commitment between the Executive Sponsors, the Steering Committees, the Project Manager and the Project Core team • Budget/Costs: • Record and track the project related capital and/or operational expenses • Forecast future operational costs • Communication Plan*: • Methods and processes for communicating the needs and issues surrounding the project • Composition and meeting structure for project related items are defined • Storage and distribution of project related documentation • Scope:* • Most critical document of any project • Scope of the project is documented and Scope Change Management is defined • Agreement between all the parties involved on what will and will not be addressed in the solution of the Problem Statement • Assessment*: • First stage of developing project requirements • Define scope • Document assumptions • Identify risks • Document workflow *Gathering the desired signatures when these documents are complete ensures key project members are all aware and agree with the content of the document. • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

20. ProjectDocument Lifecycle • Project Plan/Timeline (software tool preference): • MS Project: • Detailed work breakdown structure • Task tracking for to include, but not limited to: • Task Name, Duration, Start, Finish, Predecessors, Resource Names, % Complete. • Excel: • High level or detailed timeline • Tasks can be customized to include, but not limited to: • Task name, Resources, Planned Start, and Target Finish • RAID (Risks, Action, Issues, Decisions): • Log to identify and track severity, mitigation plans, owner and disposition • RACI (Responsible, Accountable, Consulted, Informed): • Inventory of project deliverables Disposition per deliverable monitored • Functional Requirements: • Detailed listing of the operational characteristics: • Workflow • Application • Technical Requirements: • Non-functional requirements: • Technical designs • Technical specifications *Gathering the desired signatures when these documents are complete ensures key project members are all aware and agree with the content of the document. • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

21. ProjectDocument Lifecycle • Executive Summary*: • Report for Sr. Leadership and Governance, summarizing the following: • Overall Goal • Objectives • Proposed Solution • Scope • Risks/Concerns • Timing • Resources • Scope Change Management*: • Utilized once scope is finalized and there is a change in scope: • Primary scope control for a project • Lists the changes and impacts upon the defined scope of the project • Approval and Sign off required by project leadership • Recommendation or Proposal*: • Result of the assessment, not the final design • High level proposal to highlight main areas of project • Testing Plan Strategy*: • Outline of how testing will be performed, verified and documented • Training Plan Strategy*: • Defines all the aspects of training required for the implementation of the project • Kick Off Presentation: • Presentation of the proposed solution, strategy, process, and timeline *Gathering the desired signatures when these documents are complete ensures key project members are all aware and agree with the content of the document. • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

22. ProjectDocument Lifecycle • Go Live Readiness*: • Highlights all items for Go-Live: • Staff to support Go Live • Environment for go-live • Note: Check off items and sections can be customized based on project deliverables. • Go Live Checklist*: • Itemized plan for the Go-Live event consisting of: • Pre Go-Live • Go-Live • Post Go-Live • Detailed tasks: • Responsible party • Dates, times, and duration • Task status • Note: The checklist can be customized based on project deliverables. *Gathering the desired signatures when these documents are complete ensures key project members are all aware and agree with the content of the document • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

23. ProjectDocument Lifecycle No Additional documents introduced • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

24. ProjectDocument Lifecycle • Lessons Learned*: • Review of the successes and short-comings in the project • Learn from and improve the project management process • Project Closure and Acceptance*: • Agreed upon project deliverables and requirements have been satisfied • Exceptions they are noted along with their planned disposition • Project summary for historical purposes • Summarizes the ongoing operations and support of the solution moving forward *Gathering the desired signatures when these documents are complete ensures key project members are all aware and agree with the content of the document. • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

25. Project Document Lifecycle • Ongoing Documents: Contact List, Sign In Sheet, Meeting Agenda, Meeting Minutes, Status Report, Resource Tracking

26. PMO Toolkit and Document Lifecycle Summary • The ITS PMO Toolkit and Project Document Lifecycle were developed to assist the management of ITS projects • The templates are guides to standardize project activities • Project managers and leads should become familiar with the toolkit and incorporate these templates into their project management activities • The templates use the < and > symbols to note whenever a project specific entry • should be added • Not all projects require all templates, however, all projects should minimally include: • Scope • Timeline

27. PMO Toolkit Project Example Observation Unit Development: Scope

28. PMO Toolkit Project Example Observation Unit Development: Scope

29. PMO Toolkit Project Example Observation Unit Development: Timeline and Resources Resources

30. PMO Toolkit Project Example Observation Unit Development: Budget/Costs Detail Non-IT: $34,417 (WOWs, paging system; move&secure doors; airphone-unit access) Funding: Nursing IT: $ 4,500 (Consultant hours – 45 @ $100; included above) Funding: IT Operations

31. PMO Overview - Review • Where can you find the purpose/role of the Project Management Office Team? • How many phases in the Project Lifecycle? • Does the Assessment Phase come after the Implementation phase? • Name the phases in the Project Lifecycle? • Benefits of engaging the Project Management Office • Purpose of PMO Toolkit documentation? • Are all the documents in the PMO Document Lifecycle required for each phase? • How many ITS Governance Committees are established at BMC? • What is the first Step to request a project? • What is the most important project document in the PMO Document Lifecycle? • In the Mission statement! • Six • No! • Request – Assessment – Planning – Implementation – Go Live – Project Closure • Coaching Services; Standardized Toolkit; Proven track record • Standardization across project lifecycle • No! • Two: VP Governance and ITS Internal Governance! • Complete and submit the Request form in ServiceNow! • Scope!

32. Project Management Office Tutorial Questions? THANK YOU! If you are interested in utilizing the toolkit, please contact: Lori Siracusa 617-414-8564 Lori.Siracusa@BMC.Org