1. DEFINING THE PROJECT
CHAPTER 4

2. Objectives: Step 1: Defining the Project Scope
Step 2: Establishing Project Priorities
Step 3: Creating the Work Breakdown Structure
Step 4: Integrating the WBS with the Organization
Step 5: Coding the WBS for the Information System

3. Project Priorities Unexpected tech. problems
Performance
Time
Unexpected tech. problems
Insufficient resources
Quality problems
Client changes in specs
Tasks took longer than planned
Initial time estimates were optimistic
Cost
Scope of work increases
Initial bids were too low
Poor reporting or untimely
Corrective control not exercised in time

4. Project Plan Development
Project Charter
Other information
Project description
Business case or need
Problem statement
Owner
Scope statement
Goals
Results (deliveriables)
Risks
Performance measurement baselines
Major milestones and target dates
Subsidiary management plans
Ex. Procurement plan
Project plan – formal approved set of documents used to control project execution. May change over time as more information becomes available

5. Definition of scope:
A definition of the end result or mission of the project—a product or service for the client/customer—in specific, tangible, and measurable terms.

6. Scope Checklist Project objective Deliverables Milestones
Technical requirements
Limits and exclusions
Reviews with customer

7. Issue (scope statement)
Lean Healthcare Conference
Issue (scope statement)
Focus a scope statement by answering who, what, when, and where.
Who -
Customers?
Suppliers?
Who else is involved?
What-
Nature of the problem?
-what happens?
-what do we know about it?
When-
-day, time, shift, month?
-when is the problem greatest?
Where-
Does the problem occur?
-at what step in the process?
-location?

8. Work Breakdown Structure (WBS)
An hierarchical outline (map) that identifies the products and work elements involved in a project.
Defines the relationship of the final deliverable (the project) to its sub deliverables, and in turn, their relationships to work packages.
Best suited for design and build projects that have tangible outcomes rather than process-oriented projects.

9. Steps for Constructing a WBS
Divide project into major objectives
Design stage
Construction stage
Closure
Partition Each objective into activities or tasks
Divide each activity into sub activities
Repeat step 3 until all sub activities have characteristics desired
Lowest-level sub activities will be basis of work packages that must be done in order to complete project

10. Level 1 – Program: large, long-range objective broken down into set of projects
Level 2-4: Tasks – work elements that require careful coordination and control in terms of timing, precedence, cost, performance to meet project/program goal
Work Packages – sub element of a task that needs to be accomplished in order to achieve the objetives of the task

12. Resource Planning Project goal Technical Resource availability
Project schedule
Contingency plan and replanning
Project policy
Project procedure
Performance standard
Tracking, reporting, and auditing
Goal – specification of what skill needed at each stage
Technical – technical and managerial strategies to be deployed
Availability of resource – negotieations
Schedule can be influenced by resource limitations
Policy – any guidlelines for carrying out the tasks
Procedures – method for implementing policy

13. Responsibility Matrix

14. Any Questions?