Presentation is loading. Please wait.

Presentation is loading. Please wait.

Introduction to Project Management

Similar presentations


Presentation on theme: "Introduction to Project Management"— Presentation transcript:

1 Introduction to Project Management
Project Planning Overview Welcome to Introduction to Project Management: Project Planning Overview. This is Lecture b. Lecture b This material (Comp19_Unit4b) was developed by Johns Hopkins University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC

2 Project Planning Overview Learning Objectives—Lecture b
Identify the importance and purpose of effective planning. Identify and describe each component of the project management plan. Define and prepare project planning documents. The Objectives for Project Planning Overview are to: Identify the importance and purpose of effective planning, Identify and describe each component of the project management plan, and Define and prepare project planning documents. This lecture will focus on the third objective. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b

3 Work Breakdown Structure (WBS)
Unit 4 - Project Planning Overview 7/6/10 Work Breakdown Structure (WBS) The work breakdown structure, or WBS, sets the project boundaries. It is created after the project scope statement is complete and provides detailed scope definition and is developed for all projects, regardless of size and complexity. The WBS is one of the most important project documents created during project planning, in part because it helps prevent scope creep. The project scope statement is the starting point for building the WBS. The scope statement is broken down into small manageable components through a technique called decomposition. Decomposition continues until all work is eventually broken down to the lowest level of the WBS, which is called a work package. You can see this process illustrated on the slide in the graphical depiction of the WBS. In theory, work packages are typically eight to 80 hours of work. The project manager should break the work down until a realistic chunk of work (or a deliverable) is reached that can be scheduled, assigned to be performed, cost estimated, monitored, and controlled. The key outputs of the WBS process are the WBS itself, the WBS dictionary, and the scope baseline. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

4 Work Breakdown Structure(WBS)
Unit 4 - Project Planning Overview 7/6/10 Work Breakdown Structure(WBS) The WBS is the foundation from which most planning stems. It provides a graphical view of a project, and organizes and defines the entire scope of the project. The project team will analyze each work package of the WBS to identify all the activities that need to be performed. This information will ultimately help develop the schedule and make key procurement decisions. The analysis of the WBS also helps to estimate the cost of performing the work, which ultimately leads to informing the budget; to determine the resources required to perform the work; to determine the quality of the work and to identify risks Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

5 Time Management Planning Processes
Unit 4 - Project Planning Overview 7/6/10 Time Management Planning Processes Define activities Sequence activities Estimate activity resources Estimate activity duration Develop a schedule In developing the project schedule, the project team determines what work must be performed, who will be assigned the work, the sequence the work will follow, when it will be performed, and the duration of the work. The WBS should not be confused with a schedule. It does not show activity relationships, sequence of activities, or activity dependencies. When the WBS is created, the scope of the project is decomposed to the work package level. The work packages are further decomposed into activity lists, which help develop the project schedule. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

6 Unit 4 - Project Planning Overview
7/6/10 Activity Sequencing This diagram is an activity on node diagram. Boxes represent activities and arrows connect the activities and show dependencies. This is a very common method for performing project scheduling. A high-level summary in developing a project schedule includes: Sequenced activities, meaning that the predecessors and successors of each activity are determined Determined activity paths The determined duration of each path Identify the critical path, which is the longest path through the project and determines the earliest date by which the project can be completed Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

7 Scheduling Terminology
Unit 4 - Project Planning Overview 7/6/10 Scheduling Terminology Schedule management plan Duration Effort Project schedule network diagrams Activity relationships Let’s review some schedule terminology. The Schedule Management Plan is a document that contains information on how the schedule will be developed and controlled, how schedule processes will be measured, and what scheduling tool will be used. Duration refers to the total number of work periods, as in days or workweeks, that are required to complete a scheduled activity. Effort is the amount of work or labor hours necessary to actually perform a scheduled activity. Project schedule network diagrams are a schematic depiction of scheduled activities and dependencies, which are logical relationships of activities. They model sequenced activities. Activity relationships refers to a diagramming technique that illustrates the activity’s logical relationships: finish to start, start to start, finish to finish, and start to finish. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

8 Scheduling Terminology
Unit 4 - Project Planning Overview 7/6/10 Scheduling Terminology Schedule Critical path Gantt chart Milestone Float or slack Scheduling tools The schedule documents when the project activities will be completed. The Critical path refers to the longest path of activities through the schedule network, and it establishes the earliest date by which the project can be completed. You will hear critical path referred to constantly when talking about project scheduling. A Gantt chart provides a good graphic illustration of the project schedule; this type of bar chart is easy to construct and lists the project activities vertically on the left side of the bar chart and the schedule dates horizontally across the top of the bar chart. This is the default view in tools like Microsoft Project, so if you have dealt with tools like that you have seen the Gantt chart over and over again. A milestone is a marker on a timeline with zero days duration; it signifies a major achievement or important event in a project. Float, sometimes referred to as slack, is the amount of time an activity can be delayed and not push back the early start of a successive activity, which are found on a noncritical path in the network diagram. Scheduling tools are computerized project management software applications that help the project manager develop the schedule and provide information to manage the project. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

9 Activity Duration Estimation Techniques
Unit 4 - Project Planning Overview 7/6/10 Activity Duration Estimation Techniques Estimating Techniques: Analogous Expert judgment Parametric Three-point estimate Program Evaluation & Review Technique (PERT) There are a variety of estimation techniques. It is important for the project management team to estimate the likely number of work periods required to perform an activity. The project manager and the project management team can use any of the following estimating techniques in order to achieve this. Analogous techniques determine the estimate by using resource duration estimate information from similar past projects; this is often used in project initiation or early planning when detailed project information is lacking. A project manager may use such expert judgment techniques as acquiring estimate information from individuals with historic information or experience related to similar prior projects. It is not uncommon to bring in someone with expert judgment to help perform project estimation. A parametric technique is a statistical approach to develop estimates based on historical data and other variables, such as square footage or labor hours per unit of work. A three-point estimate calculates the expected activity duration by adding an optimistic estimate, a pessimistic estimate, and a most likely average estimate together and dividing by three. A program evaluation and review technique (PERT) estimate is a popular type of three-point estimate that uses a weighted average estimate. While it has advantages, such as a more precise scheduling and control, it is a more complex and costly method to estimate durations. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

10 Types of Activity Dependencies
Unit 4 - Project Planning Overview 7/6/10 Types of Activity Dependencies Mandatory: Initial activity precedes the following activity Discretionary: Either activity can go first External: Something from “outside” is required that may impact sequence of activities You must know dependency determinations between activities when preparing a schedule and understand the relationships between activities. That is, it is very important to understand the relationships between all of the activities in the projects before you can produce an accurate schedule. Activity dependencies fall into the following 3 types: In a mandatory dependency, the activity sequence is inherent in the nature of the work performed. The initial activity must be started or completed before a following activity can begin. For example, you can’t erect a structure until after the foundation is built; you can’t paint a wall until the dry wall is complete; and you can’t test an application until after it has been developed. Discretionary dependencies involve using best practices when sequencing activities. For example, plumbing and electrical work in construction can be performed in either sequence, so the manager will have to use best judgment here. An External dependency is something that is required from “outside the project” and it can impact the sequence of activities. Permits or inspections are examples of external dependencies. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

11 Duration Compression Techniques
Unit 4 - Project Planning Overview 7/6/10 Duration Compression Techniques Crashing: adding more resources to activity; may result in increased cost Fast-Tracking: overlapping activities that are normally performed in sequence; may increase risk and result in rework Duration compression techniques are used to compress or shorten the project schedule. These techniques are typically used to get a project schedule back on track. Crashing involves adding more resources to an activity. This may result in increased costs, but it will help you push the schedule forward more quickly. Fast tracking is a way to speed up your project by overlapping your activities or running them in parallel. This can often lead to greater risk and potentially impact quality, which may sometimes result in rework. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

12 Cost Management Planning Processes
Unit 4 - Project Planning Overview 7/6/10 Cost Management Planning Processes Estimate costs Determine budget During project planning, the project team uses estimated costs of individual activities or work packages. The cost estimates are aggregated to establish a cost baseline. The cost estimating techniques, whether analogous or parametric, are the same as used in time management to estimate activity durations. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

13 Unit 4 - Project Planning Overview
7/6/10 Cost Management Plan May include: Level of accuracy of activity cost estimates Units of measure for the resources Control thresholds for cost variation Performance measurement rules Reporting formats A cost management plan sets the format regarding how project cost will be managed. The plan is developed by the project team and is a component of the project management plan. It may include: Level of accuracy of activity cost estimates Units of measure for the resources Control thresholds for cost variation Performance measurement rules Reporting formats Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

14 Planning for Project Quality Management
Unit 4 - Project Planning Overview 7/6/10 Planning for Project Quality Management During project planning the project team identifies and documents quality requirements, standards, and metrics to measure quality performance for the project and product and develops a quality management plan. Project Quality Planning Process: Plan Quality During project planning, the team identifies and documents quality requirements, standards, and metrics to measure quality performance for the project and product, and then develops a quality management plan. The project team should focus on managing customers’ expectations by meeting their requirements. The team should not attempt to exceed requirements or provide extras. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

15 Unit 4 - Project Planning Overview
7/6/10 Plan Quality The quality management plan is a document within the project management plan. The document addresses project quality control (QC), quality assurance (QA), and continuous quality improvement. The quality management plan is a document within the project management plan. This document addresses project quality control, quality assurance, and continuous quality improvement. During the planning process, the project team focuses on a proactive and preventative approach to ensure that quality is designed into the project. If this step is missed, it may result in poor quality with costs associated with excess inventory, waste, rework ,and warranty support. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

16 Planning for Human Resource Management
Unit 4 - Project Planning Overview 7/6/10 Planning for Human Resource Management After the project team has identified all activities that must be performed they determine the project resource requirements used to develop a human resource plan. Human Resource Planning Process: Develop Human Resource Plan Resources on an IT project could include one or more of the following roles: A business analyst A network specialist For a health IT project, a medical specialist who could be a doctor, nurse, or researcher A project manager A programmer Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

17 Unit 4 - Project Planning Overview
7/6/10 Human Resource Plan A human resource plan contains the following information: Assigned team member roles & responsibilities Approach for managing team members and staffing policies Describes how project resources will be acquired and released Describes how team members will be managed The human resource plan contains the following information: Assigned team member roles & responsibilities The approach for managing team members and staffing policies A description of how project resources will be acquired and released A description of how team members will be managed Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

18 A Human Resource Management Plan
Unit 4 - Project Planning Overview 7/6/10 A Human Resource Management Plan Describes how training requirements of team members will be accomplished Defines criteria for rewards and recognition Provides project organizational charts and position descriptions A human resource management plan: Describes how training requirements of team members will be accomplished Defines criteria for rewards and recognition Provides project organizational charts and position descriptions, which is an organizational breakdown structure that diagrams the project team members’ reporting relationships Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

19 Responsibility Assignment Matrix (RAM)
Unit 4 - Project Planning Overview 7/6/10 Responsibility Assignment Matrix (RAM) A common tool for project management and human resource management is a responsibility assignment matrix, or RAM. This is a diagram that correlates the project organizational structure to the WBS. The matrix diagram on this slide depicts the work that must be performed and the individual or team responsible for performing that work. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

20 Planning for Project Communications Management
Unit 4 - Project Planning Overview 7/6/10 Planning for Project Communications Management During project planning, the project team develops a communications management plan that contains a description of the identified project stakeholder information needs and defines the approach for communicating during the project. Project Communications Planning Process: Plan Communications During project planning, the project team develops a communications management plan that describes the identified project stakeholder information needs and defines the approach for communicating during the project. A communication requirements analysis is performed to determine the stakeholder information needs. The project team must determine what project information will be shared, who it will be shared with, when the information will be shared, and how the information will be shared. Information in the communication management plan may include organization charts, responsibility assignment matrix, name and contact information of change control board members, meeting times and locations, locations of team members, and potentially more information that can be determined by the project management team. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

21 Communications Management Plan
Unit 4 - Project Planning Overview 7/6/10 Communications Management Plan Describes the communication needs of the project stakeholders Describes how communication will be managed on the project, and the type and format in which the information will be communicated Describes when and how communications will be shared Identifies who is responsible for providing information Describes escalation processes The Communications Management Plan: Describes the communication needs of the project stakeholders Describes how communication will be managed on the project, and the type and format in which the information will be communicated Describes when and how communications will be shared Identifies who is responsible for providing information Describes required escalation processes for communications Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

22 Communication Requirements Analysis
Unit 4 - Project Planning Overview 7/6/10 Communication Requirements Analysis During project planning the project team conducts a communication requirements analysis to: Determine the type and format of information needed to develop the communications management plan Identify the stakeholder information needs The project team conducts a communication requirements analysis to: Determine the type and format of information needed to develop the communications management plan And identify the stakeholder information needs Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

23 Communication Methods
Unit 4 - Project Planning Overview 7/6/10 Communication Methods Interactive communication: meetings, phone calls, and so on Push communication: memos, reports, faxes, and so on Pull communication: intranet sites, knowledge repositories, and so on Project information is shared with stakeholders by different methods. First, interactive communication, which could include meetings, phone calls, and other types of communication that take place in a two-way format, such as a dialogue. Then there is push communication such as memos, reports, and faxes in which one party pushes communications to another party. There are also poll communication, which includes internet sites, knowledge repositories, and other kinds of self-service information resources where people can go and consume the information at their will. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

24 Unit 4 - Project Planning Overview
7/6/10 Kickoff Meeting First major meeting in project planning with the key project stakeholders Focus on building relationships, reviewing the project objectives & understanding project goals High level discussion of project scope, risks, schedule and milestones, communications, constraints, and assumptions Review team member roles & responsibilities Describe how the project fits in the organizations’ business strategy and the benefit in funding the project Opportunity for stakeholders to ask questions Project management plan is shared at the meeting The kickoff meeting is the first major meeting with the key project stakeholders. Its focus is on building relationships, reviewing the project objectives, and understanding project goals. It will include a high-level discussion of project scope, risks, schedule and milestones, communications, constraints, and assumptions. It is also a great chance to review team member roles and responsibilities. It allows the project leadership to describe how the project fits into the organization’s business strategy and the benefit in funding the project. It is also an opportunity for stakeholders to ask questions. Typically, the project management plan is shared during this meeting. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

25 Planning for Project Risk Management
Unit 4 - Project Planning Overview 7/6/10 Planning for Project Risk Management Project Risk Planning Processes: Plan risk management Identify risks Perform qualitative risk analysis Perform quantitative risk analysis Plan risk responses Now we’ll discuss how to plan for project risk management. Typically the project risk planning process includes planning for: risk management, identifying risks, performing qualitative risk analysis, performing quantitative risk analysis, and then understanding how to appropriately respond to all risks. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

26 Unit 4 - Project Planning Overview
7/6/10 Risk Management The project team determines risks that may affect meeting the project objectives. The goal in risk management is to increase the probability and impact of positive events and decrease the probability and impact of negative events in the project. The project team should be proactive and consistent in addressing project risk issues during the entire project life cycle. The project team identifies risks that may affect the schedule or deliverables. The risk management process aims to increase positive events and decrease negative events throughout the course of the project. The project team should address project risk issues quickly and efficiently. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

27 Unit 4 - Project Planning Overview
7/6/10 Risk Management Risk management policies of a company will help determine how the project team will plan to manage project risk. Project manager needs to understand the risk tolerance levels of the stakeholders (i.e., risk averse, risk seeker, risk neutral). The risk management policies of a company will help the project team plan to manage risk. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

28 Unit 4 - Project Planning Overview
7/6/10 Risk Management Plan Document describes how project risk management will be structured and performed on the project. A risk management plan component includes: Approach to managing project risks Roles & responsibilities in managing risks Budgeting for managing risks Risk categories (RBS) Definition of risk probability & impact Risk probability & impact matrix Stakeholders’ risk tolerances Tracking risks The risk management plan document describes how project risk management will be structured and performed on the project. Components of a risk management plan include: the appropriate approach to managing project risks, the roles and responsibilities in managing risks, budgeting for managing risks, identification of key risk categories, definition of risk probability and impact, a risk probability and impact matrix, the risk tolerances of the different stakeholders in the projects, and a place to track risks. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

29 Risk Management Terminology
Unit 4 - Project Planning Overview 7/6/10 Risk Management Terminology Dimensions of Risk: Probability of event is the chance of a risk event occurrence; odds of something occurring generally is measured in percentages, real numbers, or nonnumerical Impact of event may be good or bad Now, let’s review some risk management terminology. Dimensions of risk include the probability of event and whether the impact is good or bad. Probability of event is the chance of a risk event occurrence. The odds of something occurring generally is measured in percentages, real numbers or nonnumerically. Probability or likelihood can be measured as 0 to 100%, or low, medium and high. The impact of an event is also known as the amount at stake or consequence. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

30 Unit 4 - Project Planning Overview
7/6/10 Risk Register Risk register is a document that is developed early in project planning and progressively elaborated in the risk management planning process. At a minimum, the risk register contains identified risks, description of risks, results of the qualitative and quantitative risk analysis, risk triggers, risk owners, and planned risk response strategies. A risk register is developed early in the project planning process and elaborated on during the risk management planning process. The risk register contains identified risks, description of risks, results of the qualitative and quantitative risk analysis, risk triggers, risk owners, and planned risk response strategies. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

31 Unit 4 - Project Planning Overview
7/6/10 Risk Register This slide provides an example of a risk register. And you will see, it consists of rows and columns and the key columns are risk ID number, risk statement, probability of occurrence, and impact or potential impact of that risk playing out. A risk register can include a score, which would be probability times impact, things that could trigger that risk, who is the owner of that risk, who would deal with risk response, and what is the planned response if that risk does play out. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

32 Planning for Project Procurement Management
Unit 4 - Project Planning Overview 7/6/10 Planning for Project Procurement Management During project planning the project team develops a procurement management plan. The plan documents the goods and services that will be procured from outside the project organization and the procurement approach. A procurement management plan lists the goods and services that should be gathered from outside the project organization, and defines the means by which they will be collected. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

33 Project Planning Overview Summary—Lecture b
Unit 4 - Project Planning Overview 7/6/10 Project Planning Overview Summary—Lecture b A major reason for project failure is the lack of, or inadequate, project planning. Planning is recognized as a very crucial step in project management to ensure project success. The project team should be involved in developing the plans that define how the project will be accomplished. The plans will be used by the project team to perform the work and control the project. The amount of time and effort dedicated in planning the project should be appropriate to the project requirements. Every project should have a WBS because virtually all planning stems from it! This concludes Lecture b of Project Planning Overview. In summary, we have reviewed the importance and purpose of effective planning, the various elements of the project management plan, and defined the project planning documents. Remember that the major reason for project failure is the lack of, or inadequate, project planning. To encourage their investment in the project and hear different perspectives, you should involve your project team in developing the plans that define how the project will be accomplished. The plans will be used by the project team to perform the work and control the project. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b CDCG_PM Unit 4

34 Project Planning Overview References—Lecture b
 Health Information and Management System Society. Chicago, IL Available from: Highsmith JA. (2009). Agile Project Management: Creating Innovative Products. 2nd ed.; Boston: Addison-Wesley. HITECH Answers Available from: Houston S, Bove LA. (2010) Project Management for Healthcare Informatics. New York: Springer Science + Business Media, LLC. Kerzner H. (2009) Project Management: a Systems Approach to Planning, Scheduling, and Controlling. 10th ed. Hoboken, NJ.:Wiley.  mHealth Initiative. Boston, MA Available from: Project Management Institute, A Guide to the Project Management Body of Knowledge. 4th ed (2008).Newtown Square, PA: PMI. Scwalbe K. (2009) Information Technology Project Management (with Microsoft Project 2007 CD-ROM). 6th ed.; Boston: Cenage Learning. Stackpole C. (2009). A Project Manager’s Book of Forms: A Companion to the PMBOK Guide. Hoboken, N.J.:Wiley; Whitten N. Neal (2007).Whitten's Let's Talk! More No-nonsense Advice for Project Success. Vienna, VA.:Management Concepts Inc. Wiefling K. (2007) Scrappy Project Management: The 12 Predictable and Avoidable Pitfalls Every Project Faces 1st ed. Happy About;  Wysocki, RK .(2009).Effective Project Management: traditional, agile, extreme. 5th Edition. New York: Wiley. No audio. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b

35 Project Planning Overview References—Lecture b
Tables, Charts,Figures Table 4.4. Responsibility Matrix. Courtesy of Theron Feist. Table 4.5 Risk Register. Courtesy of Theron Feist. Images Slide 4: Work Breakdown Structure. Courtesy of Theron Feist. Slide 6: Activity Sequencing. Courtesy of Theron Feist. No audio. Health IT Workforce Curriculum Version 3.0/Spring 2012 Introduction to Project Management Project Planning Overview Lecture b


Download ppt "Introduction to Project Management"

Similar presentations


Ads by Google