1. Project Management & Project Management Software
Yale Braunstein
School of Information Management & Systems UC Berkeley

2. Getting started Think in terms of tasks They should be easily defined
IS 208
27-Oct-17
Getting started
Think in terms of tasks
They should be easily defined
There should be a “reasonable” number of tasks
Task properties: duration, predecessors, etc.
“Critical” tasks
Milestones
Summary tasks (optional, but useful)
Demo video available in the lab.
Project Mgt. & PM Software

3. Project 2000 “project map”

4. Project 98 “project map”

5. This slide from DH Casebook CD-ROM
27-Oct-17
Planning Phase
3: Work Plan
2: Feasibility
Analysis
3: Staffing Plan
2: System
Request
Project Plan
3: Risk Assessment
3: Charter
3: Standards
Analysis Phase
5: As-Is System Summary
5: To-Be System Concept
6: As-Is Use Cases
5: Improvement
Opportunities
6: To-Be Use Cases
System Proposal
Go/No-Go Decision
4: Analysis
Plan
Project Plan
6: As-Is Process Model
6: To-Be Process Model
7: As-Is Data Model
7: To-Be Data Model
Design Phase
12: Data Storage Design
9: Infrastructure Design
10: Interface Structure
8: Revised Use Cases
9: Network Model
10: Interface Standards
Go/No-Go Decision
Project Plan Revised
System Design
System Proposal
8: Physical Process
Model
13: Program Structure
11:User Interface Template
This slide from DH Casebook CD-ROM
9: Hardware/Software
Specifications
8: Design
Plan
8: Physical Data
Model
11: User Interface Design
9: Security Plan
13: Program
Specifications
Implementation Phase
15: Conversion Plan
Delivered System
14: Programs
Go/No-Go Decision
Project Plan Revised
14: Test Plan
15: Change Management Plan
System Delivery
System Design
14: User Documentation
15: Support Plan
Project Assessment
14: Tested System
Project Mgt. & PM Software

6. Using MS Project Initial steps Set initial parameters Enter tasks
Link tasks
Enter resources
Assign resources to tasks
Additional steps
Enter milestones
Enter fixed costs

7. Analysis with MS Project
Look at Critical Path & identify slack
Check if resource used more than 100%
Group tasks; Split tasks
Remember baselines
Customize printouts

8. Track progress with MS Project
Several alternatives
Enter % completed
Enter time to complete
Enter date completed
(more than one is allowed)
Choose additional reports

9. Determine the Critical Path
What is the critical path?
The critical path is the series of tasks (or even a single task) that dictates the calculated finish date of the project. That is, when the last task in the critical path is completed, the project is completed.
If it's important for your project to finish on schedule, pay close attention to the tasks on the critical path and the resources assigned to them. These elements determine whether your project will finish on time.

10. Critical Path - continued
The series of tasks are generally interrelated by task dependencies. Although there are likely to be many such networks of tasks throughout your project plan, the network finishing the latest is the project's critical path.
Note that the critical path can change from one series of tasks to another as you progress through the schedule. The critical path can change as critical tasks are completed, or tasks in another series of tasks are delayed. There is always one overall critical path for any project schedule. The new critical path then becomes the series of tasks you track more closely to ensure the finish date you want.

11. Gantt chart

12. Tracking Gantt chart

13. Using the PERT Chart view
The critical path
Using the PERT Chart view

14. Using View / More Views / Detail Gantt
The critical path
Using View / More Views / Detail Gantt