Work Breakdown Structure
Week 3 Assignment Work Breakdown Structure
BUS 611 Project Planning and Management
August 13, 2012
Week 3 Assignment WBS Level 1 | Level 2 | Level 3 | Responsibility | CPN Electronic Medical Record Work Breakdown Structure | 1.1 Project Conception and Initiation | Task: 1.1.1 Evaluation and recommendations
Task: 1.1.2 Review Scope and timeline
Task: 1.1.3 Review resources, support and Technical Plans | Project Manager, Vendor Project Manager, CIO and Key Stakeholders | | 1.2 Project Definition and Planning | Task: 1.2.1 Develop Project Charter and Project PlanTask: 1.2.2 Determine project team and
Task: 1.2.3 Project Team Kickoff Meeting | Project Manager and Vendor Project Manager | | 1.3 Project Execution | Task: 1.3.1 Install test system and complete Integrated testing
Task: 1.3.2 Procure and deploy hardware/software and User Training
Task: 1.3.3 Install Live System
Task:1.3.4 Go Live | IT Project manager and Vendor Project Managers, Systems Analysts, Systems Programmers, Clinical Informatics Specialist, Network Analyst, Ancillary Systems ManagerOpenlink Specialist, IT Techs, IT Operations Manager | | 1.4 Project Performance and Control | Task: 1.4.1 Change Management
Task: 1.4.2 Project Weekly Status Meetings
Task: 1.4.3 Risk Analysis and Contingency Plan | IT Project Manager, Change Management Committee, Vendor Project Manager | | 1.5 Project Close | Task: 1.5.1 Update and archive files/records
Task: 1.5.2 Document Lessons Learned
Task: 1.5.3 1.5.4 Sign-Off on Formal Acceptance | IT Project Manager and Vendor Manager |
A Work Breakdown Structure diagram expresses the project scope in simple graphic when tasks in a project do not need to be completed in a linear fashion.
Contingency Plan
What looked like a carefully orchestrated set of assignments can turn into a total debacle without some method of rescuing the derailing train. Effectively
BUS 611 Project Planning and Management
August 13, 2012
Week 3 Assignment WBS Level 1 | Level 2 | Level 3 | Responsibility | CPN Electronic Medical Record Work Breakdown Structure | 1.1 Project Conception and Initiation | Task: 1.1.1 Evaluation and recommendations
Task: 1.1.2 Review Scope and timeline
Task: 1.1.3 Review resources, support and Technical Plans | Project Manager, Vendor Project Manager, CIO and Key Stakeholders | | 1.2 Project Definition and Planning | Task: 1.2.1 Develop Project Charter and Project PlanTask: 1.2.2 Determine project team and
Task: 1.2.3 Project Team Kickoff Meeting | Project Manager and Vendor Project Manager | | 1.3 Project Execution | Task: 1.3.1 Install test system and complete Integrated testing
Task: 1.3.2 Procure and deploy hardware/software and User Training
Task: 1.3.3 Install Live System
Task:1.3.4 Go Live | IT Project manager and Vendor Project Managers, Systems Analysts, Systems Programmers, Clinical Informatics Specialist, Network Analyst, Ancillary Systems ManagerOpenlink Specialist, IT Techs, IT Operations Manager | | 1.4 Project Performance and Control | Task: 1.4.1 Change Management
Task: 1.4.2 Project Weekly Status Meetings
Task: 1.4.3 Risk Analysis and Contingency Plan | IT Project Manager, Change Management Committee, Vendor Project Manager | | 1.5 Project Close | Task: 1.5.1 Update and archive files/records
Task: 1.5.2 Document Lessons Learned
Task: 1.5.3 1.5.4 Sign-Off on Formal Acceptance | IT Project Manager and Vendor Manager |
A Work Breakdown Structure diagram expresses the project scope in simple graphic when tasks in a project do not need to be completed in a linear fashion.
Contingency Plan
What looked like a carefully orchestrated set of assignments can turn into a total debacle without some method of rescuing the derailing train. Effectively